[
https://issues.apache.org/jira/browse/CXF-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679562#action_12679562
]
Christofer Dutz commented on CXF-2088:
--------------------------------------
I haven't had a real deep look into how data is processed. The main problem was
that the order was simply not schema valid.
I guss to make it really fool-proof it would be necessary to do a two-phase
processing ...
1. Process attributes of current- and parent-types
2. Process the elements of the parents and then of the current type
Tanks for patching :-)
When will with be available as compiled maven-artifact?
I am curently using a local artifact of version 2.1.4 with the applied patch,
as I sort of had problems building a 2.1.4.1 version ...
> Wrong serialisation order of elements when using Aegis databinding.
> -------------------------------------------------------------------
>
> Key: CXF-2088
> URL: https://issues.apache.org/jira/browse/CXF-2088
> Project: CXF
> Issue Type: Bug
> Components: Aegis Databinding
> Affects Versions: 2.1.4
> Reporter: Christofer Dutz
> Assignee: Benson Margulies
> Fix For: 2.2
>
> Attachments: BeanType.java
>
>
> In my current case I hava
> * an abstract Java class "AbstractDatabaseObject" defining a property "id".
> * an abstract Java class "Credential" which extends "AbstractDatabaseObject"
> and defines a property "name"
> * a concrete Java class "UsernamePasswordCredential" which extends
> "Credential" and defines properties "username" and "password"
> All schemas are created to my greates satisfaction (Great Job!).
> Unfortunately the serialisation order when using Aegis databinding (don't
> know if its the same using others) is the wrong way around.
> Instead of getting:
> <cred>
> <id>306ce816-01b7-11de-8d92-8d4df6b73eb1</id>
> <name>dsfgsdfgs</name>
> <password>dsfsfdg</password>
> <username>sdsdfgsdfg</username>
> </cred>
> I get:
> <cred>
> <password>dsfsfdg</password>
> <username>sdsdfgsdfg</username>
> <name>dsfgsdfgs</name>
> <id>306ce816-01b7-11de-8d92-8d4df6b73eb1</id>
> </cred>
> Which my Flex client complains about.
> I'll try to whip up a patch fixing this issue today.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
