It's all about the answers!

Ask a question

Update a requirement in RRC 4.0 through REST API

Arnaud Bouzy (2324) | asked Jun 22 '12, 12:31 p.m.
edited Jun 22 '12, 12:48 p.m.
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>
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 ?


2 answers

permanent link
Arnaud Bouzy (2324) | answered Jun 25 '12, 9:05 a.m.
Found !
It is corrected in the GA release.

permanent link
helene højrup (231912) | answered Apr 11 '13, 6:56 a.m.
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?

Arnaud Bouzy commented Jun 19 '13, 6:31 a.m. | edited Jun 19 '13, 6:32 a.m.

 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 to post your answer.