Hi,
Has anyone successfully deployed and tested the echo example on Weblogic 9.1 - I'm having difficulty? I added a blank weblogic.xml to WEB-INF, created the war, and deployed to weblogic via auto-deploy. However I get a saaj error and it appears to be a conflict with weblogic's saaj. I've read where others have had problems with saaj and weblogic and was wondering if this might be the case as well.
<May 21, 2007 6:46:05 AM PDT> <Error> <HTTP> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@680 11a - name: 'echo.war', context-path: '/echo/services'] Root cause of ServletException.java.lang.NoSuchMethodError: newInstance at org.springframework.ws.soap.saaj.SaajSoapMessageFa ctory.afterPropertiesSet(SaajSoapMessageFactory.ja va:82)
at org.springframework.ws.transport.http.MessageDispa tcherServlet.initWebServiceMessageFactory(MessageD ispatcherServlet.java:163)
at org.springframework.ws.transport.http.MessageDispa tcherServlet.initFrameworkServlet(MessageDispatche rServlet.java:103)
...
I appeared to clear this problem by adding the following to spring-ws-servlet.xml:
<bean id="messageFactory" class="org.springframework.ws.soap.saaj.SaajSoapMe ssageFactory">
<property name="messageFactory" ref="sunSaaj"/>
</bean>
<bean id="sunSaaj" class="com.sun.xml.messaging.saaj.soap.MessageFact oryImpl" />
If I build and run the included echo saaj client I get the following on the server:
<May 21, 2007 7:21:20 AM PDT> <Error> <HTTP> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@65a b67 - name: 'echo.war', context-path: '/echo'] Root cause of ServletException.
java.lang.NoSuchMethodError: getElementQName
at org.springframework.ws.soap.saaj.Saaj13Implementat ion.getName(Saaj13Implementation.java:67)
at org.springframework.ws.soap.saaj.SaajSoapEnvelope. getBody(SaajSoapEnv
elope.java:49)
at org.springframework.ws.soap.AbstractSoapMessage.ge tSoapBody(AbstractS
oapMessage.java:35)
at org.springframework.ws.soap.AbstractSoapMessage.ge tPayloadSource(Abst
ractSoapMessage.java:49)
at org.springframework.ws.server.endpoint.mapping.Pay loadRootQNameEndpoi
ntMapping.getMessagePayloadElement(PayloadRootQNam eEndpointMapping.java:63)
Which leads me to believe saaj is still a problem.
???
Thanks for the help!
sej


Reply With Quote