[ http://issues.apache.org/jira/browse/AXIS-2013?page=comments#action_12356591 ]
Hans commented on AXIS-2013: ---------------------------- I have rewritten my testcase 'faults2' to a webservice with document/literal binding. With the Axis 1.2.1 wsdl2java generated code the deserialization of the exception is OK. I have attached the new testcase - perhaps it could be included in the testset so (de)serialization of faults with document/literal ws is tested (currently only rpc/encoded is tested in the 'faults' test). Installation: extract faults2_doclit.zip to $AXIS_HOME/test/wsdl/faults2 > 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
