axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <>
Subject [jira] Updated: (AXIS2-586) CLONE -Axis2 does not deserialise abstract types correctly when receiving WSA messages
Date Thu, 12 Oct 2006 23:35:34 GMT
     [ ]

Davanum Srinivas updated AXIS2-586:

    Component/s: databinding

> CLONE -Axis2 does not deserialise abstract types correctly when receiving WSA messages
> --------------------------------------------------------------------------------------
>                 Key: AXIS2-586
>                 URL:
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: databinding
>    Affects Versions: 0.94
>         Environment:  Suse Linux 9.3 Server, Tomcat 5.0, Axis2 0.94
>            Reporter: Justin Schoeman
>         Assigned To: Davanum Srinivas
> 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:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message