lyo-dev

Re: [lyo-dev] Fwd: How to set "priority" for my work item with OSLC?

fiedler.mf@xxxxxxx (Michael Fiedler) — Fri, 24 May 2013 18:39:20 GMT

Hi, There's currently no Java resource in OSLC4J to represent that RTC-specific Literal resource. You could either

- create one that matches the predicates in Literal and have OSLC4J de-serialize to Java for you

- Use the OSLC client to do a get and don't de-serialize to java - just process the raw xml yourself (or with an RDF lib like Jena)

Regards,

Mike

On Fri, May 24, 2013 at 1:36 PM, Pietro Marella <pietro.marella@xxxxxxxxx> wrote:

---------- Forwarded message ----------
From: Pietro Marella <pietro.marella@xxxxxxxxx>
Date: 2013/5/24
Subject: How to set "priority" for my work item with OSLC?
To: lyo-dev@xxxxxxxxxxx

Hello

hope this is the right place where to post my question.
I wrote in the forum, but I didn't get an answer yet.

So if you can, I'll appreciate if you can spend some time to help me address this problem.
Thanks in advance.

"Hi all.
I'm new with OSLC. I started from using the package org.eclipse.lyo.client.oslc.samples (RTCFormSample.java in particular) provided with the Lyo prject and I have developed a class by myself that relies on the OSLC4J client libraries to create and query work items (changerequests) on my Rational Team Concert) server.

I need now to make a pass further.

One of the attributes I need to set when I create a WI is the Priority, that can assume a predefined set of values (in a drop down menu).
When I display the RDF of a Work Item:
GET https:/X.XX.XXX.XX:9443/ccm/oslc/contexts/_ryl8MLbfEeK8JbTtKcHtwA/workitem/330

Response:

.....
priority rdf:resource="<A href="">" '="">https:/x.xx.xx.xx:9443/ccm/oslc/enumerations/_ryl8MLbfEeK8JbTtKcHtwA/priority/priority.literal.l02"/>

as you can see, Priority is a "oslc_cmx" type of attribute and its value is an enumeration (href="">
So I did a GET from my REST Client on browser
(GET https:/X.XX.XXX.XX:9443/ccm/oslc/enumerations/_ryl8MLbfEeK8JbTtKcHtwA/priority)

and I get a response with all the "enumeration" available: this is an extract of the response, as for example:

jazz.net/xmlns/prod/jazz/rtc/cm/1.0/Literal"/>

www.w3.org/2001/XMLSchema#string">High
www.w3.org/2001/XMLSchema#string">priority.literal.l11

>From this response, I know that to set my WI Priority to "High" I need to write a code like this:

//create a ChangeRequest object
ChangeRequest wi = new ChangeRequest();

//create QNAME
QName OSLC_PRIORITY = new QName("http:/jazz.net/xmlns/prod/jazz/rtc/ext/1.0/", "http:/jazz.net/xmlns/prod/jazz/rtc/cm/1.0/Literal", "oslc_cmx");

private Map properties = new HashMap();

properties.put(OSLC_PRIORITY, "https:/X.XX.XXX.XX:9443/ccm/oslc/enumerations /_ryl8MLbfEeK8JbTtKcHtwA/priority/priority.literal.l11");

//set extended properties for the changerequest
wi.setExtendedProperties(properties)

//then create the WI
....................

This code works in some way, but of course, it is not fine.. I cannot use "hardcoded" values as I used in my sample.

What I need is to retrieve at runtime what are the valid pairs (value,URI) the attribute "priority" can assume. How should I do using the OSLC4J libraries? Is there any method I can use to simulate the execution of the GET I run on my browser, and to parse the response I should get back?

Hope I've not been too much confuse....

thanks in advance"
piero m.

_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/lyo-dev

[lyo-dev] Fwd: How to set "priority" for my work item with OSLC?

pietro.marella@xxxxxxx (Pietro Marella) — Fri, 24 May 2013 17:36:41 GMT

---------- Forwarded message ----------
From: Pietro Marella <pietro.marella@xxxxxxxxx>
Date: 2013/5/24
Subject: How to set "priority" for my work item with OSLC?
To: lyo-dev@xxxxxxxxxxx

Hello
hope this is the right place where to post my question.
I wrote in the forum, but I didn't get an answer yet.

So if you can, I'll appreciate if you can spend some time to help me address this problem.
Thanks in advance.

"Hi all.
I'm new with OSLC. I started from using the package org.eclipse.lyo.client.oslc.samples (RTCFormSample.java in particular) provided with the Lyo prject and I have developed a class by myself that relies on the OSLC4J client libraries to create and query work items (changerequests) on my Rational Team Concert) server.

I need now to make a pass further.

One of the attributes I need to set when I create a WI is the Priority, that can assume a predefined set of values (in a drop down menu).
When I display the RDF of a Work Item:
GET https:/X.XX.XXX.XX:9443/ccm/oslc/contexts/_ryl8MLbfEeK8JbTtKcHtwA/workitem/330

Response:

.....
priority rdf:resource="<A href="">" '="">https:/x.xx.xx.xx:9443/ccm/oslc/enumerations/_ryl8MLbfEeK8JbTtKcHtwA/priority/priority.literal.l02"/>

as you can see, Priority is a "oslc_cmx" type of attribute and its value is an enumeration (href="">
So I did a GET from my REST Client on browser
(GET https:/X.XX.XXX.XX:9443/ccm/oslc/enumerations/_ryl8MLbfEeK8JbTtKcHtwA/priority)

and I get a response with all the "enumeration" available: this is an extract of the response, as for example:

jazz.net/xmlns/prod/jazz/rtc/cm/1.0/Literal"/>

www.w3.org/2001/XMLSchema#string">High
www.w3.org/2001/XMLSchema#string">priority.literal.l11

>From this response, I know that to set my WI Priority to "High" I need to write a code like this:

//create a ChangeRequest object
ChangeRequest wi = new ChangeRequest();

//create QNAME
QName OSLC_PRIORITY = new QName("http:/jazz.net/xmlns/prod/jazz/rtc/ext/1.0/", "http:/jazz.net/xmlns/prod/jazz/rtc/cm/1.0/Literal", "oslc_cmx");

private Map properties = new HashMap();

properties.put(OSLC_PRIORITY, "https:/X.XX.XXX.XX:9443/ccm/oslc/enumerations /_ryl8MLbfEeK8JbTtKcHtwA/priority/priority.literal.l11");

//set extended properties for the changerequest
wi.setExtendedProperties(properties)

//then create the WI
....................

This code works in some way, but of course, it is not fine.. I cannot use "hardcoded" values as I used in my sample.

What I need is to retrieve at runtime what are the valid pairs (value,URI) the attribute "priority" can assume. How should I do using the OSLC4J libraries? Is there any method I can use to simulate the execution of the GET I run on my browser, and to parse the response I should get back?

Hope I've not been too much confuse....

thanks in advance"
piero m.

[lyo-dev] Commit rights for Olivier Berger have been expired

portal-noreply@xxxxxxx (portal on behalf of emo) — Thu, 23 May 2013 23:11:01 GMT

technology.lyo Committers, Steve Speicher has expired the commit rights for Olivier Berger (oberger). The reason for this change is: Per Olivier request, I regret to have to remove his commit rights as his time is focused on other priorities and can't contribute time needed to fulfill demands of Committer. Thanks for you contributions and support!

Re: [lyo-dev] Is it the media type: "application/x-oslc-disc-service-provider-catalog+xml" implemented in Lyo?

sderas@xxxxxxx (Sergio Jose Deras Arreola/Mexico/IBM) — Thu, 23 May 2013 20:17:23 GMT
Thanks Sam.

I think I am now able to add more information. DOORS is adding a header request "accept: application/rdf+xml". And the OSLC4JBugzilla answers in this format.
But I am looking at the catalogs from DOORS 9.5 and RTC 4.0. Note that the two of them wrap all the content inside the "ServiceProviderCatalog" tag.

RTC (rdf+xml):

<rdf:RDF>
<oslc:ServiceProviderCatalog rdf:about="https://:9443/ccm/oslc/workitems/catalog">
...
oslc:ServiceProviderCatalog>
rdf:RDF>

DOORS (xml):

ServiceProviderCatalogrdf:about="https://:8443/dwa/rm/discovery/catalog">
...

While the OSLC4JBugzilla catalog starts to describe the nodes immediately:

OSLC4JBugzilla (rdf+xml):

<rdf:RDF>
...
<rdf:Description rdf:about="http://:8900/OSLC4JBugzilla/services/catalog/singleton">
...
rdf:Description>
...
rdf:RDF>

So, there is no "ServiceProviderCatalog" tag in the OSLC4JBugzilla catalog.
RTC 4.0 does not have problems dealing with this and it recognize the "serviceProvider" tags correctly.
But DOORS is not. This makes me wonder, is DOORS requesting a special structure?

Again I need to ask, am I looking at the correct specification: http://open-services.net/bin/view/Main/OslcCoreSpecification?sortcol=table;table=up;up=#Service_Provider_Resources?
If so, I do not see that we need to wrap the information in the catalog into the "ServiceProviderCatalog" tag.

Thanks in advance.

Sergio Deras Arreola
------------------------------------------------------------
Rational Lifecycle Integration Adapters
Phone: (011-52) 33-3669-7000. Ext: 5897
T/L: 8877-5897
sderas@xxxxxxxxxxx
Campus Tecnológico Guadalajara, Mx
------------------------------------------------------------

From: Samuel Padgett
To: Lyo project developer discussions
Cc: Lyo project developer discussions , lyo-dev-bounces@xxxxxxxxxxx
Date: 20/05/2013 17:19
Subject: Re: [lyo-dev] Is it the media type: "application/x-oslc-disc-service-provider-catalog+xml" implemented in Lyo?
Sent by: lyo-dev-bounces@xxxxxxxxxxx

Hey, Sergio. This is an OSLC 1.0 response. OSLC 2.0 does not define this media type, and OSLC4J only supports OSLC 2.0. You should check to see if DOORS can be configured to use OSLC 2.0 for service discovery.

You'll see the 1.0 response from RTC in REST Client if you haven't specified an OSLC-Core-Version: 2.0 request header.
--
Samuel Padgett | IBM Rational | spadgett@xxxxxxxxxx

Sergio Jose Deras Arreola---05/20/2013 05:51:21 PM---Hi again: Thanks for the previous answer about the OAuth issues, they were helpful,

From:
Sergio Jose Deras Arreola/Mexico/IBM

To:
Lyo project developer discussions

Date:
05/20/2013 05:51 PM

Subject:
[lyo-dev] Is it the media type: "application/x-oslc-disc-service-provider-catalog+xml" implemented in Lyo?

Sent by:
lyo-dev-bounces@xxxxxxxxxxx

Hi again:

Thanks for the previous answer about the OAuth issues, they were helpful, that is now solved.
Now I am trying to get my OSLC Catalog working.

The situation is this:
I am following the OSLC4J Workshop to get a CM OSLC provider application (OSLC4JBugzilla).
Things do not look so bad, I can connect the OSLC4JBugzilla with the RTC, RQM, RRC all in 4.0 versions and provide Changerequests resources.

The problem is that DOORS 9.5 is not working with this implementation. DOORS can connect with RTC, RQM and RRC projects correctly, but not with OSLC4JBugzilla.

The issue seems to me like DOORS is not getting the Catalog in the correct format from the OSLC4JBugzilla .
According to the specification (I am looking here: http://open-services.net/bin/view/Main/OslcServiceProviderCatalogV1?sortcol=table;up=#Service_Provider_Catalog_Documen )
the Catalog media type is REQUIRED to be : application/x-oslc-disc-service-provider-catalog+xml

When I debug the code, by the time the catalog is requested, I see that DOORS does not add any "accept" media type header. But when I use a REST client to access the RTC 4.0 catalog (without the "accept" header) it returns a response with the Content-Type: application/x-oslc-disc-service-provider-catalog+xml. This matches the specification.

The funny part is that the CLM apps v4.0 can connect and consume OSLC4JBugzilla services without problems.

Questions:
Am I looking at the correct version of the Catalog Specification? Am I missing something else in order to connect it with DOORS?
Is the "application/x-oslc-disc-service-provider-catalog+xml" type implemented by any class in the Workshop? If not, what should I do to implement one?

Thanks in advance.

Sergio Deras Arreola
------------------------------------------------------------
Rational Lifecycle Integration Adapters
Phone: (011-52) 33-3669-7000. Ext: 5897
T/L: 8877-5897
sderas@xxxxxxxxxxx
Campus Tecnológico Guadalajara, Mx
------------------------------------------------------------_______________________________________________ lyo-dev mailing list lyo-dev@xxxxxxxxxxxhttp://dev.eclipse.org/mailman/listinfo/lyo-dev

_______________________________________________ lyo-dev mailing list lyo-dev@xxxxxxxxxxxhttp://dev.eclipse.org/mailman/listinfo/lyo-dev

Re: [lyo-dev] Is it the media type: "application/x-oslc-disc-service-provider-catalog+xml" implemented in Lyo?

sderas@xxxxxxx (Sergio Jose Deras Arreola/Mexico/IBM) — Thu, 23 May 2013 20:16:50 GMT
Thanks for the answer Maeve. I will take a note about that.
It looks like DOORS is expecting a specific structure as an answer, I will add more information in this thread, but in another mail.

Regards.

Sergio Deras Arreola
------------------------------------------------------------
Rational Lifecycle Integration Adapters
Phone: (011-52) 33-3669-7000. Ext: 5897
T/L: 8877-5897
sderas@xxxxxxxxxxx
Campus Tecnológico Guadalajara, Mx
------------------------------------------------------------

From: Maeve O Reilly
To: Lyo project developer discussions
Cc: "lyo-dev-bounces@xxxxxxxxxxx"
Date: 21/05/2013 07:19
Subject: Re: [lyo-dev] Is it the media type: "application/x-oslc-disc-service-provider-catalog+xml" implemented in Lyo?
Sent by: lyo-dev-bounces@xxxxxxxxxxx

Maybe this is related - in the DOORS Remote Services tab, manually set the OSLC version to 2.0. The auto detect always detects 1.0 (defect, due to be fixed in the June release).

HTH.
Maeve

From: Samuel Padgett
To: Lyo project developer discussions
Cc: Lyo project developer discussions ; lyo-dev-bounces@xxxxxxxxxxx
Sent: Monday, 20 May 2013, 23:18
Subject: Re: [lyo-dev] Is it the media type: "application/x-oslc-disc-service-provider-catalog+xml" implemented in Lyo?

Hey, Sergio. This is an OSLC 1.0 response. OSLC 2.0 does not define this media type, and OSLC4J only supports OSLC 2.0. You should check to see if DOORS can be configured to use OSLC 2.0 for service discovery.

You'll see the 1.0 response from RTC in REST Client if you haven't specified an OSLC-Core-Version: 2.0 request header.
--
Samuel Padgett | IBM Rational | spadgett@xxxxxxxxxx

Sergio Jose Deras Arreola---05/20/2013 05:51:21 PM---Hi again: Thanks for the previous answer about the OAuth issues, they were helpful,

Sergio Jose Deras Arreola/Mexico/IBM

Lyo project developer discussions

05/20/2013 05:51 PM

[lyo-dev] Is it the media type: "application/x-oslc-disc-service-provider-catalog+xml" implemented in Lyo?

lyo-dev-bounces@xxxxxxxxxxx

Hi again:

Thanks for the previous answer about the OAuth issues, they were helpful, that is now solved.
Now I am trying to get my OSLC Catalog working.

The situation is this:
I am following the OSLC4J Workshop to get a CM OSLC provider application (OSLC4JBugzilla).
Things do not look so bad, I can connect the OSLC4JBugzilla with the RTC, RQM, RRC all in 4.0 versions and provide Changerequests resources.

The problem is that DOORS 9.5 is not working with this implementation. DOORS can connect with RTC, RQM and RRC projects correctly, but not with OSLC4JBugzilla.

The issue seems to me like DOORS is not getting the Catalog in the correct format from the OSLC4JBugzilla .
According to the specification (I am looking here: http://open-services.net/bin/view/Main/OslcServiceProviderCatalogV1?sortcol=table;up=#Service_Provider_Catalog_Documen )
the Catalog media type is REQUIRED to be : application/x-oslc-disc-service-provider-catalog+xml

When I debug the code, by the time the catalog is requested, I see that DOORS does not add any "accept" media type header. But when I use a REST client to access the RTC 4.0 catalog (without the "accept" header) it returns a response with the Content-Type: application/x-oslc-disc-service-provider-catalog+xml. This matches the specification.

The funny part is that the CLM apps v4.0 can connect and consume OSLC4JBugzilla services without problems.

Questions:
Am I looking at the correct version of the Catalog Specification? Am I missing something else in order to connect it with DOORS?
Is the "application/x-oslc-disc-service-provider-catalog+xml" type implemented by any class in the Workshop? If not, what should I do to implement one?

Thanks in advance.

Sergio Deras Arreola
------------------------------------------------------------
Rational Lifecycle Integration Adapters
Phone: (011-52) 33-3669-7000. Ext: 5897
T/L: 8877-5897
sderas@xxxxxxxxxxx
Campus Tecnológico Guadalajara, Mx
------------------------------------------------------------_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/lyo-dev

_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/lyo-dev

_______________________________________________ lyo-dev mailing list lyo-dev@xxxxxxxxxxxhttp://dev.eclipse.org/mailman/listinfo/lyo-dev

[lyo-dev] Fwd: Fw: Forward this mail to the people you wish to invite to Event "Eclipse Lyo and OSLC Open Source Meetup"

sspeiche@xxxxxxx (Steve Speicher) — Tue, 21 May 2013 18:44:46 GMT

I (of course) will be there, if you are in Orlando on June 4th hope you can make it. Please register so we can notify you of the room # once we know it.

You have been invited to attend the following event:

Eclipse Lyo and OSLC Open Source Meetup

Event Date: Jun 4, 2013
Event Time: 3:00 PM - 4:30 PM (Eastern Time)
Hosted By: Eclipse Lyo and OSLC Open Source Communitiees
Presented By: Steve Speicher (IBM, Eclipse Lyo Project co-lead)

(This is a face-to-face meeting, not a web conference, we're just using the IBM SmartCloud Events infrastructure to handle registrations. The actual location at the Innovate conference will be shared with registrants once we know.)

Join fellow Eclipse Lyo and OSLC Open Source enthusiasts while at IBM Innovate for an informal meetup. Whether you are a current contributor, looking to contribute, consuming open source assets, learning about what is going on or want to just provide some feedback...this is the place for you. No limits to topics: various technologies such as Java, .NET, ... or even OSLC-enabling open source tools such as Bugzilla. Attendees make up the agenda and everyone can participate. It is expected that multiple project committers will be there to help with more advanced questions.
Register for the Event
Register for this event at:
https://events.na.collabserv.com/register.php?id=e3c94f76c4&l=en-US
If clicking a link above does not work, please copy the entire link and paste it into your Web browser.
For technical questions, contact support at support@xxxxxxxxxxxxxx.
For questions about this event, contact the hosts at: sspeiche@xxxxxxxxx and seanpk@xxxxxxxxxx.

Powered by IBM SmartCloud for Social Business
©Copyright 2000, 2013 IBM Corporation. All Rights Reserved.

Re: [lyo-dev] Is it the media type: "application/x-oslc-disc-service-provider-catalog+xml" implemented in Lyo?

maevedevine@xxxxxxx (Maeve O Reilly) — Tue, 21 May 2013 12:18:03 GMT

Maybe this is related - in the DOORS Remote Services tab, manually set the OSLC version to 2.0. The auto detect always detects 1.0 (defect, due to be fixed in the June release).

HTH.
Maeve

From: Samuel Padgett
To: Lyo project developer discussions
Cc: Lyo project developer discussions ; lyo-dev-bounces@xxxxxxxxxxx
Sent: Monday, 20 May 2013, 23:18
Subject: Re: [lyo-dev] Is it the media type: "application/x-oslc-disc-service-provider-catalog+xml" implemented in Lyo?

Hey, Sergio. This is an OSLC 1.0 response. OSLC 2.0 does not define this media type, and OSLC4J only supports OSLC 2.0. You should check to see if DOORS can be configured to use OSLC 2.0 for service discovery.

You'll see the 1.0 response from RTC in REST Client if you haven't specified an OSLC-Core-Version: 2.0 request header.
--
Samuel Padgett | IBM Rational | spadgett@xxxxxxxxxx

Sergio Jose Deras Arreola---05/20/2013 05:51:21 PM---Hi again: Thanks for the previous answer about the OAuth issues, they were helpful,

Sergio Jose Deras Arreola/Mexico/IBM

Lyo project developer discussions

05/20/2013 05:51 PM

[lyo-dev] Is it the media type: "application/x-oslc-disc-service-provider-catalog+xml" implemented in Lyo?

lyo-dev-bounces@xxxxxxxxxxx

Hi again:

Thanks for the previous answer about the OAuth issues, they were helpful, that is now solved.
Now I am trying to get my OSLC Catalog working.

The situation is this:
I am following the OSLC4J Workshop to get a CM OSLC provider application (OSLC4JBugzilla).
Things do not look so bad, I can connect the OSLC4JBugzilla with the RTC, RQM, RRC all in 4.0 versions and provide Changerequests resources.

The problem is that DOORS 9.5 is not working with this implementation. DOORS can connect with RTC, RQM and RRC projects correctly, but not with OSLC4JBugzilla.

The issue seems to me like DOORS is not getting the Catalog in the correct format from the OSLC4JBugzilla .
According to the specification (I am looking here: http://open-services.net/bin/view/Main/OslcServiceProviderCatalogV1?sortcol=table;up=#Service_Provider_Catalog_Documen )
the Catalog media type is REQUIRED to be : application/x-oslc-disc-service-provider-catalog+xml

When I debug the code, by the time the catalog is requested, I see that DOORS does not add any "accept" media type header. But when I use a REST client to access the RTC 4.0 catalog (without the "accept" header) it returns a response with the Content-Type: application/x-oslc-disc-service-provider-catalog+xml. This matches the specification.

The funny part is that the CLM apps v4.0 can connect and consume OSLC4JBugzilla services without problems.

Questions:
Am I looking at the correct version of the Catalog Specification? Am I missing something else in order to connect it with DOORS?
Is the "application/x-oslc-disc-service-provider-catalog+xml" type implemented by any class in the Workshop? If not, what should I do to implement one?

Thanks in advance.

Sergio Deras Arreola
------------------------------------------------------------
Rational Lifecycle Integration Adapters
Phone: (011-52) 33-3669-7000. Ext: 5897
T/L: 8877-5897
sderas@xxxxxxxxxxx
Campus Tecnológico Guadalajara, Mx
------------------------------------------------------------_______________________________________________ lyo-dev mailing list lyo-dev@xxxxxxxxxxxhttp://dev.eclipse.org/mailman/listinfo/lyo-dev

_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/lyo-dev

Re: [lyo-dev] Is it the media type: "application/x-oslc-disc-service-provider-catalog+xml" implemented in Lyo?

spadgett@xxxxxxx (Samuel Padgett) — Mon, 20 May 2013 22:18:58 GMT

Hey, Sergio. This is an OSLC 1.0 response. OSLC 2.0 does not define this media type, and OSLC4J only supports OSLC 2.0. You should check to see if DOORS can be configured to use OSLC 2.0 for service discovery.

You'll see the 1.0 response from RTC in REST Client if you haven't specified an OSLC-Core-Version: 2.0 request header.
--
Samuel Padgett | IBM Rational | spadgett@xxxxxxxxxx

Sergio Jose Deras Arreola---05/20/2013 05:51:21 PM---Hi again: Thanks for the previous answer about the OAuth issues, they were helpful,

From:

Sergio Jose Deras Arreola/Mexico/IBM

To:

Lyo project developer discussions

Date:

05/20/2013 05:51 PM

Subject:

[lyo-dev] Is it the media type: "application/x-oslc-disc-service-provider-catalog+xml" implemented in Lyo?

Sent by:

lyo-dev-bounces@xxxxxxxxxxx

Hi again:

Thanks for the previous answer about the OAuth issues, they were helpful, that is now solved.
Now I am trying to get my OSLC Catalog working.

The situation is this:
I am following the OSLC4J Workshop to get a CM OSLC provider application (OSLC4JBugzilla).
Things do not look so bad, I can connect the OSLC4JBugzilla with the RTC, RQM, RRC all in 4.0 versions and provide Changerequests resources.

The problem is that DOORS 9.5 is not working with this implementation. DOORS can connect with RTC, RQM and RRC projects correctly, but not with OSLC4JBugzilla.

The issue seems to me like DOORS is not getting the Catalog in the correct format from the OSLC4JBugzilla .
According to the specification (I am looking here: http://open-services.net/bin/view/Main/OslcServiceProviderCatalogV1?sortcol=table;up=#Service_Provider_Catalog_Documen )
the Catalog media type is REQUIRED to be : application/x-oslc-disc-service-provider-catalog+xml

When I debug the code, by the time the catalog is requested, I see that DOORS does not add any "accept" media type header. But when I use a REST client to access the RTC 4.0 catalog (without the "accept" header) it returns a response with the Content-Type: application/x-oslc-disc-service-provider-catalog+xml. This matches the specification.

The funny part is that the CLM apps v4.0 can connect and consume OSLC4JBugzilla services without problems.

Questions:
Am I looking at the correct version of the Catalog Specification? Am I missing something else in order to connect it with DOORS?
Is the "application/x-oslc-disc-service-provider-catalog+xml" type implemented by any class in the Workshop? If not, what should I do to implement one?

Thanks in advance.

Sergio Deras Arreola
------------------------------------------------------------
Rational Lifecycle Integration Adapters
Phone: (011-52) 33-3669-7000. Ext: 5897
T/L: 8877-5897
sderas@xxxxxxxxxxx
Campus Tecnológico Guadalajara, Mx
------------------------------------------------------------_______________________________________________ lyo-dev mailing list lyo-dev@xxxxxxxxxxxhttp://dev.eclipse.org/mailman/listinfo/lyo-dev

[lyo-dev] Is it the media type: "application/x-oslc-disc-service-provider-catalog+xml" implemented in Lyo?

sderas@xxxxxxx (Sergio Jose Deras Arreola/Mexico/IBM) — Mon, 20 May 2013 21:50:45 GMT
Hi again:

Thanks for the previous answer about the OAuth issues, they were helpful, that is now solved.
Now I am trying to get my OSLC Catalog working.

The situation is this:
I am following the OSLC4J Workshop to get a CM OSLC provider application (OSLC4JBugzilla).
Things do not look so bad, I can connect the OSLC4JBugzilla with the RTC, RQM, RRC all in 4.0 versions and provide Changerequests resources.

The problem is that DOORS 9.5 is not working with this implementation. DOORS can connect with RTC, RQM and RRC projects correctly, but not with OSLC4JBugzilla.

The issue seems to me like DOORS is not getting the Catalog in the correct format from the OSLC4JBugzilla .
According to the specification (I am looking here: http://open-services.net/bin/view/Main/OslcServiceProviderCatalogV1?sortcol=table;up=#Service_Provider_Catalog_Documen )
the Catalog media type is REQUIRED to be : application/x-oslc-disc-service-provider-catalog+xml

When I debug the code, by the time the catalog is requested, I see that DOORS does not add any "accept" media type header. But when I use a REST client to access the RTC 4.0 catalog (without the "accept" header) it returns a response with the Content-Type: application/x-oslc-disc-service-provider-catalog+xml. This matches the specification.

The funny part is that the CLM apps v4.0 can connect and consume OSLC4JBugzilla services without problems.

Questions:
Am I looking at the correct version of the Catalog Specification? Am I missing something else in order to connect it with DOORS?
Is the "application/x-oslc-disc-service-provider-catalog+xml" type implemented by any class in the Workshop? If not, what should I do to implement one?

Thanks in advance.

Sergio Deras Arreola
------------------------------------------------------------
Rational Lifecycle Integration Adapters
Phone: (011-52) 33-3669-7000. Ext: 5897
T/L: 8877-5897
sderas@xxxxxxxxxxx
Campus Tecnológico Guadalajara, Mx
------------------------------------------------------------

[lyo-dev] Fw: [oslc] OSLC Connect 2013 - 1st anual OSLC Event - survey

seanpk@xxxxxxx (Sean Kennedy) — Fri, 17 May 2013 15:42:12 GMT

FYI, maybe FYA

Best regards,

Sean Kennedy

OSLC Community Development Leader for IBM Rational

Operations Coordinator for the OSLC Steering Committee

Phone: +1-905-413-4385 8200 Warden Ave

Fax: +1-905-413-4850 Markham, Ontario L6G 1C7

Email: seanpk@xxxxxxxxxx D1/R0A/8200/MKM

LinkedIn: http://www.linkedin.com/in/seanpk Canada

OSLC: Lifecycle integration inspired by the web http://open-services.net

Eclipse Lyo: Enabling tool integration with OSLC http://eclipse.org/lyo

There is nothing more powerful than an idea whose time has come. -- Victor Hugo

----- Forwarded by Sean Kennedy/Toronto/IBM on 2013/05/17 11:41 AM -----

From: "Vasaiely, Parham"
To: ,
Date: 2013/05/17 01:08 AM
Subject: [oslc] OSLC Connect 2013 - 1st anual OSLC Event - survey
Sent by: "Community"

Dear OSLC Community members,

The Communications WG, with support from OASIS, is organizing an OSLC event. OSLC Connect 2013 is an inaugural one-day program, scheduled to take place in London this coming fall (Oct dates specifically). The goal of this annual OSLC event is to bring tool providers, end-users and academic partners together. The event will support dissemination, collaboration and develop business cases which result in value for service/tool providers and end-users. The world-wide OSLC community will be invited to submit presentation proposals for committee review. The one-day final program will consist of a combination of submitted presentations and interactive panel sessions. The day will be completed by an optional evening event.

In order to develop some figures about suitable dates and number of participants, we have created a survey, which we would kindly ask you all to conduct. Please also feel free to distribute outside the community list to raise awareness. The survey will end by 24^th May 2013.

http://www.surveymonkey.com/s/LBPYSP8

Kind Regards,
Parham Vasaiely
Project Manager R&D
---------------------------------------------------------------------------------------
EADS UK Ltd.
Engineering & Architecture, Systems and Software Engineering
_______________________________________________ Community mailing list Community@xxxxxxxxxxxxxxxxxhttp://open-services.net/mailman/listinfo/community_open-services.net

From:	Samuel Padgett
To:	Lyo project developer discussions
Cc:	Lyo project developer discussions , lyo-dev-bounces@xxxxxxxxxxx
Date:	20/05/2013 17:19
Subject:	Re: [lyo-dev] Is it the media type: "application/x-oslc-disc-service-provider-catalog+xml" implemented in Lyo?
Sent by:	lyo-dev-bounces@xxxxxxxxxxx

From:	Sergio Jose Deras Arreola/Mexico/IBM
To:	Lyo project developer discussions
Date:	05/20/2013 05:51 PM
Subject:	[lyo-dev] Is it the media type: "application/x-oslc-disc-service-provider-catalog+xml" implemented in Lyo?
Sent by:	lyo-dev-bounces@xxxxxxxxxxx

From:	Maeve O Reilly
To:	Lyo project developer discussions
Cc:	"lyo-dev-bounces@xxxxxxxxxxx"
Date:	21/05/2013 07:19
Subject:	Re: [lyo-dev] Is it the media type: "application/x-oslc-disc-service-provider-catalog+xml" implemented in Lyo?
Sent by:	lyo-dev-bounces@xxxxxxxxxxx


Sean Kennedy
OSLC Community Development Leader for IBM Rational
Operations Coordinator for the OSLC Steering Committee

Phone:	+1-905-413-4385	8200 Warden Ave
Fax:	+1-905-413-4850	Markham, Ontario L6G 1C7
Email:	seanpk@xxxxxxxxxx	D1/R0A/8200/MKM
LinkedIn:	http://www.linkedin.com/in/seanpk	Canada


	OSLC: Lifecycle integration inspired by the web	http://open-services.net
	Eclipse Lyo: Enabling tool integration with OSLC	http://eclipse.org/lyo

There is nothing more powerful than an idea whose time has come. -- Victor Hugo