> Another simple way to achieve the same is setting the > fgXercesSchemaExternalSchemaLocation and > fgXercesSchemaExternalNoNameSpaceSchemaLocation parameters (or using > setExternalSchemaLocation and setExternalNoNamespaceSchemaLocation > methods if available).
If you're writing code, yes, in contrast to just trying to use the utilities as written, because they don't expose options for those settings (not that they couldn't). But it's also important to note that naively using those options won't work either, because (in what I've always considered a buggy "feature", though it's probably to spec) those overrides only apply to the schema lookup *within* the XML instance being validated, and NOT to any lookup of imported schemas in the schemas you pull in. They only go one layer deep, in other words. So a complete solution (in code) really has to register an EntityResolver and fully hijack the whole mechanism in some brittle ways, unfortunately. -- Scott --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
