OSLC RM API
I have requirement artifact uri
https://localhost:9443/rm/resources/_5b8b8a809b134f3bbe48d08f24d7176d
I want to find the title and its id using OSLC API. I was able to find the both them for the 5.0.1 RM application when i try to run same code for another requirement artifact in RM 6.0 it is not working.
I am not able to understand why it is behaving this way for different versions of CLM.
|
3 answers
Hi, do you do an OSLC GET to the resource URI or an OSLC query ?
Comments
vijayakumar ramesh
commented Nov 04 '15, 10:26 a.m.
I do the OSLC GET to the resource URI
Sample code
// Setup the HttClient
DefaultHttpClient httpclient = new DefaultHttpClient();
HttpUtils.setupLazySSLSupport(httpclient);
// Setup the rootServices request
HttpGet rootServiceDoc = new HttpGet(rootServices);
rootServiceDoc.addHeader("Accept", "application/rdf+xml");
rootServiceDoc.addHeader("OSLC-Core-Version", "2.0");
Gabriel Ruelas
commented Nov 04 '15, 10:29 a.m.
What is the error /output ? Have you checked the rm.log in the server?
Gabriel Ruelas
commented Nov 04 '15, 10:30 a.m.
What is the error /output ? Have you checked the rm.log in the server?
vijayakumar ramesh
commented Nov 10 '15, 6:08 a.m.
Actually I am not getting error but response what I am getting programatically when I call the GET is different from one I get the response in the browser REST Client. |
Has this artifact a link to an artifact of another Project Area?
If you don't need the the link information, than add nolinks=true to you call Otherwise you have to support me on the defect https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/101650 Thank you Comments
vijayakumar ramesh
commented Nov 10 '15, 6:13 a.m.
This artifact doesn't have link to another artifact. |
Hello
Since you don't provide any details, I can only speculate that you are not specifying the required http headers when using the REST client (as you are doing int he programmatic case). Can you confirm? For me to be able to help you further, please post the expected and actual responses. cheers
ps. the suggestion to use "nolinks=true" should be disregarded; this is not a valid query parameter in OSLC protocols.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.