So, I should be using something like this in my schemaLocation: xsi:schemaLocatio="http://www.savatech.ro/XFragConfig http://www.savatech.ro/XFragConfig";
and use the system id in my entity resolver to serve an alternate XSD file from my local classpath or if not found let the parser get the schema from the www site. Is this OK? Thanks for your help, Dan Corneanu. No, it's not a bug. There is no public identifier for the xsi:schemaLocation or xsi:noNamespaceSchemaLocation attrs. So the fact that you're seeing a null publicId in your entity resolver is normal. I don't think that you should be embedding file:///... system identifiers into your XML document, anyway. It's better to use the namespace URI as the "hint" in the xsi:schemaLocation attribute and let your registered entity resolver handle the details of mapping it to the correct entity. -- Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
