DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15853>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15853 Allow to plug-in different XML Catalog resolver in XSLTProcessor task Summary: Allow to plug-in different XML Catalog resolver in XSLTProcessor task Product: Ant Version: 1.5.1 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Enhancement Priority: Other Component: Core tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] 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> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
