Unknown JAXBContext implementation

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Unknown JAXBContext implementation

forums
Hi, I get the following exception using jax-ws 2.2.7 combined with jdk
1.7.0_09 when programmatically throwing a SOAPFaultException: Unknown
JAXBContext implementation: class
com.sun.xml.internal.bind.v2.runtime.JAXBContextImpl (see complete stack
trace at the end of the message) The "com.sun.xml.internal.bind" package is
part of the bundled jaxb-api in jdk 7, whereas the jax-ws implementation uses
"com.sun.xml.bind" . So there must be a conflict between both jaxb versions.
Putting the jax-ws "jaxb-api.jar" and "jaxws-api.jar" into the java endorsed
dir did not help. Same exception occured. Any request without
programmatically throwing an exception works as expected .. Any hints
appreciated. Complete stack trace:
com.sun.xml.ws.handler.SOAPHandlerProcessor insertFaultMessage SEVERE:
exception while creating fault message in handler chain
com.sun.xml.ws.spi.db.DatabindingException: Unknown JAXBContext
implementation: class com.sun.xml.internal.bind.v2.runtime.JAXBContextImpl at
com.sun.xml.ws.spi.db.BindingContextFactory.getJAXBFactory(BindingContextFactory.java:207)
at
com.sun.xml.ws.spi.db.BindingContextFactory.create(BindingContextFactory.java:149)
at com.sun.xml.ws.message.jaxb.JAXBMessage.create(JAXBMessage.java:161) at
com.sun.xml.ws.fault.SOAPFaultBuilder.createSOAP11Fault(SOAPFaultBuilder.java:423)
at
com.sun.xml.ws.fault.SOAPFaultBuilder.createSOAPFaultMessage(SOAPFaultBuilder.java:165)
at com.sun.xml.ws.api.message.Messages.create(Messages.java:433) at
com.sun.xml.ws.handler.SOAPHandlerProcessor.insertFaultMessage(SOAPHandlerProcessor.java:95)
at
com.sun.xml.ws.handler.HandlerProcessor.callHandlersRequest(HandlerProcessor.java:146)
at
com.sun.xml.ws.handler.ServerSOAPHandlerTube.callHandlersOnRequest(ServerSOAPHandlerTube.java:138)
at com.sun.xml.ws.handler.HandlerTube.processRequest(HandlerTube.java:127) at
com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063) at
com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979) at
com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950) at
com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825) at
com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:380) at
com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:651)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:264) at
com.sun.xml.ws.transport.http.servlet.ServletAdapter.invokeAsync(ServletAdapter.java:218)
at
com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doGet(WSServletDelegate.java:159)
at
com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:194)
at com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:192)
at
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:245)
at
de.intermediate.components.server.ReloadingClassFilter.doFilter(ReloadingClassFilter.java:44)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:929)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:405)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:964)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:515)
at
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:302)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722) jax-ws version: 2.2.7 jdk: 1.7.0_09
Thanks, Alex

--

[Message sent by forum member 'alexschmidt']

View Post: http://forums.java.net/node/893038


Reply | Threaded
Open this post in threaded view
|

Re: Unknown JAXBContext implementation

blair424
Did you find a fix for this problem? I'm seeing exactly the same thing. Thanks!
Reply | Threaded
Open this post in threaded view
|

Re: Unknown JAXBContext implementation

yaroska
Hi,

recently I’ve made some related changes in the code.

You can wait until it will be promoted to metro.
Or you can build it by yourself.

git://java.net/jax-ws~git


Yarda

> On 13 May 2015, at 20:56, blair424 <[hidden email]> wrote:
>
> Did you find a fix for this problem? I'm seeing exactly the same thing.
> Thanks!
>
>
>
> --
> View this message in context: http://metro.1045641.n5.nabble.com/Unknown-JAXBContext-implementation-tp5710095p5710483.html
> Sent from the Metro - Users mailing list archive at Nabble.com.