In the OSLC implementation of IBM Jazz CLM, there are two ways to specify the configuration context, that is, the URI of the configuration the request uses: Using the header “Configuration-Context” or appending the query parameter “oslc_config.context” to the URL.
This last way is not recommended in IBM Jazz CLM since it is not homogeneous between the core CLM apps. For example, in DNG, adding this causes an error when requesting a resource, but in RQM it works as expected.
In the OSLC4J Client library https://github.com/eclipse/lyo.client/tree/master/oslc4j-client, I found the next issues related to this:
- It doesn’t seem possible to add this header inside the OslcClient class (/src/main/java/org/eclipse/lyo/oslc4j/client/OslcClient.java), other than in the getResource method.
- Inside the OSLC Query related classes there doesn’t seem to be a way to add headers or append the “oslc_config.context” parameter.
- In the RmUtil class (/src/main/java/org/eclipse/lyo/oslc4j/client/resources/RmUtil.java) the “typeURI” request fails if the type is in another Configuration
Are OSLC Configurations supported in the OSLC4J Client?
A little bit related to this, there are times where I need to unset the “OSLC-Core” header to access a particular API to manage modules in DNG https://jazz.net/wiki/bin/view/Main/DNGModuleApiOverview. Specifically, instead of that header, I need to set one as “DoorsRP-Request-Type” with value “public 2.0”. Is there a way to do this?