axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 20653] - AxisFault during config processing gives NPE
Date Tue, 10 Jun 2003 18:05:35 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20653>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20653

AxisFault during config processing gives NPE

dug@us.ibm.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|Other                       |High



------- Additional Comments From dug@us.ibm.com  2003-06-10 18:05 -------
If you modify the server-config.wsdd so that there's a bad classname in
one of the handlers (like change JWSHandler to JWSHandler11) then you'll
get a NPE:
java.lang.NullPointerException
        at org.apache.axis.message.SOAPFault.getFaultQName(SOAPFault.java:215)
        at org.apache.axis.message.SOAPFault.outputImpl(SOAPFault.java:185)
        at org.apache.axis.message.MessageElement.output(MessageElement.java:783
)
        at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:174)
        at org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:509
)
        at org.apache.axis.message.MessageElement.output(MessageElement.java:783
)
        at org.apache.axis.AxisFault.output(AxisFault.java:692)
        at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:259)
        at org.apache.axis.SOAPPart.getAsString(SOAPPart.java:468)
        at org.apache.axis.SOAPPart.getAsBytes(SOAPPart.java:375)
        at org.apache.axis.Message.getContentType(Message.java:399)
        at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:88
7)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
...
this is because the responseMsg object doesn't have its messageContext set.
This is a change from previous behaviour and is critical.

Mime
View raw message