axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hans (JIRA)" <>
Subject [jira] Commented: (AXIS-2013) Deserialization of Exception fails
Date Tue, 01 Nov 2005 09:00:56 GMT
    [ ] 

Hans commented on AXIS-2013:

Because the problem did not occur using the Axis wsdl2java generated client code I did not
fix the problem.
Also when using org.apache.axis.client.Call as done in the testcase (attached) if sendMultiRefs
is set to false everything works ok.  I'm wondering whether I did not do something wrong in
the testcase code, perhaps something wrong in registration of the call / (de)serializers -
because with generated wsdl2java code everything works ok.

> Deserialization of Exception fails
> ----------------------------------
>          Key: AXIS-2013
>          URL:
>      Project: Apache Axis
>         Type: Bug
>   Components: Serialization/Deserialization
>     Versions: current (nightly)
>  Environment: Linux, JDK 1.4.2_06
>     Reporter: Hans
>     Assignee: Davanum Srinivas
>     Priority: Critical
>  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