There's one case in which my ordered="false" attribute seems to have no effect.
I have an XSD taken from OTA 2010B specs: http://old.nabble.com/file/p31789973/OTA_CommonTypes.xsd OTA_CommonTypes.xsd The CustomerType is indeed a <xs:sequence>, so JiBX assumes correctly it contains elements in the specified order. Unfortunately the other party server ignores it, and sends messages in the wrong order. I've modified the JiBX generated mapping file: http://old.nabble.com/file/p31789973/org.ota.common.xml org.ota.common.xml I added ordered="false", but I still get the same error: JiBX unmarshalling exception; nested exception is org.jibx.runtime.JiBXException: Expected "{http://www.opentravel.org/OTA/2003/05}Customer"; end tag, found "{http://www.opentravel.org/OTA/2003/05}Email"; start tag (line 79, col 17) What can I do? Modify the schema setting <xs:all> in place of <xs:sequence>? Change position of the contained elements in the XSD? Why did it work in other cases, and not this time? Any suggestion is much appreciated Cheers Vito Meuli -- View this message in context: http://old.nabble.com/Hot-to-instruct-codegen-to-use-ordered%3D%22false--tp31635937p31789973.html Sent from the jibx-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ jibx-users mailing list jibx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-users
