It's all about the answers!

Ask a question

Attribute URI resolving


Kira Resari (412) | asked Aug 17 '20, 1:44 a.m.

Hello,

 

I am stuck on a really difficult problem with DOORS DWA OLSC LYO that I have been spending days to figure out, without any progress.

 

I am trying to read out and map a Requirement using DOORS DWA OSLC LYO in Java. Thus far, I have gotten to the point where I have managed to map the Requirement, as well as most of its attributes.

 

However, a few Attributes are giving me trouble. Specifically ENUMS, and one of which I don't even know the type.

 

Whereas most attributes are of a datatype that I can easily map, these are of the type URI, and contain URIs such as:

 

I want to know how to resolve these URIs. I tried resolving them via `oslcOauthClient.getResource(uri.toString(), mediaType)` trying out the various media types, however...

 

...for the first one (types/attrDef-1025#1) (which I can tell points to the first allowable value of the ENUM that gets mapped as attrDef-1025), the best I can get returned is an XML overview of the Formal Module that the attribute Definition is a part of . It's as if the request is ignoring the trailing `/types/attrDef-1025#1`. That is, these to requests are returning the same entities for me:

 

 

And for the second one (acp), I haven't even been able to find a call that returns me a valid entity. All I tired only results in "NOT_ACCEPTABLE (406)".

 

So, what can I do here?

 

To sum it up again, I have these URIs in `resource.extendedProperties[*].value`

 

 

And I want to convert these URIs into whatever values they actually represent. How can I do that?

 

Thanks in advance,

Kira


P.S.:

I have also tried manually inputting the URLs into a browser. However, entering:

http://localhost:8080/dwa/rm/urn:rational::1-5efc6f9a4ff877cf-M-00000100/types/attrDef-1025#1

...just redirects me to

http://localhost:8080/dwa/rm/urn:rational::1-5efc6f9a4ff877cf-M-00000100

And entering:

http://localhost:8080/dwa/rm/acp/urn:rational::1-5efc6f9a4ff877cf-F-00000000/gFgcK1req0%252BQ5gE6yE5YsEZZcDI%253D%250A

...just gives me the same old "NOT_ACCEPTABLE (406)" response displayed in the browser.

Be the first one to answer this question!


Register or to post 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.