Can you use XMLCatalog to resolve xsds in schema import statements? If so, what is the preferred/best practice? I want to package the xsds in a jar, so using a relative schemaLocation has not worked. So far I am trying to do something like: SchemaFactory factory = SchemaFactory .newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI)...
I'm using an OASIS v 1.1 compatible resolver (Norm Walsh's XMLResolver in conjunction with the catalog below. However, I'm pretty sure I've made some sort of obvious error here (this is the first time I've needed to use v 1.1 features) since attempting to resolve OxChapML.dtd fails. Can anyone see something obviously wrong with this? Or ...
Dear forum, what is the difference between the JDK contained import com.sun.org.apache.xml.internal.resolver.CatalogManager; and the one contained in the Apache Xerces project import org.apache.xml.resolver.tools.CatalogResolver; are there any benefits of using the latter for simple Catalog Resolving? From what I read on Wikipedia ...
A Java package I want to use was written by people who neglected to include catalog resolver support. In Java 1.5 / 1.6 + Xerces, is there any way to 'inject' a catalog resolver via a system property? ...