DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17314>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17314 XMLGrammarPool operation [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[EMAIL PROTECTED] Severity|Blocker |Enhancement Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From [EMAIL PROTECTED] 2003-02-26 07:54 ------- Thanks Sandy. with some code changes I've been able to get it to work in 2.3.0. I've had to change each schema to have a distinct namespace. I've dropped severity to Enhancement rather than Closed because the operation of the grammar bucket does not match with XML Schema specs. I say this because each schema may have one or zero target namespaces (via the attribute), but there is nothing to prevent many schemas sharing the same namespace. The documented operation of the grammar bucket is to hash on the namespace. I got the result one would expect from the documentation when I used the <include > tag to reference another schema with the same namespace; it did not load the new schema, attempted to validate against the other one, and failed. The requested enhancement is to alter operation of the grammar bucket so it hashes on the schemaLocation hint carried in <include> and <import> statements. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
