Is your solution the right one? If the biz logic returns null then its saying it has no XML to return. IMO that should result in the following message:
<s:Envelope> <s:Body/> </s:Envelope> Boring, but valid SOAP message. Its not a fault to have no output. If this was a POX request this'll map to HTTP 200 OK with a content length of zero .. which is correct I'd argue. Sanjiva. On Mon, 2006-10-02 at 23:20 -0700, Asankha C. Perera (JIRA) wrote: > RawXMLINOnlyMessageReceiver throws a NPE if method is not found > --------------------------------------------------------------- > > Key: AXIS2-1287 > URL: http://issues.apache.org/jira/browse/AXIS2-1287 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: core > Reporter: Asankha C. Perera > Priority: Minor > > > The RawXMLINOnlyMessageReceiver throws a NPE SOAP fault back to the client if > the method referenced is not found on the ServiceClass implementation. A > meaningful SOAP fault should be returned. > > <service > > <parameter name="ServiceClass" locked="false">test.mr.MRTest1</parameter> > <operation name="invalidMethodName"> > <messageReceiver > class="org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver"/> > <actionMapping>urn:invalidMethodName</actionMapping> > </operation> > </service> > > public class MRTest1 { > public void invalidMethodNameX(OMElement element){ > ..... > } > } > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
