axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Schoeman (JIRA)" <>
Subject [jira] Commented: (AXIS2-586) CLONE -Axis2 does not deserialise abstract types correctly when receiving WSA messages
Date Mon, 24 Apr 2006 07:54:15 GMT
    [ ] 

Justin Schoeman commented on AXIS2-586:

The following files are required (in the same directory):

Use '-d xmlbeans' with WSDL2Java, as the ADB code produced is not compilable. Also, may need
to edit the SoapAction fields the the wsdl file - just make them the same as the operation
names for the operations you intend to call. Axis2 performs the wrong operation if this is
not done.


> CLONE -Axis2 does not deserialise abstract types correctly when receiving WSA messages
> --------------------------------------------------------------------------------------
>          Key: AXIS2-586
>          URL:
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug

>     Versions: 0.94
>  Environment:  Suse Linux 9.3 Server, Tomcat 5.0, Axis2 0.94
>     Reporter: Justin Schoeman
>     Assignee: Ajith Harshana Ranabahu

> When receiving WSA encoded messages containing abstract types, the created objects are
for the implementation of the abstract class, instead of the actual type sent over the wire.
> In the following example, DeviceID is an abstract type, and EANDeviceID is an implementation
of that type. The following information is obtained from the deserialised DeviceID object
(which is sent as an EANDeviceID object):
> WSA:
> getClass().getName():
> schemaType(): DeviceID@
> toString(): <xml-fragment type="sch:GenericDeviceID" id="255255010" xmlns:sch=""/>
> XSI:
> getClass().getName():
> schemaType(): T=GenericDeviceID@
> toString(): <xml-fragment xsi:type="sch:GenericDeviceID" id="255255010" xmlns:sch=""
> As you can see, in both cases, the correct information is contained in the xmlbean, but
for the WSA message it is deserialised incorrectly.
> -justin

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message