0 Replies Latest reply on Nov 30, 2004 9:08 AM by Stacy Johnson

    Castor version conflict

    Stacy Johnson Newbie

      When trying to move a war from JBoss 3.2.3 to 3.2.6, we get the following error when the server tries to return a message to the client

      java.lang.NoSuchMethodError: org.exolab.castor.xml.Unmarshaller.unmarshal(Ljava/lang/Class;Lorg/w3c/dom/Node;)Ljava/lang/Object;
      org.apache.axis.encoding.ser.castor.CastorDeserializer.onEndElement(CastorDeserializer.java:62)
      org.apache.axis.encoding.DeserializerImpl.endElement(DeserializerImpl.java:534)
      org.apache.axis.encoding.DeserializationContextImpl.endElement(DeserializationContextImpl.java:1015)
      org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:204)
      org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:722)
      org.apache.axis.message.RPCElement.deserialize(RPCElement.java:233)
      org.apache.axis.message.RPCElement.getParams(RPCElement.java:347)
      org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:184)
      org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:333)
      org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
      org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
      org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
      org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:481)
      org.apache.axis.server.AxisServer.invoke(AxisServer.java:323)
      org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:854)
      javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
      org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:339)
      javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
      org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)

      This reads as a classpath problem, but even when I remove the castor.jar that comes with JBoss 3.2.6 and replace with ours, the problem persists. It should be noted that everything works fine in 3.2.3 and it comes with the same jar as is in 3.2.6, so classpath ordering must have changed since the 3.2.3 release.