axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AXIS2-479) Axis2 does not deserialise abstract types correctly when receiving WSA messages
Date Tue, 26 Dec 2017 13:11:00 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16303829#comment-16303829
] 

Hudson commented on AXIS2-479:
------------------------------

ABORTED: Integrated in Jenkins build Axis2 #3864 (See [https://builds.apache.org/job/Axis2/3864/])
Recycle the test case for AXIS2-479 and transform it into a test case for Axiom. It is no
longer relevant for Axis2 itself because XmlBeans objects are now serialized using SAX. (veithen:
rev 1819279)
* (edit) axis2/modules/integration/itest-build.xml
* (edit) axis2/modules/integration/pom.xml
* (delete) axis2/modules/integration/test-resources/xsd/type-test.xsd
* (delete) axis2/modules/integration/test/org/apache/axis2/om/OMAttributeTest.java


> Axis2 does not deserialise abstract types correctly when receiving WSA messages
> -------------------------------------------------------------------------------
>
>                 Key: AXIS2-479
>                 URL: https://issues.apache.org/jira/browse/AXIS2-479
>             Project: Axis2
>          Issue Type: Bug
>    Affects 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(): za.co.eskom.nrs.www.xmlvend.base._2_0.schema.impl.DeviceIDImpl
> schemaType(): DeviceID@http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema
> toString(): <xml-fragment type="sch:GenericDeviceID" id="255255010" xmlns:sch="http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema"/>
> XSI:
> getClass().getName(): za.co.eskom.nrs.www.xmlvend.base._2_0.schema.impl.GenericDeviceIDImpl
> schemaType(): T=GenericDeviceID@http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema
> toString(): <xml-fragment xsi:type="sch:GenericDeviceID" id="255255010" xmlns:sch="http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
> 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 was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message