On 15/04/2015 17:28, Bert Verhees wrote: > On 15-04-15 17:19, Dmitry Baranov wrote: >> Sorry Bert ) I had to explain that Oracle 11 is a business >> requirement, not a hardware limitation. >> >>> Just do it, and then it should run fine, although you have to change >>> the >>> XML-Schemas (a bit) before registering them to Oracle. I already >>> explained to you before what and why. >> I remember your advise but not sure that changing all the sequences >> to choices is a right way for many reasons. And I'm almost sure that >> it's an Oracle bug since other XSD validation tools (visual studio, >> netbeans and eclipse) say that my instance files are all OK and >> conform to XML schema. > > You are right it is a messy solution, but if you use "sequence", like > it is defined in the XML Schema, you have to take care that all the > nodes in your XML are in the right/defined order. > I think this is hard to achieve when XML-files are created in > production, but of course, you can arrange that as an alternative. > > I think it is a stupid rule in the XML-Schema standard.
I just hit this in doing the AOM2 schema. It's a completely senseless rule, clearly a hangover from 'document' thinking - nothing to do with 'data' thinking. I ended up replacing <sequence> with. <xs:choice maxOccurs="unbounded"> I have to say, XML-schema based data looks extremely unattractive as a basis for anything except data exchange. I wouldn't try to implement anything important inside a system with it, you are too compromised in too many ways. - thomas
