Hi Rob The XML Schema validator is based on the Xerces validator (parser), so I had a discussion with one of the developers. I'll try to answer your questions:
1) The validator resolves components via imports so if the import is missing, the schema is invalid. See: https://www.w3.org/TR/xmlschema-1/#src-resolve 2) This is a good question. I suspect that this client schema on its own is 'invalid' and is never intended to be used that way. (There are no global elements too so you can't create an instance document from it). The EE 5 schema includes this schema, so it is valid as part of 'the whole'. eg. If you remove the include directive from the EE5 schema, then the EE5 schema is invalid. 3,4,5) are somewhat related. I'm looking into this. Regards, Keith Chong WTP Web Services From: Rob Stryker <rob.stry...@redhat.com> To: "General discussion of project-wide or architectural issues." <wtp-dev@eclipse.org> Date: 02/16/2016 12:58 PM Subject: [wtp-dev] Question on XML Validation and oracle xsds Sent by: wtp-dev-boun...@eclipse.org Hi All: So after running into validation issues for our users' xml files using our schema for week after week, I finally decided to dig in a little and see how the JEE distribution handles validation of schema without so many upstream dependencies. It's clear that if a parent or referenced schema is invalid, the user will experience obscure validation errors when developing their own webapps etc. With that in mind I opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=487851 The usecase is that I simply took oracle's javaee_web_services_client_1_2.xsd from http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/javaee_web_services_client_1_2.xsd and tried to put it in a dynamic web project and let the validator work its magic. I wouldn't be posting here if it succeeded ;) The questions are basically: 1) Why are oracle's xsd's failing to validate? Are they really all invalid? 2) Why has nobody in the world asked Oracle to fix them? 3) How do we/you, as consumers / extenders of wtp, prevent errors in oracle's (or other upstream) xsd's from cascading down to our respective jee / appserver-specific schema when our schema import, extend, or reference upstream failing xsds? 4) Is this an error in source-editing plugins for not mapping directly to the most commonly used jee namespaces? Would that even fix the issue? (It didn't when I tried it but maybe I was doing it wrong). 5) If oracle won't fix their incomplete xsd's, is it reasonable for source-editing to do it, to make sure each and every one validate correctly, and that, by extension, all other schema that reference, import, or otherwise make use of oracles' schema won't be hit by a series of cascading validation errors? I suppose it's possible our product is simply "doing it wrong", but the fact that simply placing an official javaee oracle xsd into a clean JEE Mars eclipse environment fails validation is indicative to me that something bigger is going on here. - Rob Stryker JBoss Tools And Other Cool Stuff _______________________________________________ wtp-dev mailing list wtp-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________ wtp-dev mailing list wtp-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/wtp-dev
