Description Michael Fiedler 2011-09-20 07:55:20 EDT

Build Identifier: 

Investigate a possible regression in the test suite.   


Trying to get CM tests to run well against the ref implementation and hitting an issue.  Might have to discuss directly, but am
documenting it here for followup.

For RTC, the serviceProvider entry in the ServiceProviderCatalog looks like this:

<oslc:serviceProvider>
	<oslc:ServiceProvider rdf:about="https://rqmx64e.rtp.raleigh.ibm.com:9443/ccm/oslc/contexts/_GhH_MtlrEeCqjb8y_rUpVQ/workitems/services.xml">
		<dcterms:title rdf:parseType="Literal">JKE Banking (Change Management)</dcterms:title>
		<oslc:details rdf:resource="https://rqmx64e.rtp.raleigh.ibm.com:9443/ccm/process/project-areas/_GhH_MtlrEeCqjb8y_rUpVQ"/>
		<ns1:consumerRegistry rdf:resource="https://rqmx64e.rtp.raleigh.ibm.com:9443/ccm/process/project-areas/_GhH_MtlrEeCqjb8y_rUpVQ/links"/>
	</oslc:ServiceProvider>
</oslc:serviceProvider>

The ServiceProvider about URI points to a document with a toplevel oslc:ServiceProvider element which contains multiple oslc:service entries.



For the CM ref implementation the entry in the ServiceProviderCatalog looks like this:

<oslc:serviceProvider rdf:resource="http://localhost:8080/rio-cm/services"/>

This points to a document with a toplevel oslc:ServiceProvider element which contains an oslc:service entry.


The CM testcases are not running well against the ref implementation because they expect the catalog to contain a ServiceProvider entry with an about property.
The ref implementation contains the rdf:resource entry instead.  


Reproducible: Always

Steps to Reproduce:
1. Start CM RIO
2. Run the Test-CM RIO test suite

Several tests will fail to run due to the inability to get the ServiceProvider document.