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=27450>. 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=27450 Validating against schemas importing other schemas ------- Additional Comments From [EMAIL PROTECTED] 2004-03-04 20:08 ------- Thank you, Khaled. I see. It's not part of the base class' DOMBuilder interface, though. (As in http://xml.apache.org/xerces-c/apiDocs/classDOMBuilder.html ) Having to narrow the return value of DOMImplementationLS::createDOMBuilder has a somewhat hackish feel to it. And I also seem to be getting confused about the different DOM parsers (so what was XercesDOMParser about, should I be using it instead of the DOMBuilder?). But this is getting off-topic with regards to this bug. (I'd appreciate a private mail, maybe with a document pointer, or a separate thread, on this subject.) So yes, using the XMLEntityResolver works better, turning this solution from an awkward hack to a merely annoying workaround. I guess I'd still like the test program to work, picking up the schemaLocations from either the XML document or from the XercesSchemaExternalSchemaLocation attribute. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
