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=6200>. 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=6200 Parser failure with validate=true when processing stylesheet ------- Additional Comments From [EMAIL PROTECTED] 2003-10-08 11:55 ------- Configuring the xml-parser component with validate=true will never work, simply because this is the parser used to parse every single XML file. This means also XSLT stylesheets, JXTemplate files, Woody form definition, or any arbitrary XML markup. We can't possible have DTD's for all these formats, and can't require the DOCTYPE to be present everywhere. What would be needed in my opinion is a ComponentManager where we can explicitely resolve the dependencies. So you would then be able to configure multiple instances of the xml-parser and let one filegenerator use a validating parser and let another one use a nonvalidating parser. Something similar is currently done for the store component: there are multiple stores and for some components you can explicitely configure which store role they should use. We could do the same thing for the xml-parser, i.e. make a "parser/validating" role and a "parser/nonvalidating" role and make it possible for relevant components (mostly the FileGenerator I think) to configure which role they should use. However this seems like an abuse of the role concept, I'd rather have a component system where the dependencies can be explicitely provided (I know this is possible in the Phoenix container, not in ECM, don't know about the others).
