David M. Lloyd wrote:
On 04/13/2009 03:36 PM, Alexey Loubyansky wrote:
> Jason T. Greene wrote:
>> Alexey Loubyansky wrote:
>>> Yes, the purpose of CR1 was for testing. I haven't heard of any
>>> issue except for setting -Dxb.builder.useUnorderedSequence for the
>>> testsuite. So, no problem with doing GA.
>>>
>>> I'll do maybe one more thing for the binder: if a Java type is bound
>>> to a sequence and doesn't use @XmlType.propOrder then the binding
>>> will fail with an exception. We've seen how missed propOrder can
>>> cause deployment errors in 5.0.0.GA in some environments. So, really
>>> if you bind to a sequence and don't use propOrder your
>>> project/product may fail on a different JVM. I'll make a config
>>> option for that as well.
>>
>> Do you support @XmlAccessOrder(ALPHABETICAL)? This does give
>> compliant behavior when propOrder is undefined. If so, perhaps this
>> option should only trigger an error/warning when properOrder is
>> undefined and XmlAccessOrder is set to UNDEFINED.
>
> Yes, it is supported. And yes it should be taken into account in this
> case.
So for those of us who are mostly JAXB-ignorant - if I give propOrder={}
this means that no additional order (beyond what's in the XSD, if
validation is enabled) will be enforced, right? So I should be adding
this to every XmlType in my MC metadata class definitions?
Basically.
See the javadoc to XmlType, it has a nice decision table. The odd
behavior is the default, which is very unintuitive.
--
Jason T. Greene
JBoss, a division of Red Hat