I try to use schema validation with preparsed schemas.
Within a more complex example I failed to preparse and cache a schema that imports an already loaded schema.
Example: schema B includes schema A schema C includes schema A
loadGrammer() of schema B failes because target namespace of schema A is already known.
I helped myself with adapting the GrammarResolver::cacheGrammars() function.
The new behaviour is to ignore caching of a new schema that is already known, and not to throw an exception as in original code.
With this little change anything (preparsing and validation) works fine.
Here my questions:
- Are there any reasons why GrammarResolver throws an exception if it should add an new Grammar to the cache? (Maybe I don't see other impacts yet)
- Wouldn't be this change be useful for all xerces users?
- I my eys an additional merging functionality would be useful, that updates and enhances definitions of an already cached grammar. Example: file a.xsd and b.xsd define elements of the same target namespace. It would be useful if the internal grammar representation would be a union of file a and b What do you think?
Regards
Matthias
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
