[
https://issues.apache.org/jira/browse/CXF-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735871#action_12735871
]
Daniel Kulp commented on CXF-2362:
----------------------------------
Actually, 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.
> AegisJSONProviderTest.testManyTags fails with the ibm jdk
> ---------------------------------------------------------
>
> Key: CXF-2362
> URL: https://issues.apache.org/jira/browse/CXF-2362
> Project: CXF
> Issue Type: Bug
> Environment: ibm jdk on linux or aix
> Reporter: Peter Jones
>
> The AegisJSONProviderTest.testManyTags () fails when run with the ibm jdk.
> It attempts to do a straight string comparison of the response, however, the
> order of the elements in the reponse is different on the ibm jdk than it is
> on the sun jdk.
> Expected:
> <...,{"ns1.TagVO":{"ns1.[group":"b","ns1.name":"a]"}}]}]}>
> Was:
> <...,{"ns1.TagVO":{"ns1.[name":"a","ns1.group":"b]"}}]}]}>
> Specifying a propOrder in the XmlType annotation doesn't seem to work for
> this case (using aegis), so probably the best solution is to check for a
> different string when running with the ibm jdk.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
