[closed] Project Area Configuration For OSLC?
Hello
I am running into an issue where I am able to change state transitions via OSLC (cURL PUT) in one Project Area and not the other. Is there any configuration within Project Area which can cause the above behavior?
Worth to mention : The Project Area where OSLC commands are not working was migrated from RTC 3.0.1.3 to RTC 4.0.3 version whereas the Project Area where OSLC commands are working is the one derived from one of the default template which came with RTC 4.0.3
Thanks
K..
The question has been closed for the following reason: "Problem is not reproducible or outdated" by rschoon Mar 29 '23, 2:01 a.m.
One answer
Kartik,
Here are few things to try. I seem to recall the problem is that RTC silently ignores actions it doesn't know about. And the action ids are different from server instance to server instance, even with the same process setup (disclaimer, I'm not in RTC dev and haven't verified this...just wanted to give a couple things to try:
-
Verify the action ids are current for the server+project you are sending the request, namely:
?_action=com.xxx.team.workitem.buildWorkflow.action.a2
or
?_action=storyworkflow.action.a4
-
Change to using OSLC 2.0 style requests, this can be done by setting this header:
OSLC-Core-Version: 2.0
Hopefully someone with a bit more day-to-day hands on with RTC may be able to confirm or deny this.
Comments
Donald Nong
Feb 16 '14, 8:56 p.m.Kartik Manchanda
Feb 16 '14, 9:18 p.m.Kartik Manchanda
Feb 19 '14, 3:26 p.m.Kartik Manchanda
Mar 29 '23, 1:29 a.m.Kartik Manchanda
Feb 19 '14, 3:27 p.m.Steve Speicher
JAZZ DEVELOPER Mar 05 '14, 2:31 p.m.