On 16/04/2008, Steve Loughran <[EMAIL PROTECTED]> wrote: > > I've given up with the xslt task now; > > Need it to handle a different parser (xercesImpl) for xIncludes > > and Apache resolver.jar for catalogs - I don't think > > the xslt task can hack that? > > > > -you should be using xercesImpl from ANT_HOME/lib anyway...drop in a new > version if you want to change that. > -resolver.jar is used for catalog resolution; I dont know what happens with > xincludes > > if xinclude doesnt work when resolver.jar is on the classpath, that's a > feature to fix...
See the <java example earlier. Saxon needs the parser specifying with -x command line option? <arg line="-x org.apache.xml.resolver.tools.ResolvingXMLReader"/> <arg line="-y org.apache.xml.resolver.tools.ResolvingXMLReader"/> <arg line="-r org.apache.xml.resolver.tools.CatalogResolver "/> I don't think (I'm not 100% sure though) it is available using a -D system property. Since <xslt/> task doesn't allow for 'command line' arguments of this type, I don't think I can get it to work? There is also an outsanding bug relating to Saxon linked from a page with a solution http://vocaro.com/trevor/blog/2007/01/08/how-to-use-saxon-with-ant/ so it's all looking a bit messy? I tried it with Xalan but that seems not to support the parser selection using the <factory/> child :-) regards -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
