Access to DOORS computed Attribute via OSLC
I am developing an application to import and export requirements from and to DOORS via OSLC. On import, I get all the real attributes of the requirement as specified by the Instance Shape. My specific case is with respect to Object Number. When I perform a Get Resource for a requirement, I see the "object number" property but it never has a value. I am totally new to DXL but thought I would try a simple script to create an attribute for object number with a DXL script. The documentation seems to indicate that a DXL script is only executed when a view is rendered but given that I am making a call via OSLC and no view is rendered I can understand why no "object number" value in my query result.
So my question is what is the mechanism for getting the value of computed attributes via OSLC? Thanks a million James
|
Accepted answer
Hi James,
I don't know what this object number represents. The absolute number is send as part of GET when I run the lyo client sample http://wiki.eclipse.org/Lyo/BuildClient#DoorsOauthSample I very much doubt you can control it on import though I'm not certain on that.
fyi, the Developer works forum is generally a better place for questions re. DXL and DOORS 9. https://www.ibm.com/developerworks/community/forums/html/forum?id=11111111-0000-0000-0000-000000001527
HTH
Maeve
James Antoine selected this answer as the correct answer
|
One other answer
I assume you refer to DXL Attributes, when you say computed attributes. DXL Attributes are not exposed via OSLC query capability.
Object Number in itself is a "special" attribute - which too isn't exposed via OSLC. A simple GET on a requirement doesn't bring that up.
As Maeve suggests, simple approach really is to create a DXL function that will fetch all the attribute values you need, and make that DXL function as a DXL Service. This service will then appear as a service in the ServiceProviderCatalog.
|
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.