[ http://issues.apache.org/jira/browse/AXIS-2013?page=all ]

David McCullough updated AXIS-2013:
-----------------------------------

    Attachment: calc.zip

OK, I've found that if I define my service to use the RPC style, I get my 
specific exception. If I use wrapped/literal, I just get an AxisFault. 

I've tried this both under 1.2.1 and 1.3. Also, the setting of the 
"sendMultiRefs" parameter in server-config.wsdd doesn't seem to make a 
difference.

Swithcing to RPC is not an option for me. Is there some other way around this 
problem?

The attached calc.zip file contains a sample demonstrating the problem. Here 
are the files:
genstubs.bat - generates the client side stubs 
server-config.wsdd - the global configuration axis config file
CalcException - the custom exception thrown by the server
Calculator - implements the service on the server
CalcClient - calls the server, using the generated stubs

> 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: calc.zip, 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

Reply via email to