Follow up:
After adding a namespace to the extension schema and tweaking a bit, I was
able to get this to work using your suggestion. Thanks!
There are two things I don't love about this solution:
First, I have to add a namespace to the externsion schema, which I do not
maintain or have control over. However, I guess it's really the proper
thing to do, as most parsers are processing namespaces now.
Second, the externalSchemaLocation setting does not give me control over
which schema files get loaded, as the parser seems to check the directory
where the instance file is located first. I was using loadGrammar() to
cache the schema files in advance, and that allowed me to specify exactly
which files to load. My understanding is that I may have to implement an
entityResolver to control that.
Vitaly Prapirny wrote:
>
> You can define namespaces for base and extension schemas and then set
> parser property XMLUni::fgXercesSchemaExternalSchemaLocation accordingly
> ("base_schema_ns base_schema.xsd extension_schema_ns ext_schema.xsd")
>
> Good luck!
> Vitaly
>
>
--
View this message in context:
http://old.nabble.com/Validation-of-Instance-Extended-Through-%27any%27-Element-tp31758318p31795714.html
Sent from the Xerces - C - Users mailing list archive at Nabble.com.
