Smooks Splitting Message

[ama1]

Hi,
I trying to split a message into pieces and write those pieces to a file.

But in difference to the available examples I want to write all e.g. order-items to a file order-item.txt and dont want to create a file/order-item.

I tryed a configuration like that (my order-item is my product, which is a child element of Company):

<!-- Hotel - Create/open a file output stream. -->
 <file:outputStream openOnElement="Company" resourceName="hotelSplitStream">
 <file:fileNamePattern>hotel.csv</file:fileNamePattern>
 <file:destinationDirectoryPattern>d:/temp/inbound/</file:destinationDirectoryPattern>
 <file:listFileNamePattern>sam-files.lst</file:listFileNamePattern>
 <file:highWaterMark mark="1" />
 </file:outputStream>

 <!-- Hotel -->
 <ftl:freemarker applyOnElement="Product">
 <ftl:template><!--${bla}--></ftl:template>
 <ftl:use>
 <ftl:outputTo outputStreamResource="hotelSplitStream" />
 </ftl:use>
 </ftl:freemarker>

But that produces me this error message:

Caused by: org.milyn.SmooksException: OutputResource 'hotelSplitStream' not bound to context. Configure an 'org.milyn.io.AbstractOutputStreamResource' implementation, or change resource ordering.

Apperently, the stream is only visible on the same element...?
Is my use case feasible like this? Or do I have to find another way?

[tfennelly]

What does the input message look like?

[ama1]

The XML - input message looks basicly like that:

<Delivery>
 <Company>
 <Agencies>
 <Agency>
 <Dossiers>
 <Dossier>
 <Products>
 <Product/>
 </Products>
 </Dossier>
 </Dossiers>
 </Agency>
 </Agencies>
 </Company>
</Delivery>

Whereas the plural in the tag name indicates a 1-n relation, meaning under e.g. Agencies are multiple Agency elements.

What I plan is to create csv-files out of this xml-message. Each csv-file should hold a specific entity (like product or agency etc.)

[tfennelly]

From what I see there... it looks as though it should work... the file:outputStream is scoped around the Company fragment (openOnElement="Company") and the templating is applied on the Product fragment (applyOnElement="Product"), which is within the "Company" fragment.

If you could send an executable example based on either the ESB quickstart or Smooks example formats, then I could have a quick look.