axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hans (JIRA)" <>
Subject [jira] Updated: (AXIS-2013) Deserialization of Exception fails
Date Thu, 02 Jun 2005 14:37:51 GMT
     [ ]

Hans updated AXIS-2013:


I attached a testcase to clarify the problem: it's derived from the faults testcase in $AXIS_HOME/java/test/wsdl/faults
and should be installed in $AXIS_HOME/java/test/wsdl/faults2. 

The test will generate a webservice from FaultService.wsdl and access it in the FaultServiceTestCase
by creating a org.apache.axis.client.Call. The webservice will throw an exception which should
be serialized to the client.
First it will do so with 'sendMultiRefs=false' in deploy.wsdd (test will succeed), then it
will attempt to do so with 'sendMultiRefs=true' in deploy.wsdd (test will fail).

> Deserialization of Exception fails
> ----------------------------------
>          Key: AXIS-2013
>          URL:
>      Project: Axis
>         Type: Bug
>   Components: Serialization/Deserialization
>     Versions: current (nightly)
>  Environment: Linux, JDK 1.4.2_06
>     Reporter: Hans
>  Attachments:
> I have a very basic application deployed as a webservice with one operation that throws
a user-defined exception (derived from AxisFault). The client application calling this operation
has defined a type mapping that maps the operation fault to a client-side Exception class.
When the client invokes the operation and the exception is thrown, the client throws an AxisFault
instead of the client-exception class. 
> When I edit the server-config.wsdd and set the parameter 'sendMultiRefs' to false, everything
works ok: the exception thrown in the server is deserialized and the client throws the mapped
client-side exception. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message