You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 24, 2018. It is now read-only.
The JSR 222 EG already agreed that a mapping rule that maps the
Javabean like properties and fields within a class to a xs:sequence
compositor should be supported. However, the Javabean properties and
fields within a class are unordered. So should there be default order
specified ?
One suggestion was to use alphabetical order as default order.
Environment
Operating System: All
Platform: All
Affected Versions
[2.0 draft]
The text was updated successfully, but these errors were encountered:
The JSR 222 EG already agreed that a mapping rule that maps the
Javabean like properties and fields within a class to a xs:sequence
compositor should be supported. However, the Javabean properties and
fields within a class are unordered. So should there be default order
specified ?
One suggestion was to use alphabetical order as default order.
Environment
Operating System: All
Platform: All
Affected Versions
[2.0 draft]
The text was updated successfully, but these errors were encountered: