Hi Maarten,

Thx for this. I'm looking at some <xmltask> work next week so I'll review then. I see no major reason why it won't go in - I might change the element name from <sequential> however - but I understand it's trying to leverage off the <parallel> task.

Brian

Maarten Coene wrote:
Hi Brian,

I've created a patch for RFE 1192359.
This patch changes the <call> element to allow the following construction:
<xmltask source="test.xml">
    <call path="/modules/module">
        <param name="modName" path="@name"/>
        <param name="modOwner" path="@owner" default="n/a"/>
        <sequential>
            <echo>Module Name: @{modName}</echo>
            <echo>Module Owner: @{modOwner}</echo>
        </sequential>
 
   </call>
</xmltask>

If you have the following XML:

<modules>
    <module name="module1" owner="owner1" />
    <module name="module2" />
    <module name="module3" owner="owner3" />
</modules>

the result of calling the xmltask in the example above will be:

Module Name: module1
Module Owner: owner1
Module Name: module2
Module Owner: n/a
Module Name: module3
Module Owner: owner3

Could you please review this patch, because I really need such functionality and I'd prefer to work with official releases instead of patching it myself.
http://sourceforge.net/tracker/index.php?func=detail&aid=1192359&group_id=27398&atid=390338

Thanks,
Maarten

-- 
Brian Agnew                  http://www.oopsconsultancy.com
OOPS Consultancy Ltd         brian @ oopsconsultancy.com
Tel: +44 (0)7720 397526
Fax: +44 (0)20 8682 0012

Reply via email to