Details
Description
Procedure:
1) Create POJO service with non-returning function which throws a custom exception, e.g.:
public class ExampleService { public void testFunction(String something) throws MyException { throw new MyException("testing123", 123); }}
Explicitly define testFunction() as "InOnly" in services.xml (due to AXIS2-5215):
<operation name="testFunction"><messageReceiver class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver" /></operation>
3) Call testFunction() from client
4) Change function to be non-void, e.g.:
public boolean testFunction(String something) throws MyException { throw new MyException("testing123", 123); }}
5) Repeat step 3
Result:
3) Additional exception variables are not returned as part of xml response, i.e. an empty "<detail/>" tag is returned.
5) Fully populated <detail> tag returned as part of exception, as expected.
Attachments
Issue Links
- is related to
-
AXIS2-4408 the problem of In-only method with throw exception
- Resolved
-
AXIS2-5215 wsdl:fault tag missing for soap bindings in wsdl for In-Only POJO
- Resolved