You also could do
- create a new buildfile
- invoce that buildfile
not tested...
<presetdef name="append">
<echoxml file="sub.xml" append="true"/>
</presetdef>
<append>
<project><xslt in="in.xml" out="out.xml" style="in2out.xsl">
</append>
<ac:for param="name" list="one,two,three">
<sequential>
<append> <param name="@{name}" value="[EMAIL PROTECTED]"/> </append>
</sequential>
</ac:for>
<append> </xslt></project> </append>
<ant file="sub.xml"/>
Jan
>-----Ursprüngliche Nachricht-----
>Von: Holger Rauch [mailto:[EMAIL PROTECTED]
>Gesendet: Montag, 11. September 2006 12:08
>An: [email protected]
>Betreff: Invoking Ant XML fragments (Was:Re: Adding variable
>no of <param> elements to <xslt> task)
>
>Hi Antoine,
>
>after googling a bit, I found this:
>
>http://www.oopsconsultancy.com/software/xmltask/#examples
>
>=> It's possible to create an XML fragment describing the <xslt> task
> (including the <param> elements for the stylesheet parameters)
>
>But that leads me to a totally different question: Is it
>possible to "invoke" such a dynamically created fragment (i.e.
>the <xslt> task is invoked in a way as if the fragment were
>already contained in the Ant file instead of being dynamically
>generated)?
>
>(Reason why I'm asking is that I want to avoid - if possible -
>style breaks by introducing beanshell code).
>
>Thanks in advance for any info!
>
>Kind regards,
>
> Holger
>
>On Sun, 10 Sep 2006, Antoine Levy-Lambert wrote:
>
>> [...]
>> I would extend the XSLTTask at your place.
>> [...]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
