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=3321 *** shadow/3321 Tue Aug 28 14:12:51 2001 --- shadow/3321.tmp.15202 Tue Aug 28 14:12:51 2001 *************** *** 0 **** --- 1,26 ---- + +============================================================================+ + | Inconsistent Docs, One is Wrong | + +----------------------------------------------------------------------------+ + | Bug #: 3321 Product: Xerces-J | + | Status: NEW Version: 1.4.3 | + | Resolution: Platform: PC | + | Severity: Normal OS/Version: Windows NT/2K | + | Priority: Other Component: Docs | + +----------------------------------------------------------------------------+ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + | CC list: Cc: | + +----------------------------------------------------------------------------+ + | URL: | + +============================================================================+ + | DESCRIPTION | + In the DOMParser methods (Full API Documentation) the + setExternalNoNamespaceSchemaLocation ID is documented as + http://apache.org/xml/properties/validation/schema/external- + noNamespaceSchemaLocation. I spent a lot of time before I realized that this + is incorrect, because your ParserWrapper turns off error reporting for this + kind of error. + + In the "Properties" section accessed off the main page of the documentation + this ID is documented as http://apache.org/xml/properties/schema/external- + noNamespaceSchemaLocation Note that this is different. It also works. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
