ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 47704] New: Allow Project to take an XMLCatalog instance for use in configuring catalog-aware tasks
Date Wed, 19 Aug 2009 04:19:37 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=47704

           Summary: Allow Project to take an XMLCatalog instance for use
                    in configuring catalog-aware tasks
           Product: Ant
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Core tasks
        AssignedTo: notifications@ant.apache.org
        ReportedBy: drmacro@yahoo.com


--- Comment #0 from Eliot Kimber <drmacro@yahoo.com> 2009-08-18 21:19:34 PDT ---
When running Ant from within for example a CMS system exposed as a Web app,
there are several problems with managing resolution of XML resources (entity
resolution, URI resolution):

- It is not possible to have different classpaths for different uses of Ant
(for example, different DITA Open Toolkit instances accessible through main CMS
application)

- Setting a classpath on XMLCatalog in the build file or task (e.g., within
<xslt>) appears to have no effect, even when resolver.jar is on the classpath
(but in any case, just using CatalogManager with static catalog files is not
sufficient.

- There is no way to initialize Project with a pre-existing URI resolver, for
example, one that does CMS-specific resolving of CMS-specific URLs.

Enhancement request:

Allow Project to have an XMLCatalog instance set on it and use this catalog to
initialize e.g., XSLTProcess.

In examining the 1.7.1 source I could find any place that
setConfiguredCatalog() is ever called on XSLTProcess. I think this may be a
code bug but I haven't had a chance to verify that.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Mime
View raw message