Loop, Atomic Transaction

You shouid consider using the xpath function, along with the position() xpath function.

Initialize a variable to contain the number of items:

nbItems = System.Convert.ToInt32(orderMsg, “count(//*[local-name()=’item’ and namespace-uri()=’ns’)”);

Then, initialize a counter:

itemcounter = 1;

In a loop, while itemcounter <= nbItems

Use another xpath expression to extract the item information. For instance, suppose your item has only one information, the item description:

itemDesc = xpath(orderMsg, “//*[local-name()=’item’ and namespace-uri()=’ns’ and position() ='” +itemcounter + “‘]”);

Increment itemcounter before the next loop.

That way, you won’t have to use an atomic scope.

Another way would be to treat your order as an envelope and each item as a separate document, disassemble it in a pipeline and process it in a sequential convoy.

You can use pipline XML dissassembler component to parse the order list into individual orders. You can call the receive pipeline from the orchestration to achieve this.

Here is an example to help you:

http://geekswithblogs.net/sthomas/archive/2005/06/16/44023.aspx

Also if you are not concerned about the order of processing each orders, use can use a Start Orchestration Shape and use Send/Receive request to FTP server in the called orchestration. Make sure the called orchestration should not be Atomic.

Let me know if it helps.