PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2882 *** shadow/2882 Mon Jul 30 03:06:23 2001 --- shadow/2882.tmp.25482 Mon Jul 30 08:31:12 2001 *************** *** 162,165 **** > : XML and <a href="http://jini.netbeans.org/";>Jini</a> modules</address> ! -- Petr Nejedly NetBeans/Sun Microsystems http://www.netbeans.org --- 162,201 ---- > : XML and <a href="http://jini.netbeans.org/";>Jini</a> modules</address> ! -- Petr Nejedly NetBeans/Sun Microsystems http://www.netbeans.org ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-07-30 08:31 ------- ! >The second thing I don't understand is why I have to switch some ! >proprietary feature to prevent Xercer from asking for DTD when the ! >document itself specifies it is standalone and I'm not validating. ! >Can somebody explain me this behaviour? ! ! There are several issues you raise. ! ! First, there IS a "standard" feature to control reading the DTD, but it is less ! specific than the proprietary one that you mention. The ! "http://xml.org/sax/features/external-parameter-entities"; feature will also ! disable reading the external DTD subset in addition to other external parameter ! entity references that may appear in the internal DTD subset. ! ! Second, the standalone declaration is only meaningful to the parser if you are ! reporting validation errors, otherwise it is ignored since the only effect that ! it can have is to fail validity constraints. ! ! Lastly, there is a misunderstanding about what the "validation" feature means. ! The Xerces parser is a validating XML processor. A validating processor, "at ! user option", reports failures of validity constraints. The validation feature ! is that option. It should not have any other effect on processing. ! ! As an example, let's say that your document says that it is standalone, and ! references an external DTD subset, and you have turned off reporting of validity ! constraint failures. If the external DTD subset were to introduce a defaulted ! attribute value, that attribute would be added to the infoset of the document ! and the document would in fact be invalid since it is not in fact standalone. ! However, the document may still be well-formed and since you are not reporting ! validity constraint failures then everything will complete successfully. ! ! So you see, turning it around, without some indication from the application to ! the parser that it not read the external DTD subset, the parser must read that ! parsed entity to find possible changes introduced by that entity. Not reporting ! validation errors is an orthogonal issue. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
