NullPointerException in org.apache.axiom.om.impl.util.OMSerializerUtil
----------------------------------------------------------------------

                 Key: AXIS2-3369
                 URL: https://issues.apache.org/jira/browse/AXIS2-3369
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: om
    Affects Versions: 1.3
         Environment: Cent OS 5, Apache 2.2.3, Tomcat 5.5.23, Axis2 1.3
CPU: AMD64
            Reporter: Kengo Seki


I'm trying to build my web service from WSDL already I have using Axis2 1.3, 
but the deployed web service doesn't work because of NullPointerException in 
OMSerializerUtil.

I have tried:

1. Using wsdl2java, generating skeleton codes from the wsdl attached to this 
post.
2. Build an aar file from skeletons and deploy it on Tomcat/Axis2 server.
3. Accessing deployed services. It causes server-side errors like this:

2007-11-27 17:24:34,608 [http-8080-Processor24] ERROR 
org.apache.axis2.transport.http.AxisServlet  - 
java.lang.NullPointerException
   at 
org.apache.axiom.om.impl.util.OMSerializerUtil.generateSetPrefix(OMSerializerUtil.java:560)
   at 
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSerializerUtil.java:273)
   at 
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSerializerUtil.java:172)
   at 
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:218)
   at 
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:814)
   at 
org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:421)
   at 
org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:68)
   at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.sendUsingOutputStream(CommonsHTTPTransportSender.java:294)
   at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:211)
   at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396)
   at 
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:45)
   at 
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96)
   at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)
   at 
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
   at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120)
   at 
javax.servlet.http.HttpServlet.service(tomcat5-servlet-2.4-api-5.5.23.jar.so)
   at 
javax.servlet.http.HttpServlet.service(tomcat5-servlet-2.4-api-5.5.23.jar.so)
   at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(catalina-5.5.23.jar.so8lr3s7.so)
   at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(catalina-5.5.23.jar.so8lr3s7.so)
   at 
org.apache.catalina.core.StandardWrapperValve.invoke(catalina-5.5.23.jar.so8lr3s7.so)
   at 
org.apache.catalina.core.StandardContextValve.invoke(catalina-5.5.23.jar.so8lr3s7.so)
   at 
org.apache.catalina.core.StandardHostValve.invoke(catalina-5.5.23.jar.so8lr3s7.so)
   at 
org.apache.catalina.valves.ErrorReportValve.invoke(catalina-5.5.23.jar.so8lr3s7.so)
   at 
org.apache.catalina.core.StandardEngineValve.invoke(catalina-5.5.23.jar.so8lr3s7.so)
   at 
org.apache.catalina.connector.CoyoteAdapter.service(catalina-5.5.23.jar.so8lr3s7.so)
   at 
org.apache.coyote.http11.Http11Processor.process(tomcat-http-5.5.23.jar.so)
   at 
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(tomcat-http-5.5.23.jar.so)
   at 
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(tomcat-util-5.5.23.jar.so)
   at 
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(tomcat-util-5.5.23.jar.so)
   at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(tomcat-util-5.5.23.jar.so)
   at java.lang.Thread.run(libgcj.so.7rh)

Almost same trouble also occurs if using the latest snapshot (revision 595335).
It seems to be able to avoid by null check on the return of 
writer.getNamespaceContext().

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to