TO access SCM/CM data which is more better Plain Java API's or OSLC API's?
Accepted answer
Hi Vijaya,
I am not sure what you have in your mind, but I think Plain Java is more efficient. Because it have more methods than OSLC services. In terms of execution time, it totally depends on what you are going to do. If you think to follow the OSLC spec (RootSerivice -> Catalog -> Services), Plain Java is more faster and easier to do a same thing.
Comments
I wanted to fetch the Change sets of Component belonging to particular baseline, I have implemented this in Plain Java client libraries, wanted to know is it more efficient using OSLC API's
I wanted to fetch the Change sets of Component belonging to particular baseline, I have implemented this in Plain Java client libraries, wanted to know is it more efficient using OSLC API's
If that's the case, I do believe Plain Java has an advantage because you need to know both OSLC CM and OSLC SCM that are different. I think you are going to a right way.
Thanks for the info and support :)
One other answer
The OSLC Configuration Management API has not yet been approved (it is still in Draft status). RTC does have an implementation of the current draft, but note that it is subject to change (because it has not yet been approved), and note that it only provides access to a relatively small, albeit important, subset of RTC SCM functionality. In particular, the draft does not define access to change sets, so you cannot use the draft specification for the use case you describe.