REST API loses attachment reference
Hi,
I've got the xml for a specific Test Case from RQM using the REST API. The Test Case in question has an attachment (so the attachment element in the retrieved xml is populated).
I've then put that xml back up to the server using the REST API and the PUT method. I get a 200 success status back and the Test Case has been updated but the Test Case no longer has an attachment linked.
The Test Case has definitely been updated (as I've tested changing the title in the xml before putting it back to the server). The xml is correct as I'm using the message I've gotten from the server so it looks like the REST API is just ignoring the attachment element.
Has anyone else experienced this? Looks like it could be a defect.
Cheers, Cliff
I've got the xml for a specific Test Case from RQM using the REST API. The Test Case in question has an attachment (so the attachment element in the retrieved xml is populated).
I've then put that xml back up to the server using the REST API and the PUT method. I get a 200 success status back and the Test Case has been updated but the Test Case no longer has an attachment linked.
The Test Case has definitely been updated (as I've tested changing the title in the xml before putting it back to the server). The xml is correct as I'm using the message I've gotten from the server so it looks like the REST API is just ignoring the attachment element.
Has anyone else experienced this? Looks like it could be a defect.
Cheers, Cliff
One answer
We got an error in the SystemLog with a WARN about not being able to associate the attachment to the Test Case.
The details for the error were:
com.ibm.ws.webcontainer.servlet.exception.NotargetForURIException: No target servlet configured for uri: /(unknown)
Potentially a WAS configuration problem?
Cheers, Cliff
The details for the error were:
com.ibm.ws.webcontainer.servlet.exception.NotargetForURIException: No target servlet configured for uri: /(unknown)
Potentially a WAS configuration problem?
Cheers, Cliff