Skip to main content

javax.xml.ws.Response is an interface, and JAXB can't handle interfaces.

No replies
b_wilson
Offline
Joined: 2013-04-30
Points: 0

Hello Everyone

I am running into a brick wall with Glassfish 3.1.2 where I get the following
this problem is related to the following location:
at javax.xml.ws.Response
at public javax.xml.ws.Response com.blah.platform.webservices.importdataservice.jaxws.ImportFileGroupsAsyncResponse._return
at com.blah.platform.webservices.importdataservice.jaxws.ImportFileGroupsAsyncResponse

at com.sun.xml.ws.db.glassfish.JAXBRIContextFactory.newContext(JAXBRIContextFactory.java:101)
at com.sun.xml.ws.spi.db.BindingContextFactory.create(BindingContextFactory.java:182)
at com.sun.xml.ws.model.AbstractSEIModelImpl$1.run(AbstractSEIModelImpl.java:213)
at com.sun.xml.ws.model.AbstractSEIModelImpl$1.run(AbstractSEIModelImpl.java:186)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.xml.ws.model.AbstractSEIModelImpl.createJAXBContext(AbstractSEIModelImpl.java:186)
at com.sun.xml.ws.model.AbstractSEIModelImpl.postProcess(AbstractSEIModelImpl.java:111)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:318)
at com.sun.xml.ws.db.DatabindingImpl.(DatabindingImpl.java:99)
at com.sun.xml.ws.db.DatabindingProviderImpl.create(DatabindingProviderImpl.java:74)
at com.sun.xml.ws.db.DatabindingProviderImpl.create(DatabindingProviderImpl.java:58)
at com.sun.xml.ws.db.DatabindingFactoryImpl.createRuntime(DatabindingFactoryImpl.java:130)
at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:433)
at com.sun.xml.ws.server.EndpointFactory.create(EndpointFactory.java:268)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:145)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:569)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:552)

This is an application that was on Apache Geronimo and worked fine. I placed all the WSDLs in the WSDL directory in the WEB-INF folder and I get the stack trace above. Thie thing to note is that this is an async web service and the continer is choking on the response. The services were created using apache CXF but I wouldnt think that would matter in this case. Any thoughts??

thanks