Does DNG REST API intensionally exclude link type DerivedLink in response payload?
I'm trying to access links from DNG to RMM (system defined link name : Refines Architecture Element) using DNG reportable REST APIs. Surprisingly link type 'DerivedLink' is not included in returned response content. where as if i try to request the same URL on browser, response content does have these links included in it.
Note: I have tried setting up exactly same header on REST request as like browser request with no sucess.
My question is, What could be possible root cause REST API return different (content with missing links elements) content than browser for the same request URL?
For a reference XML element of browser response which is missing in REST response.
|
One answer
|
+Update
I further dig into this issue and found that, This issue is somewhere related to HTTPClient. First I used HTTPClient associated with OSLC Client services to execute URL through REST APIs which responded without DerivedLink (Refines Architecture Element) in response content, Then I tried executing same URL by using General org.apache.http.client.HttpClient client and responded with content along with DerivedLink element in it. Same was the case when i access URL on browser.
This is completely weird behavior of REST APIs. Does anyone experience something similar? |
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.