Posted by fl.schmitt(ops-users) on May 11, 2011; 8:27am
URL: https://discuss.orbeon.com/can-t-get-2-processor-in-1-pipeline-to-work-tp3514050p3514179.html

James,

> Isn't each processor inside p:config called sequentially?

AFAIK no, because of the lazy evaluation model. In your save_all.xpl, it
seems producing the output is simply done by the save.xpl, so it seems
that there's no need to call delete_all.xpl. If the save.xpl depends on
a succesfull execution of delete_all.xpl, you will have to express that
dependency explicitly.

To do so, you could connect both pipeline processors:

- add a p:output to the first processor (calling delete_all.xpl) to
expose the result of delete_all.xpl;
- add a p:input the the second processor (calling save.xpl) that
references the output of the first processor.

This way, save.xpl will be called only if delete_all.xpl has finished;
you may even handle different results of the delete_all "action", for
example if the delete wasn't succesful for any reason.

HTH
florian




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws