cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christofer Dutz (JIRA)" <j...@apache.org>
Subject [jira] Created: (CXF-2088) Wrong serialisation order of elements when using Aegis databinding.
Date Thu, 05 Mar 2009 09:53:58 GMT
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


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.


Mime
View raw message