xml commons resolver
Posted: Tue Mar 02, 2010 11:51 pm
This is either a feature request, or a question about how I should solve a problem.
I use custom catalog entries with xml commons resolver (i.e. I extend Catalog and OASISXmlCatalogReader), but oxygen seems to use it's own version of classes with the same name as classes in xml commons resolver, in oxygen.jar, so my URI resolver was failing at runtime. Specifically, there is no Catalog.catalogEntries field in org.apache.xml.resolver.Catalog that is in oxygen.jar.
I am using a class loader to get around the problem, by explicitly loading classes from resolver.jar instead. But, unless I should be solving this a different way, it would be convenient if oxygen did not include classes below the package org.apache.xml.resolver that are different from the classes in xml commons resolver.
I use custom catalog entries with xml commons resolver (i.e. I extend Catalog and OASISXmlCatalogReader), but oxygen seems to use it's own version of classes with the same name as classes in xml commons resolver, in oxygen.jar, so my URI resolver was failing at runtime. Specifically, there is no Catalog.catalogEntries field in org.apache.xml.resolver.Catalog that is in oxygen.jar.
I am using a class loader to get around the problem, by explicitly loading classes from resolver.jar instead. But, unless I should be solving this a different way, it would be convenient if oxygen did not include classes below the package org.apache.xml.resolver that are different from the classes in xml commons resolver.