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=8252>. 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=8252 Chained call to external entities is not conform to W3C XML specification Summary: Chained call to external entities is not conform to W3C XML specification Product: Xerces2-J Version: 2.0.0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: SAX AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hi, Mr Xerces developper, I encountered a new bug when I tried to avoid the problem #8249. If urn doesn't work fine in certain circumstances, I added a real file in the chain call. The document contains : <!ENTITY % refdoc SYSTEM "urn:x-semir:RESS:dtd/refdoc.ent"> The entity resolver finds the file refdoc.ent that contains : <!ENTITY % ENTITIES SYSTEM "entities.ent"> %ENTITIES; Notice that this is a way to avoid the problem reported in bug #8249, but, as refdoc.ent and entities.ent were put in the same folder, the SAX parser try to read entities.ent in the same folder as the document. To make it work, I use a relative path from the document location to the entities location. But the W3C XML specification tells that (see �4.2.2) : ".../... A URI might thus be relative to the document entity, to the entity containing the external DTD subset, or to some other external parameter entity." The behaviour I obtained is not the one described in the W3C XML spec. Best regards, Philippe Poulard, INRIA --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
