Results 1 to 8 of 8

Thread: Spring WS tutorial sample issues

  1. #1
    Join Date
    Jul 2005
    Location
    Zagreb, Croatia
    Posts
    69

    Default Spring WS tutorial sample issues

    Hello all...

    First of all, Arjen, congrats on a job well done, as far as i can see SWS 1.5 will be a great piece of software (JMS transport is what i'll be using and evaluating the most....)...

    Now for some bitter stuff...

    I'm trying to run the tutorial sample (modified in such a way that it uses the marshalling endpoint and JMS transport)....
    My environment is:
    - WAS 6.1
    - IBM Java 1.5 (build&runtime)
    - WAS-MQ 6.0
    - running with application classloader first
    - classpath as follows:
    Code:
    castor-1.1.1.jar
    commons-logging-1.1.1.jar
    log4j-1.2.14.jar
    servlet-api-2.5.jar
    spring-beans-2.0.7.jar
    spring-context.jar
    spring-core-2.0.7.jar
    spring-dao.jar
    spring-jms-2.0.7.jar
    spring-oxm-1.5.0-m1.jar
    spring-web-2.0.7.jar
    spring-ws-1.5.0-m1.jar
    spring-ws-core-1.5.0-m1.jar
    spring-xml-1.5.0-m1.jar
    stax-1.2.0.jar
    stax-api-1.0.1.jar
    wsdl4j-1.6.1.jar
    The issue is this:
    When i try to run the sample i get this in my log:
    Code:
    [11/12/07 14:55:44:164 CET] 00000031 WebExtensionP W   Servlet springws is currently unavailable: SRVE0203E: Servlet [springws]: org.springframework.ws.transport.http.MessageDispatcherServlet was found, but is missing another required class.
    SRVE0206E: This error typically implies that the servlet was originally compiled with classes which cannot be located by the server.
    SRVE0187E: Check your classpath to ensure that all classes required by the servlet are present.SRVE0210I: This problem can be debugged by recompiling the servlet using only the classes in the application's runtime classpath
    Any insight would be appreciated...I'm probably missing something obvious...

    Thanks in advance!

  2. #2
    Join Date
    Jul 2005
    Location
    Rotterdam, the Netherlands
    Posts
    1,562

    Default

    Thanks!

    As for the issue: it's really hard to figure out what is missing without having a class name or something. I have no idea if WebSphere logging can be increased, so that we can actually determine the missing class. Otherwise, what you can do, is try to deploy the same warfile on something like Tomcat, and see if it gives more verbose info.
    Arjen Poutsma

    Spring Web Services Dev Lead
    Please read the FAQ

  3. #3
    Join Date
    Jul 2005
    Location
    Zagreb, Croatia
    Posts
    69

    Default

    Quote Originally Posted by Arjen Poutsma View Post
    Thanks!

    As for the issue: it's really hard to figure out what is missing without having a class name or something. I have no idea if WebSphere logging can be increased, so that we can actually determine the missing class. Otherwise, what you can do, is try to deploy the same warfile on something like Tomcat, and see if it gives more verbose info.
    Hi..managed to work around that issue..it was a classpath problem...

    I do have a new issue

    I'm using the
    Code:
     org.springframework.ws.wsdl.wsdl11.builder.XsdBasedSoap11Wsdl4jDefinitionBuilder
    to publish my wsdl. When i change the locationUri property value, my changes get saved, my app gets republished successfully...but...when i try to see my wsdl (with my locationUri changes) i get a generic:
    Code:
    Error 500: SRVE0207E: Uncaught initialization exception thrown by servlet
    with the trace:
    Code:
    [12/12/07 17:47:47:374 CET] 00000049 WebApp        E   [Servlet Error]-[springws]: java.lang.VerifyError: javax/xml/xpath/XPath.setNamespaceContext(Ljavax/xml/namespace/NamespaceContext;)V
    	at org.springframework.xml.xpath.Jaxp13XPathExpressionFactory.createXPathExpression(Jaxp13XPathExpressionFactory.java:80)
    	at org.springframework.xml.xpath.XPathExpressionFactory.createXPathExpression(XPathExpressionFactory.java:86)
    	at org.springframework.ws.transport.http.WsdlDefinitionHandlerAdapter.afterPropertiesSet(WsdlDefinitionHandlerAdapter.java:142)
    	at org.springframework.ws.transport.http.MessageDispatcherServlet.initWsdlDefinitionHandlerAdapter(MessageDispatcherServlet.java:288)
    	at org.springframework.ws.transport.http.MessageDispatcherServlet.initFrameworkServlet(MessageDispatcherServlet.java:203)
    	at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:237)
    	at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:126)
    	at javax.servlet.GenericServlet.init(GenericServlet.java:256)
    ....
    ....
    ....
    ....
    I need to restart my appserver, and after the restart, i can see my changed wsdl...

    Ideas?

    Thanks in advance!

  4. #4
    Join Date
    Dec 2005
    Posts
    24

    Default Same problem here

    Has anyone encountered this problem and fixed it? This occurs when I set the transformlocation property in web.xml I believe it is related to WSDL4J. There's gotta be a way to overcome this, can Spring ws use another implmentation othen than Jaxp13XPathExpressionFactory? I think it's trying to use a class that is newer than the one Websphere loaded, but I'm unsure which it is.

  5. #5
    Join Date
    Nov 2008
    Posts
    1

    Default

    Quote Originally Posted by miha View Post
    Hi..managed to work around that issue..it was a classpath problem...

    I do have a new issue

    I'm using the
    Code:
     org.springframework.ws.wsdl.wsdl11.builder.XsdBasedSoap11Wsdl4jDefinitionBuilder
    to publish my wsdl. When i change the locationUri property value, my changes get saved, my app gets republished successfully...but...when i try to see my wsdl (with my locationUri changes) i get a generic:
    Code:
    Error 500: SRVE0207E: Uncaught initialization exception thrown by servlet
    with the trace:
    Code:
    [12/12/07 17:47:47:374 CET] 00000049 WebApp        E   [Servlet Error]-[springws]: java.lang.VerifyError: javax/xml/xpath/XPath.setNamespaceContext(Ljavax/xml/namespace/NamespaceContext;)V
    	at org.springframework.xml.xpath.Jaxp13XPathExpressionFactory.createXPathExpression(Jaxp13XPathExpressionFactory.java:80)
    	at org.springframework.xml.xpath.XPathExpressionFactory.createXPathExpression(XPathExpressionFactory.java:86)
    	at org.springframework.ws.transport.http.WsdlDefinitionHandlerAdapter.afterPropertiesSet(WsdlDefinitionHandlerAdapter.java:142)
    	at org.springframework.ws.transport.http.MessageDispatcherServlet.initWsdlDefinitionHandlerAdapter(MessageDispatcherServlet.java:288)
    	at org.springframework.ws.transport.http.MessageDispatcherServlet.initFrameworkServlet(MessageDispatcherServlet.java:203)
    	at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:237)
    	at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:126)
    	at javax.servlet.GenericServlet.init(GenericServlet.java:256)
    ....
    ....
    ....
    ....
    I need to restart my appserver, and after the restart, i can see my changed wsdl...

    Ideas?

    Thanks in advance!
    Hi,

    I have the same problem. How were you able to resolve this?

    [11/12/07 14:55:44:164 CET] 00000031 WebExtensionP W Servlet springws is currently unavailable: SRVE0203E: Servlet [springws]: org.springframework.ws.transport.http.MessageDispa tcherServlet was found, but is missing another required class.
    SRVE0206E: This error typically implies that the servlet was originally compiled with classes which cannot be located by the server.
    SRVE0187E: Check your classpath to ensure that all classes required by the servlet are present.SRVE0210I: This problem can be debugged by recompiling the servlet using only the classes in the application's runtime classpath

  6. #6
    Join Date
    Feb 2009
    Posts
    1

    Default MessageDispatcherServlet issue

    [QUOTE=miha;155619]Hi..managed to work around that issue..it was a classpath problem...

    Hi,
    can u tell us how you managed to work around the issue. I am running was6.1

    Thanks in advance

  7. #7
    Join Date
    Apr 2009
    Posts
    7

    Default How did you fix it?

    hi there!

    It will be really nice if someone who already fixed the issue will post the solution here. We are running WAS 6.1 as well.

    thanks a lot in advance

  8. #8
    Join Date
    Mar 2010
    Posts
    1

    Default Just in case

    Just in case anyone is getting this error in WAS 6.1 - check your startup logs. The error means what it says, but the startup logs give more details - check the location of the "FFDC opened incident stream file" - it should tell you the details of the missing class. Then you'll need to find it - add it into your classpath - rinse and repeat.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •