Hi
On 09/10/13 22:32, tomstark wrote:
Hi Sergey,
Answers to some of your questions:
Do you mean it is not guaranteed from JSON client ? If so, do you mean
that a new content covered by xsd:any can get in front of someInt ?
The order of the elements from the JSON from the client is not guaranteed to
match that of the schema. The schema example was overly simplified to a
single field. A better example would have been to have multiple elements
along with the xs:any. In that case, unordered JSON violates the schema and
is rejected.
In general, the xs:any is in place for clients or servers to be able to
interact with the other side (server or client, respectively) without having
to be on the exact version of the API. Typically, this is useful when
adding additional fields to the end of a sequence definition for a
particular object.
Does that affect the answer you gave me regarding modifying the JSON
provider?
Not really, the last suggestion re using xsd:all on JSON path (you can
explicitly configure JSONProvider with the list of schemas) and dropping
the extension elements should do, because all xs:any allows is not
validating but accepting the extra bits with the older data containers,
so this should work dropping the extensions via inDropElements
Cheers, Sergey
(I'm looking into your answer now)
Thanks,
Tom
--
View this message in context:
http://cxf.547215.n5.nabble.com/Can-unordered-JSON-work-with-XML-sequence-with-validation-tp5734874p5734878.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
