ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knuplesch, Juergen" <>
Subject AW: Xalan hinders saxon: converting property values
Date Thu, 08 Oct 2009 09:26:51 GMT

I did put saxon on the classpath as some docu told:

>         <classpath>
>           <pathelement location="${ant.xslt.saxonjar}" />
>         </classpath>

Afterwards it worked without xalan on the classpath.
When I put xalan into Ants libpath it fails.
Probably Ant is using now xalan.

I wanted to try factory, but there is a jar missing. 
I did not find out which jar is missing.
Maybe I try this later...

I tried a different plan.
I installed the Saxon Ant-xslt task.
But this task does not understand my windows full filenames.
It works when I replace all \ to / in the calling params.
Is there a way to convert in a property all "\" to "/" ?

Greetings Juergen

Jürgen Knuplesch          
icon Systemhaus GmbH                Tel. +49 711 806098-275
Sophienstraße 40                    
D-70178 Stuttgart                   Fax. +49 711 806098-299

Geschäftsführer: Uwe Seltmann
HRB Stuttgart 17655
USt-IdNr.: DE 811944121 
-----Ursprüngliche Nachricht-----
Von: Stefan Bodewig [] 
Gesendet: Donnerstag, 8. Oktober 2009 09:39
Betreff: Re: Xalan hinders saxon

On 2009-10-07, Knuplesch, Juergen <> wrote:

> After taking xalan 2.7.1 into Ants lib path, my XSLT using saxon dont 
> work anymore:

Are you sure Ant is using Saxon at all after your change?  I don't see any explicit configuration
for saxon here

>  <xslt style="${dsf.comparedsffiles.xsltfile}"
>           in="${}"
>           out="${dsf.comparedsffiles.out}" >
>         <classpath>
>           <pathelement location="${ant.xslt.saxonjar}" />
>         </classpath>
>         <param name="filename.1" expression="${dsf.comparedsffiles.file1}"/>
>         <param name="filename.2" expression="${dsf.comparedsffiles.file2}"/>
>         <param name="errorfilename" expression="${dsf.comparedsffiles.error}"/>
>     </xslt>

Does it help if you add a <factory> nested element to the task?


To unsubscribe, e-mail: For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message