Issue with Spring-WS 2.0.0-RC2 and JBoss
Hi:
I am using JBoss 4.3.0 with JDK 6. I developed a service with Spring-WS 2.0.0-RC1 which worked fine. I updated my project to use 2.0.0-RC2 and deployed the same service to JBoss this morning to only be rudely greeted by the following stacktrace:
2/31/2010 07:14:04:403 org.springframework.web.servlet.FrameworkServlet [DEBUG] - Could not complete request
java.lang.LinkageError: loader constraint violation: when resolving interface method "javax.xml.soap.SOAPElement.getElementQName()Ljava x/xml/namespace/QName;" the class loader (instance of org/jboss/mx/loading/UnifiedClassLoader3) of the current class, org/springframework/ws/soap/saaj/Saaj13Implementation, and the class loader (instance of <bootloader>) for resolved class, javax/xml/soap/SOAPElement, have different Class objects for the type javax/xml/namespace/QName used in the signature
at org.springframework.ws.soap.saaj.Saaj13Implementat ion.getName(Saaj13Implementation.java:68)
at org.springframework.ws.soap.saaj.SaajSoapMessage.t oString(SaajSoapMessage.java:369)
at java.lang.String.valueOf(String.java:2826)
at java.lang.StringBuilder.append(StringBuilder.java: 115)
at org.springframework.ws.server.MessageDispatcher.re ceive(MessageDispatcher.java:170)
at org.springframework.ws.transport.support.WebServic eMessageReceiverObjectSupport.handleConnection(Web ServiceMessageReceiverObjectSupport.java:88)
at org.springframework.ws.transport.http.WebServiceMe ssageReceiverHandlerAdapter.handle(WebServiceMessa geReceiverHandlerAdapter.java:57)
at org.springframework.ws.transport.http.MessageDispa tcherServlet.doService(MessageDispatcherServlet.ja va:222)
at org.springframework.web.servlet.FrameworkServlet.p rocessRequest(FrameworkServlet.java:644)
at org.springframework.web.servlet.FrameworkServlet.d oPost(FrameworkServlet.java:560)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:717)
at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doF ilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:173)
at org.jboss.web.tomcat.security.SecurityAssociationV alve.invoke(SecurityAssociationValve.java:182)
at org.jboss.web.tomcat.security.JaccContextValve.inv oke(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.CachedConnectionV alve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:241)
at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11Conn ectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run( JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:662)
Any Ideas? I would ordinally do some investigative work on this myself but I am pressed for time to implement the features of my service and don't really want to dive into this right now. I did include a jboss-web.xml into my war that changes the class loading behavior to my WEB-INF/lib first via java2ParentDelegation=true.
Thanks.....
