You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org> on 2007/09/28 14:54:04 UTC
[jira] Updated: (AXIS-2013) Deserialization of Exception fails
[ https://issues.apache.org/jira/browse/AXIS-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS-2013:
-----------------------------------
Assignee: (was: Davanum Srinivas)
> Deserialization of Exception fails
> ----------------------------------
>
> Key: AXIS-2013
> URL: https://issues.apache.org/jira/browse/AXIS-2013
> Project: Axis
> Issue Type: Bug
> Components: Serialization/Deserialization
> Affects Versions: current (nightly)
> Environment: Linux, JDK 1.4.2_06
> Reporter: Hans
> Priority: Critical
> Attachments: calc.zip, faults2.zip, faults2_doclit.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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org