Pradeep, In addition to Neil's comment, there's also sort of a "good form" element to this. Placing such paths in the systemId pins your implementation/deployment down, especially if you are receiving these xml documents from an external source. As suggested, use an EntityResolver with the base dtd name. Use the EntityResolver to locate the dtd as needed with your implementation. This way, you don't have to require that content be changed if your deployment changes, which can be a real pain if you are receiving documents from multiple sources.
:-) BradO -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, March 05, 2001 11:07 AM To: [EMAIL PROTECTED] Subject: Re: Likely bug when resolving relative paths for SYSTEM identifiers Hi Pradeep, The problem is that Xerces is expecting a URI, not a path (and especially not a Windows path) as a systemId. i.e., the first thing not to do in a systemId is to use backslashes. :-) Hope that helps, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 416-448-3519, T/L 778-3519 E-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
