Bug 522235 - OSLC Query does not work correctly when Global Configuration is enabled in DNG
Summary: OSLC Query does not work correctly when Global Configuration is enabled in DNG
Status: NEW
Alias: None
Product: Lyo
Classification: Technology
Component: Client (show other bugs)
Version: 2.2.0   Edit
Hardware: PC Windows 7
: P3 minor (vote)
Target Milestone: 2.x.x   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-13 08:29 EDT by Massimo Caprinali CLA
Modified: 2017-11-06 12:03 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Massimo Caprinali CLA 2017-09-13 08:29:11 EDT
Using DNG Query capability we are not able to retrieve Requirements.

I think the problem is the query capability url.

When GC is enabled the query capability url is:

https://<host>:<port>/rm/views?oslc.query=true&projectURL=<project_area_url>&vvc.configuration=<stream_url> so there is the parameter vvc.configuration

this url is not contained in the RDF Triples. For example the Predicate is http://www.w3.org/2000/01/rdf-schema#member, the Subject is https://<host>:<port>/rm/views?oslc.query=true&projectURL=<project_area_url>, without  vvc.configuration parameter.

In class OslcQueryResult, the method initializeRdf() set membersResource = rdfModel.getResource(query.getCapabilityUrl()); but in the model there isn't memeber resource with "query.getCapabilityUrl()" subject.

so rdfModel.listStatements(select) is empty in method getMembersUrls()

Removing vvc.configuration from capability url, all works correctly.
Comment 1 Andrii Berezovskyi CLA 2017-11-06 11:58:06 EST
Hi Massimo,

Sorry for a delay in my reply. Have you already resolved the issue? As far as I recall from some SO questions, it is Doors' limitation as vvc.configuration query parameter is not supposed to be used with OSLC query.

Anyway, Jim (CC) knows much better about this.

/Andrew
Comment 2 Andrii Berezovskyi CLA 2017-11-06 12:03:45 EST
I am setting a 'minor' priority as it's not an issue from the Lyo SDK side, but from the IBM Doors' side.