Results 1 to 7 of 7

Thread: spring ws example with websphere 6.1

  1. #1
    Join Date
    Oct 2007
    Posts
    7

    Default spring ws example with websphere 6.1

    When I tried the echo example of spring-ws 1.5.8 with websphere 6.1 (without feature pack), and configured the classloader to:

    * Classes loaded with application class loader first
    * Single class loader for application

    I got the following exception. What did I miss?


    [28/09/09 11:10:33:925 EDT] 00000061 WebApp E [Servlet Error]-[spring-ws]: java.lang.VerifyError: javax/xml/soap/SOAPElement.getElementQName()Ljavax/xml/namespace/QName;
    at org.springframework.ws.soap.saaj.Saaj13Implementat ion.getName(Saaj13Implementation.java:67)
    at org.springframework.ws.soap.saaj.SaajSoapEnvelope. getBody(SaajSoapEnvelope.java:54)
    at org.springframework.ws.soap.AbstractSoapMessage.ge tSoapBody(AbstractSoapMessage.java:36)
    at org.springframework.ws.soap.AbstractSoapMessage.ge tPayloadSource(AbstractSoapMessage.java:46)
    at org.springframework.ws.server.endpoint.mapping.Pay loadRootQNameEndpointMapping.resolveQName(PayloadR ootQNameEndpointMapping.java:57)
    at org.springframework.ws.server.endpoint.mapping.Abs tractQNameEndpointMapping.getLookupKeyForMessage(A bstractQNameEndpointMapping.java:33)
    at org.springframework.ws.server.endpoint.mapping.Abs tractMapBasedEndpointMapping.getEndpointInternal(A bstractMapBasedEndpointMapping.java:106)
    at org.springframework.ws.server.endpoint.mapping.Abs tractEndpointMapping.getEndpoint(AbstractEndpointM apping.java:83)
    at org.springframework.ws.server.MessageDispatcher.ge tEndpoint(MessageDispatcher.java:248)
    at org.springframework.ws.server.MessageDispatcher.di spatch(MessageDispatcher.java:201)
    at org.springframework.ws.server.MessageDispatcher.re ceive(MessageDispatcher.java:168)
    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:230)
    at org.springframework.web.servlet.FrameworkServlet.p rocessRequest(FrameworkServlet.java:571)
    at org.springframework.web.servlet.FrameworkServlet.d oPost(FrameworkServlet.java:511)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:763)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:856)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.ser vice(ServletWrapper.java:1143)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.han dleRequest(ServletWrapper.java:591)
    at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.h andleRequest(ServletWrapper.java:481)
    at com.ibm.ws.webcontainer.webapp.WebApp.handleReques t(WebApp.java:3453)
    at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequ est(WebGroup.java:267)
    at com.ibm.ws.webcontainer.WebContainer.handleRequest (WebContainer.java:815)
    at com.ibm.ws.wswebcontainer.WebContainer.handleReque st(WebContainer.java:1466)
    at com.ibm.ws.webcontainer.channel.WCChannelLink.read y(WCChannelLink.java:119)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleDiscrimination(HttpInboundLink.java:458)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleNewInformation(HttpInboundLink.java:387)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.ready(HttpInboundLink.java:267)
    at com.ibm.ws.tcp.channel.impl.NewConnectionInitialRe adCallback.sendToDiscriminators(NewConnectionIniti alReadCallback.java:214)
    at com.ibm.ws.tcp.channel.impl.NewConnectionInitialRe adCallback.complete(NewConnectionInitialReadCallba ck.java:113)
    at com.ibm.ws.tcp.channel.impl.AioReadCompletionListe ner.futureCompleted(AioReadCompletionListener.java :165)
    at com.ibm.io.async.AbstractAsyncFuture.invokeCallbac k(AbstractAsyncFuture.java:217)
    at com.ibm.io.async.AsyncChannelFuture.fireCompletion Actions(AsyncChannelFuture.java:161)
    at com.ibm.io.async.AsyncFuture.completed(AsyncFuture .java:136)
    at com.ibm.io.async.ResultHandler.complete(ResultHand ler.java:196)
    at com.ibm.io.async.ResultHandler.runEventProcessingL oop(ResultHandler.java:751)
    at com.ibm.io.async.ResultHandler$2.run(ResultHandler .java:881)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:1473)

  2. #2

    Default

    This FAQ entry might be helpful for you:
    http://static.springsource.org/sprin...saaj-websphere
    Tareq Abedrabbo

    My Twitter
    My Blog

  3. #3
    Join Date
    Oct 2007
    Posts
    7

    Default

    The faq link is very helpful. Thank you very much, Tareq.

  4. #4
    Join Date
    Oct 2009
    Posts
    1

  5. #5
    Join Date
    Mar 2011
    Posts
    27

    Default

    Hi mzliu,
    Can you please take me through how you solved this problem. I am having the same issue with WAS 6.1. Can you please tell me the jars you referenced in the shared libraries in the admin console. I will very much appreciate it.
    Thanks in advance.

    Emmanuel

  6. #6
    Join Date
    Jul 2011
    Posts
    8

    Default

    Hi Emmanuel,

    Did you get any answer? I am too caught up on this same issue.

    Hardik

  7. #7
    Join Date
    Jul 2011
    Posts
    8

    Default

    Latest JAXB2_20110512 will solve the problem. Just run this self extracting jar and should have latest jaxb jars and thats it.

Posting Permissions

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