Why am I getting Exception while executing OSLC properties query on DNG?

G C

(49●1●11) Dec 04 '20, 1:28 a.m.

When I try to execute oslc.properties query with a dcterm and a custom value, I am getting the below error

com.ibm.oslc.query.parser.select.ParseException: Invalid prefix definition: j.0

The query would be like - https://localhost:9090/testserver/resources?oslc.properties=j.0:sample,dcterms:title&oslc.prefix=j.0=<http://localhost:9090/testserver/>,dcterms=<http://purl.org/dc/terms/>

Please let me know how this can be fixed ASAP.

0 votes

Comments

Ian Barnard

FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Dec 04 '20, 7:08 a.m.

I've never seen an OSLC Query for DNG based on something like your URL https://localhost:9090/testserver/resources - was this retrieved from a query capability? Or where else did you get it from? Also what is j.0:sample as a URI - this has to be the URI of an attribute type definition. I'm not sure j.0 is valid as a prefix, try j0 or just j? And what headers are you sending with the GET? It's usually easiest to get your query working the first time by using a REST client like Postman - once it works then apply the same headers/parameters in your code.

G C

Dec 07 '20, 12:37 a.m.

https://localhost:9090/testserver/resources - This is my server URL from where I am getting response using OSLC query. In have my sample response as shown below <dcterms:title rdf:parseType="Literal">Some Title</dcterms:title> <dcterms:identifier rdf:datatype="http://www.w3.org/2001/XMLSchema#string">10</dcterms:identifier> <j.0:sample rdf:datatype="http://www.w3.org/2001/XMLSchema#string">Sample Data</j.0:sample> <j.0:test rdf:datatype="http://www.w3.org/2001/XMLSchema#string">Cake</j.0:test>

Ian Barnard

FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Dec 07 '20, 7:32 a.m.

AFAICT https://localhost:9090/testserver/resources isn't a published OSLC query URL, i.e. it's not in a QueryCapability, so you're unlikely to get any sense out of it using OSLC Query parameters. On my test env the query capability base URL for resources looks like https://jazz.ibm.com:9443/rm/views?oslc.query=true&projectURL=https://jazz.ibm.com:9443/rm/process/project-areas/_DbozQC3oEemAJfncWWzRjA For more details about using OSLC with DOORS Next see https://jazz.net/library/article/1197

Ian Barnard

FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Dec 07 '20, 8:59 a.m.

This is the most likely cause of the exception you're getting. To avoid the exception, use a published QueryCapability urls.

2 answers

5,135 views

0 votes

2 answers

Permanent link

David Honey

FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER (1.8k●1●7) Dec 04 '20, 5:50 a.m.

Are you URL encoding the values for the oslc.properties and oslc.prefix parameters?
URL encoding is required for these because they typically contain characters such as ":", "<", ">" etc.

0 votes

Comments

G C

Dec 07 '20, 12:02 a.m.

I tried encoding as well, but if I encode, I am not getting the filtered results. I am using oslc.properties just because I need only those values in the response specified in the query

Permanent link

David Honey

FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER (1.8k●1●7) Dec 07 '20, 5:32 a.m.

You might try oslc.select instead of oslc.properties. As explained in OSLC Query 3.0 oslc.properties selects properties of the query result container itself, whereas oslc.select selects properties of each member of that container found by the query. For OSLC queries, you almost always want to use oslc.select. While most server implementations that implement OSLC query support oslc.select, many might not support oslc.properties.

0 votes

Comments

G C

Dec 07 '20, 6:01 a.m.

I tried using OSLC select but it is not filtering selected values from the response, my query is like The query would be like - https://localhost:9090/testserver/resources?oslc.select=dcterms:title,j.0:sample

David Honey

FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Dec 07 '20, 6:59 a.m.

I would expect that to fail because: The oslc.select value is not URL encoded and contains ":", and The oslc.select value references the prefix "j.0" which is unlikely to have been defined by default and the URI does not define it using oslc.prefix. As a general principle, it's better to use a meaningful prefix name, and if it's not defined by default, specify oslc.prefix to define it. The known prefixes will be listed on the OSLC service provider using oslc:prefixDefinition. See section 5.2 of https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/discovery.html

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.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers

Answers and Comments

Question details

extending

× 11,106

clm

× 7,622

rational-doors-next

× 6,177

requirements-management-doors-next

× 1,673

elm

× 1,452

Question asked: Dec 04 '20, 1:28 a.m.

Question was seen: 5,135 times

Last updated: Dec 07 '20, 8:59 a.m.

Why am I getting Exception while executing OSLC properties query on DNG?

Comments

2 answers

5,135 views

0 votes

2 answers

Comments

Comments

Your answer

Follow this question

Question details

Related questions