[CXF-2088] Wrong serialisation order of elements when using Aegis databinding.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.4
• Fix Version/s: 2.1.5
• Component/s: Aegis Databinding
• Estimated Complexity: Advanced
• Assignee: Benson Margulies
• Reporter: Christofer Dutz
• Created: 05/Mar/09 09:53
• Updated: 24/Apr/09 21:17
• Resolved: 05/Mar/09 23:58

Description

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.