OSLC-QM: Missing essential classes and members
Hi,
we are currently interfacing RQM via oslc4j and are facing some problems with it. Basically there are two major problems bothering us:
1) Essential classes are entirely missing in the oslc4j interface. There are, for example, no classes for creating or querying TestSuites, TestSuiteExecutionRecords or TestSuiteResults.
2) If there are classes predefined, some essential properties of the resources are not available over oslc at all. For example there seems to be no way for accessing the testphase/iteration of a TestExecutionRecord or no details of a TestResult.
Since we are able to extend oslc4j, we can live with the first issue. Nevertheless, its kind of annoying that those resources cannot be addressed over oslc4j by default. Why is that so?
The second point is the more crucial, because there seems to be no way for addressing the information via oslc AT ALL. And therefore we are forced to implement a client simultaneously interfacing oslc AND the restfull api. On the other hand we cannot use ONLY the restfull api since we are depending on oslc-ids for other purposes.
So, long story short, the question is: Is there any development on the oslc backend going on at the moment? Is there a chance that some day soon the oslc api has the same power as the restfull api? Or is there some best practise for accessing elements not available over oslc?
Thanks and kind regards,
René Grellert
One answer
Hi René,
For #1, please post to the Eclipse Lyo project (http://eclipse.org/lyo) that owns this library.
For #2, we have made progress in aligning the RQM OSLC QM API with the RQM Reportable REST API. However, there are still gaps. Don's post on the Plain Old XML (POX) Profile Requests is intended to assist in this scenario. Are there specific resources/properties you require? What RQM version are you using?
Comments
Donald Nong
Mar 21 '17, 10:10 p.m.I notice this section in the document.
Plain Old XML (POX) Profile Requests
The OSLC QM V2 API supports Plain Old XML (POX) profile requests1. POX profile requests are redirected (
302 Found/Moved Temporarily) to the RQM Reportable REST API.1 Rational Quality Manager 6.0.2+
So it appears that you can "mix" OSLC and reportable REST API together. Is it something you have been doing already?
The Knowledge Center does show that the OSLC capability is limited to selected artifact types only, probably only those defined in the QM OSLC spec.
https://jazz.net/help-dev/clm/topic/com.ibm.rational.test.qm.doc/topics/r_rqm_provider.html