Thanks you all, your inputs and suggestions helped me in fixing my problem.
 
Just as an update, I created three matches in one pipeline, :
 
<map:match pattern="out/*.xml">
<map: generator src=""/>

<map:transform src=""/>

<map:transform src="">
<map:serialize/>
</map:match>

<map:match pattern="save_image">
<map:generate src=""/>
<map:transform/> // and save image in the file system
<map:serialize type="xml"/>
</map:match>

 <map:match pattern="get_xml_back">
<map:generate src=""/>
<map:serialize type="xml"/>
</map:match>

One concept that i was missing was each match has to end with a serializer and start with an generator.
 
Thanks much.

Thorsten Scherler <[EMAIL PROTECTED]> wrote:
Derek Hohls wrote:

>One way would be to use *4* pipelines;
>1. one that generates the original XML (and serializes it as XML)
>2. one that creates your image - based on a cocoon:/ call to Pipe 1
>3. one that creates your base HTML - based on a cocoon:/ call to Pipe
>1
>4. one that aggregates the results of pipes 2 and 3.
>
>Pipe 1 should be cached, so even though you call it twice, it
>should only have to do the work once...
>
>HTH
>Derek
>
>
>
+1

It is the cleanest solution!

thorsten

--
Thorsten Scherler

Departamento de Desarrollo de Proyectos
Sociedad Andaluza para el Desarrollo de la Sociedad de la Informacio'n S.A.U.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



- Java Developer


Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!

Reply via email to