Hi, David. does enclosing your XML in a CDATA section help? It should just get written out without being interpreted, and it works for me in the toolfactory - the contents still get written out but without the CDATA section. <configfiles> <configfile name="loadTestxml"> <![CDATA[ *<!DOCTYPE crystal SYSTEM "/usr/share/sgml/crystal.dtd"> <!--- Load a pos file called "babla.pos" --> <crystal> <version value="0.0.1"/> <posload name="${posfile}"/> </crystal>* ]]>* * </configfile> </configfiles> On Fri, Mar 8, 2013 at 4:23 PM, David Angot <davida@intersect.org.au> wrote:
Hello,
I have a tool that takes an XML file as input. So I thought it would be a good idea to put it in the <configfiles> tag, to replace some of the variables.
Quick example :
.... <inputs> <param name="posfile" type="data" label="Posfile" help="Posfile you want to input to POSGEN" format="pos" /> </inputs>
<configfiles> <configfile name="loadTestxml"> *<!DOCTYPE crystal SYSTEM "/usr/share/sgml/crystal.dtd"> <!--- Load a pos file called "babla.pos" --> <crystal> <version value="0.0.1"/> <posload name="${posfile}"/> </crystal> * </configfile> </configfiles> ....
But when I load the tool configuration, it seems that the XML in <configfile> is interpreted, and/or I don't get anything in the input file.
Is there a way to do what I want ?
Cheers,
-- *David *