[jira] Resolved: (CXF-2365) XSD produced by Aegis is different depending on what JVM is used to compile and run the application

["Benson Margulies (JIRA)" <ji...@apache.org>]

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

Benson Margulies resolved CXF-2365.
-----------------------------------

    Resolution: Fixed

r831680. Note that this is a potential incompatibility between 2.2.x and 2.3.

The references sun bug issue was addressed some time ago, the fix is already in the code.


> XSD produced by Aegis is different depending on what JVM is used to compile and run the application
> ---------------------------------------------------------------------------------------------------
>
>                 Key: CXF-2365
>                 URL: https://issues.apache.org/jira/browse/CXF-2365
>             Project: CXF
>          Issue Type: Improvement
>          Components: Aegis Databinding
>    Affects Versions: 2.2.2
>            Reporter: Sergey Beryozkin
>            Assignee: Benson Margulies
>             Fix For: 2.3
>
>
> Dan Kulp : I think in the aegis BeanType.Info.initializeProperties method, the resulting list of PropertyDescriptors should be sorted into a predictable and reproducable order (alpha by name would work). Currently, the XSD produced by aegis will be completely different depending on what JVM is used to compile and run the application which is probably not a good thing. ALTERNATIVELY (or in addition to), update the aegis.type.java5 @XmlType annotation to have the propOrder thing that the JAXB thing has as well.
> see https://issues.apache.org/jira/browse/CXF-2362 for more info

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.