Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Update a requirement in RRC 4.0 through REST API

In an existing requirement, I need to add a traceability link to a test case.
This implies to create a relationship in both directions.
Creating the TC to Req "validatesRequirement" links works fine via a PUT
But the other way around doesn't: I get an error code 400: Bad Request anytime, even if I don't change anything in the content retrieved from a previous GET.
I guess there is something wrong the my headers, but I don't know what
PUT to requirement address: https:://host:9443/rm/resource/<theid>
Headers:
If-Match:&lt;the ETag got previously&gt;
Content-Type: application/rdf+xml
OSLC-Core-Version: 2.0

Content: well, just the one got from the previous GET...or the modified one give the same error

the rm.log file displays an RRSException in OSLC20ContentHandler.updateRequirementResource

This is run under RRC 4.0 RC3

Any help ?

Thanks

0 votes



2 answers

Permanent link
Found !
It is corrected in the GA release.

2 votes


Permanent link
I'm having the same problem?! I'm a newbee what is the GA release, and what is that I should do to solve this problem?

0 votes

Comments

 GA stands for General Availability (RC is for Release Candidate). The GA is the "official" release deployable for any customer after some validations, after a certain number of RCs.

If you are experiencing this now, it is probably due to another reason, the GA was released in 2012...

Your answer

Register or log in 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.

Search context
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
× 516
× 479

Question asked: Jun 22 '12, 12:31 p.m.

Question was seen: 5,284 times

Last updated: Jun 19 '13, 6:32 a.m.

Confirmation Cancel Confirm