Re: [lyo-dev] Is it the media type: "application/x-oslc-disc-service-pro

[Sergio Jose Deras Arreola/Mexico/IBM <sderas@xxxxxxxxxxx>]

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):
<?xml version="1.0" encoding="UTF-8"
?>
<rdf:RDF>
 <oslc:ServiceProviderCatalog rdf:about="https://<host>:9443/ccm/oslc/workitems/catalog">
...
</oslc:ServiceProviderCatalog>
</rdf:RDF>

DOORS (xml):
<?xml version="1.0"?>
  <oslc_disc:ServiceProviderCatalog
rdf:about="https://<host>:8443/dwa/rm/discovery/catalog">
  ...
  </oslc_disc:ServiceProviderCatalog>

While the OSLC4JBugzilla catalog starts
to describe the nodes immediately:

OSLC4JBugzilla (rdf+xml):
<?xml version="1.0" encoding="UTF-8"
?>
<rdf:RDF>
...
        <rdf:Description rdf:about="http://<host>: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 <spadgett@xxxxxxxxxx>
To:	Lyo project developer discussions <lyo-dev@xxxxxxxxxxx>
Cc:	Lyo project developer discussions <lyo-dev@xxxxxxxxxxx>, 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 <sderas@xxxxxxxxxxx>
To:	Lyo project developer discussions <lyo-dev@xxxxxxxxxxx>
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@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/lyo-dev

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