axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayachandra Sekhara Rao Sunkara (JIRA)" <>
Subject [jira] Commented: (AXIS-1662) Missing xsi:type when a web service throws a fault that is an extension of the declared fault
Date Tue, 16 Nov 2004 09:16:25 GMT
     [ ]
Jayachandra Sekhara Rao Sunkara commented on AXIS-1662:

Oops! sorry for that. I've copied the Impl file now.

> Missing xsi:type when a web service  throws a fault that is an extension of the declared
> ----------------------------------------------------------------------------------------------
>          Key: AXIS-1662
>          URL:
>      Project: Axis
>         Type: Bug
>   Components: Serialization/Deserialization
>     Versions: 1.2RC1
>  Environment: Linux (debian testing distribution)
> JDK 1.4.2 (blackdown 1.4.2-rc1)
> Axis 1.2RC1
>     Reporter: Peter Canning
>  Attachments:, exceptionTest.wsdl,
> I started from a WSDL specification that defines a complexType BaseException which is
used as the type of an element used in a message that us used for the fault of an operation.
 It also defines a complex type DerivedException that is an extension of BaseException.  I
generate both server and client stubs using WSDLToJava, and fill in the bodies of the methods
in the ...Impl class in the server stubs.  I then write a client using client stubs to exercise
the web service.
> Using SimpleAxisServer to run the web service, when the ...Impl method (which is declared
to throw a BaseException) throws a DerivedException, the web service correctly serializes
the additional elements in the DerivedException, but it does not serialize an xsi:type to
specify that the element has type DerivedException rather than BaseException.  As a result,
the Axis client fails, reporting the error:
> Exception in thread "main" AxisFault
>  faultCode: {}Server.userException
>  faultSubcode: 
>  faultString: org.xml.sax.SAXException: Invalid element in exceptionTest.client.BaseException
- size

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message