Hello, I asked the following question on the axis user-list but no one seemed able to answer. I am wondering if this could be a bug so I forward it here.
- emmanuel Emmanuel GUITON Ingénieur développement Fixe : +33 1 70 92 84 16 * Standard : +33 1 41 91 77 77 215, Avenue Georges Clemenceau * 92024 Nanterre [cid:image95bd42.gif@e0c146a3.dae84cae]<http://www.intrinsec.com/> [cid:imageba76b3.jpg@7a658df9.c6454df9]<http://www.intrinsec.com/> Cliquez ici pour obtenir la dernière étude Markess sur le Cloud<http://www.markess.fr/demandedocument.php?refdoc=798> De : Emmanuel GUITON [mailto:emmanuel.gui...@intrinsec.com] Envoyé : vendredi 6 avril 2012 17:44 À : java-u...@axis.apache.org Objet : [Axis 2] NullPointerException in RPCMessageReceiver.invokeBusinessLogic Hello all, I implemented a web-service and I am running into trouble with a custom soap fault message. Each time I throw the corresponding Java exception, I get the following soap fault : <soapenv:Fault> <faultcode>soapenv:Server</faultcode> <faultstring>java.lang.NullPointerException</faultstring> <detail /> </soapenv:Fault> Which is not my own exception. In fact, the NullPointerException comes from the invokeBusinessLogic method in org.apache.axis2.rpc.receivers. RPCMessageReceiver java.lang.NullPointerException at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:179) at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40) Indeed, inMessage.getAxisService().getTypeTable() returns NULL in the following code : 177 String partQName = inMessage.getAxisService().getName() + getSimpleClassName(exceptionType); 178 TypeTable typeTable = inMessage.getAxisService().getTypeTable(); 179 QName elementQName = typeTable.getQNamefortheType(partQName); I am stuck with this error. Does anyone has an idea about what I could do wrong ? I am using jaxws-maven-plugin to generate the bindings, Axis2 1.6.1 webapp in a tomcat 7 server to deploy the generated AAR file. And here is the definition of my own fault message : <wsdl:message name="faultResponse"> <wsdl:part element="lbp:faultResponse" name="content" /> </wsdl:message> <complexType name="FaultType"> <sequence> <element minOccurs="0" name="reason" type="string" /> </sequence> </complexType> Thanks for any help, - emmanuel Emmanuel GUITON Ingénieur développement Fixe : +33 1 70 92 84 16 * Standard : +33 1 41 91 77 77 215, Avenue Georges Clemenceau * 92024 Nanterre [cid:image98e4c0.gif@8a1cc81a.904f4db4]<http://www.intrinsec.com/> [cid:imagea50606.jpg@92bddefc.1a0a4ce6]<http://www.intrinsec.com/> Cliquez ici pour obtenir la dernière étude Markess sur le Cloud<http://www.markess.fr/demandedocument.php?refdoc=798>
<<inline: image98e4c0.gif@8a1cc81a.904f4db4>>
<<inline: imagea50606.jpg@92bddefc.1a0a4ce6>>
<<inline: image95bd42.gif@e0c146a3.dae84cae>>
<<inline: imageba76b3.jpg@7a658df9.c6454df9>>
