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=14239>. 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=14239 Entity Resolver gets different "systemId" on Entity Resolver callback. Summary: Entity Resolver gets different "systemId" on Entity Resolver callback. Product: Xerces2-J Version: 2.0.0 Platform: Sun OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other Component: SAX AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] To reproduce this, we need to do the following: * Get the SAX parser, set a dummy entity resolver, which only prints the "systemId" and returns null [ handing over the default parser to parse] * get a xml file [ filename is in Japanese "Shift_Jis" multi byte non ascii encoded] - Set the doctype's SYSTEM as relative URI. for eg: <!DOCTYPE extension SYSTEM "h:/core/../core/extensions.dtd" > * Parse the file using SAX parser The output: I am getting as system Id h:/core/../core/extensions.dtd If I change the fileName from japanese multi bute character to english [ascii] I gets the output file:/h:/core/extensions.dtd My guess is: Since the system assumes the default base URI as the location of xml file, while computing the absolute URI of the given relative uri....It backfires due to multi byte character. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
