Error in making a POST call to DOORS[9.6] via RTC[5.0.2] follow-up operation.
Hello Everyone,
We are looking to transfer data from RTC to DOORS through a custom follow-up operation. This operation participant will make a POST call to the DOORS server to create an object in a particular module.
While executing this feature we get an exception thrown while making a POST call to the DOORS system.
The line in which the exception is getting thrown is:
ClientResponse creationResponse = client.createResource(
requirementFactory, requirement,
OslcMediaType.APPLICATION_RDF_XML,
OslcMediaType.APPLICATION_RDF_XML);
The stack trace of the exception is as follows:
org.apache.wink.client.ClientRuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: javax.ws.rs.WebApplicationException: java.lang.ClassCastException: org.apache.xalan.processor.TransformerFactoryImpl incompatible with javax.xml.transform.TransformerFactory
at org.apache.wink.client.internal.ResourceImpl.invoke(ResourceImpl.java:240)
at org.apache.wink.client.internal.ResourceImpl.invoke(ResourceImpl.java:189)
at org.apache.wink.client.internal.ResourceImpl.invokeNoException(ResourceImpl.java:181)
at org.apache.wink.client.internal.ResourceImpl.post(ResourceImpl.java:322)
at org.eclipse.lyo.client.oslc.OslcOAuthClient.createResource(OslcOAuthClient.java:186)
at com.daimler.stan.doorsclient.CrAdapter.transferDatatoCr(CrAdapter.java:204)
at com.daimler.stan.changerequest.CrDoorsAdapter.run(CrDoorsAdapter.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Any Suggestions on how to handle this exception.
Thanks in Advance.
Abhishek Kumar
One answer
I don't know about your error. I would start by looking at the https://wiki.eclipse.org/Lyo/BuildClient#DoorsOauthSample there is java code with a sample that creates a requirement in DOORS 9.
For debugging, if you refer to your logs in DWA/server/festival/logs they can be helpful. You can get more detailed logging by replacing festival\config\festival-log4j.xml with festival-log4j.xml.support and restarting DWA.
HTH
Maeve
For debugging, if you refer to your logs in DWA/server/festival/logs they can be helpful. You can get more detailed logging by replacing festival\config\festival-log4j.xml with festival-log4j.xml.support and restarting DWA.
HTH
Maeve