How to return linked resource properties with REST API or OSLC calls
Hi,
|
2 answers
You're using application/rdf+xml in the Content-Type for a GET. It should be Accept: application/rdf+xml and no Content-Type. GET does not have an entity request body. Comments
Masizane Marivate
commented Mar 26 '18, 12:57 p.m.
Hi Jim,
|
I think you're missing the prefix definitions. Comments
Masizane Marivate
commented Mar 26 '18, 1:05 p.m.
Does one still have to include prefix definitions for dcterms:title even if all the other resources have it and return it?
Masizane Marivate
commented Mar 27 '18, 6:36 a.m.
I also added the rqm prefix, and still the testplan and test case resource properties are not returned.
Masizane Marivate
commented Mar 28 '18, 4:37 a.m.
on further investigation "http://jazz.net/ns/qm/rqm#" returns a 404 page not found error. perhaps this is the source of the problem?
|
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.
Comments
I can see the same symptom, and will give you more details if I can figure it out.
If I read the document correctly, only two artifact types will give you the embedded referenced resource properties, with limitation.
https://jazz.net/wiki/bin/view/Main/RqmApi#Embedded_referenced_resource_pro
(but I can't get it to work for the two types mentioned in the document)
The OSLC API lacks behind in terms of implementation compared to the REST API, and I doubt that it provide such capability either.
https://jazz.net/wiki/bin/view/Main/RqmOslcQmV2Api
Hi Donald,
My queries, either RTP or OSLC, are looking up testcase/testscript/testplan and execution results, of which only the last one is not listed as a primitive property. Further still i'm initially only trying to get simple embedded info, like title/and shortId(webId). I've followed the documentation examples and guidelines however it doesn't seem to be working as expected.
Also.. I have surprisingly gotten further with OSLC than I have with REST API:
you must change header to:
accept: "application/atom+xml
this will return nested properties for testscript and testexecutionresult. however the testplan and testcase properties are not nested.
If you search for the execution result and requested nested properties for the testcase, tesplan, testscript,testexecution record, weirdly enough testcase and testplan nested properties are returned but testscript and testexecution record are not returned