You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cxf.apache.org by "Benson Margulies (JIRA)" <ji...@apache.org> on 2009/03/06 00:59:56 UTC

[jira] Resolved: (CXF-2088) Wrong serialisation order of elements when using Aegis databinding.

     [ https://issues.apache.org/jira/browse/CXF-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benson Margulies resolved CXF-2088.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2

Fix applied to trunk.

> 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.