[jira] [Updated] (AXIS2-5092) IN-only method custom exception return missing details

["Vilnis Termanis (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AXIS2-5092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vilnis Termanis updated AXIS2-5092:
-----------------------------------

             Priority: Major  (was: Critical)
          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 update() as "InOnly" in services.xml (due to AXIS2-5215):
 <operation name="update"><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.

  was:
If an In-Only (RPCInOnlyMessageReceiver) POJO function throws a custom exception, the details tag is empty, e.g.:

public void myFunction(String myArg) throws MyException {}
(where MyException e.g. has a "public int getCode()" function)

Note: This might be related to AXIS2-4408. Also the details tag is populated as expected if the function returns something (i.e if it isn't an In-Only).

          Environment: Tomcat 6, jdk 1.6.0_26  (was: Tomcat 6, jdk 1.6.0_24)
    Affects Version/s: 1.7.0
                       1.6.1
              Summary: IN-only method custom exception return missing details  (was: IN-only method exception produces empty detail tag)
    
> IN-only method custom exception return missing details
> ------------------------------------------------------
>
>                 Key: AXIS2-5092
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5092
>             Project: Axis2
>          Issue Type: Bug
>          Components: adb, rpc
>    Affects Versions: 1.5.5, 1.6.0, 1.6.1, 1.7.0
>         Environment: Tomcat 6, jdk 1.6.0_26
>            Reporter: Vilnis Termanis
>              Labels: detail, exception, in-only, pojo
>
> 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 update() as "InOnly" in services.xml (due to AXIS2-5215):
>  <operation name="update"><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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org