You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by kdesin <ka...@gmail.com> on 2013/05/03 16:49:33 UTC
Problems with CXF2.6.1 and jbossws-native-saaj.jar
Hi all,
We are trying to co-exist jbossws (on jboss-4.2.3GA) and Apache CXF 2.6.1.
The problem is arising when we keep the jbossws-native-saaj.jar in the
jboss/lib/endorsed folder ,the SOAPMessage.class when it is trying to
resolve the implemetor ,it is taking from jbossws-native-saaj.jar instead of
the CXF saaj jars.
We cannot migrate the jbossws service to CXF due to some client
restrictions.Kindly provide any pointers which can help.
Saludos
Kartheek
-----
Saludos
Kartheek
--
View this message in context: http://cxf.547215.n5.nabble.com/Problems-with-CXF2-6-1-and-jbossws-native-saaj-jar-tp5727143.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Problems with CXF2.6.1 and jbossws-native-saaj.jar
Posted by Daniel Kulp <dk...@apache.org>.
As Alessio mentioned….. CXF isn't even in that stack trace you provided. You're not even ending up using CXF at all. If the intention is to be using CXF, that's the first issue you need to resolve.
That said, most likely you can remove the SAAJ impl and saaj-api jars we provide and use the container provided versions. When running in J2EE container, the container does provide those and thus, you don't need to add them to the war/ear.
Dan
On May 3, 2013, at 11:22 AM, kdesin <ka...@gmail.com> wrote:
> Thanks Alessio. None of the versions we can change now per the client
> requirements but can you please tell if there is a way to instruct CXF to
> use it's own saaj implementation (sun) and Jbossws to use it's own native
> libraries?
>
> What you have detailed is correct,it is coming because the endorsed folder
> jar was taking precedence before coming to the CXF specific saaj lib in the
> cxfwar-specif lib.Is there a way to separate these out and let them work
> parallely as the native-saaj is required for the JBOSS-WS hosted service
>
>
> Saludos
> Kartheek
>
>
>
>
> -----
> Saludos
> Kartheek
> --
> View this message in context: http://cxf.547215.n5.nabble.com/Problems-with-CXF2-6-1-and-jbossws-native-saaj-jar-tp5727143p5727150.html
> Sent from the cxf-user mailing list archive at Nabble.com.
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: Problems with CXF2.6.1 and jbossws-native-saaj.jar
Posted by kdesin <ka...@gmail.com>.
Thanks Alessio. None of the versions we can change now per the client
requirements but can you please tell if there is a way to instruct CXF to
use it's own saaj implementation (sun) and Jbossws to use it's own native
libraries?
What you have detailed is correct,it is coming because the endorsed folder
jar was taking precedence before coming to the CXF specific saaj lib in the
cxfwar-specif lib.Is there a way to separate these out and let them work
parallely as the native-saaj is required for the JBOSS-WS hosted service
Saludos
Kartheek
-----
Saludos
Kartheek
--
View this message in context: http://cxf.547215.n5.nabble.com/Problems-with-CXF2-6-1-and-jbossws-native-saaj-jar-tp5727143p5727150.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Problems with CXF2.6.1 and jbossws-native-saaj.jar
Posted by Alessio Soldano <as...@redhat.com>.
JBoss AS 4.2.3 was released on July *2008*, it's probably time to move
to something recent...
The exception you're getting basically says that the jbossws-native
jaxws impl is not able to work with the saaj-ri (as it was meant to run
with its own jbossws-native-saaj instead). Depending on what you're
trying to achieve, the problem might even be that you're not using the
jaxws impl you're actually expecting to use (cxf one perhaps).
It's really a matter of classloading setup, the jars in lib/endorsed
control the jaxws and saaj factories through service api resolution.
Alessio
On 05/03/2013 04:49 PM, kdesin wrote:
> Hi all,
>
> We are trying to co-exist jbossws (on jboss-4.2.3GA) and Apache CXF 2.6.1.
> The problem is arising when we keep the jbossws-native-saaj.jar in the
> jboss/lib/endorsed folder ,the SOAPMessage.class when it is trying to
> resolve the implemetor ,it is taking from jbossws-native-saaj.jar instead of
> the CXF saaj jars.
>
> We cannot migrate the jbossws service to CXF due to some client
> restrictions.Kindly provide any pointers which can help.
>
> Saludos
> Kartheek
>
>
>
> -----
> Saludos
> Kartheek
> --
> View this message in context: http://cxf.547215.n5.nabble.com/Problems-with-CXF2-6-1-and-jbossws-native-saaj-jar-tp5727143.html
> Sent from the cxf-user mailing list archive at Nabble.com.
--
Alessio Soldano
Web Service Lead, JBoss
Re: Problems with CXF2.6.1 and jbossws-native-saaj.jar
Posted by kdesin <ka...@gmail.com>.
Here is the stack trace:
2013-05-03 07:00:14,136 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS]
SOAP request exception
java.lang.ClassCastException:
com.sun.xml.messaging.saaj.soap.ver1_1.Envelope1_1Impl
at
org.jboss.ws.core.soap.SOAPEnvelopeImpl.<init>(SOAPEnvelopeImpl.java:59)
at
org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:125)
at
org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:97)
at
org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:255)
at
org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:179)
at
org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:192)
at
org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:502)
at
org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at
org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:543)
at
atg.support.SecureSessionCookieValve.invoke(SecureSessionCookieValve.java:17)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
com.redhat.jboss.support.ConfigureSessionCookieValve.invoke(ConfigureSessionCookieValve.java:37)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at
org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437)
at
org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
2013-05-03 07:00:14,138 ERROR
[org.jboss.ws.core.server.AbstractServiceEndpointServlet] Error processing
web service request
java.lang.ClassCastException:
com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl
at
org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:235)
at
org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:164)
at
org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104)
at
org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:659)
at
org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:224)
at
org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:502)
at
org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at
org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:543)
at
atg.support.SecureSessionCookieValve.invoke(SecureSessionCookieValve.java:17)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
com.redhat.jboss.support.ConfigureSessionCookieValve.invoke(ConfigureSessionCookieValve.java:37)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at
org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437)
at
org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
2013-05-03 07:00:14,138 ERROR [org.apache.catalina.core.ContainerBase]
Servlet.service() for servlet ChaseService threw exception
java.lang.ClassCastException:
com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl
at
org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:235)
at
org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:164)
at
org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104)
at
org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:659)
at
org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:224)
at
org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:502)
at
org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at
org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:543)
at
atg.support.SecureSessionCookieValve.invoke(SecureSessionCookieValve.java:17)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
com.redhat.jboss.support.ConfigureSessionCookieValve.invoke(ConfigureSessionCookieValve.java:37)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at
org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437)
at
org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
-----
Saludos
Kartheek
--
View this message in context: http://cxf.547215.n5.nabble.com/Problems-with-CXF2-6-1-and-jbossws-native-saaj-jar-tp5727143p5727144.html
Sent from the cxf-user mailing list archive at Nabble.com.