[ http://issues.apache.org/jira/browse/AXIS-2013?page=all ]
Davanum Srinivas updated AXIS-2013:
-----------------------------------
Priority: Critical (was: Blocker)
> Deserialization of Exception fails
> ----------------------------------
>
> Key: AXIS-2013
> URL: http://issues.apache.org/jira/browse/AXIS-2013
> 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: faults2.zip
>
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
