Bug 15853 - Allow to plug-in different XML Catalog resolver in xslt task
Summary: Allow to plug-in different XML Catalog resolver in xslt task
Status: NEW
Alias: None
Product: Ant
Classification: Unclassified
Component: Core tasks (show other bugs)
Version: 1.5.1
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: ---
Assignee: Ant Notifications List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-07 19:15 UTC by Ella Belisario
Modified: 2008-11-24 03:57 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ella Belisario 2003-01-07 19:15:37 UTC
Current implementation of the XML Catalog in xslt task has a limitation -  
it is not possible to set a base path for entity and uri resolution. 
     In addition to that, a user may already have created catalogs in the 
external xml files and has his own implementation of the resolvers that work 
with that catalog format.  
     Could you please consider adding attributes to the XSLTProcess to set 
entity and uri resolver classes, something like this:
<xslt
      basedir   = "${basedir}/xml"
      destdir   = "${basedir}/result1"
      style     = "${transformer1}"
      extension = ".html"
      includes   = "Books.xml"
      uriResolver = "com.sun.resolver.tools.CatalogResolver"
      entityResolver = "com.sun.resolver.tools.CatalogResolver">
      <classpath refid = "classpath.resolver"/>
</xslt>
Comment 1 Jose Alberto Fernandez 2003-01-08 10:36:48 UTC
Alternatively XMLCatalog needs to be subclassable in the practical sense
so that users can pass a subclass with their own implementation of XMLCatalog.

The current implementation does things in such a way that subclassing is 
useless. We need a real delegation mechanism rather than copying.