On Thu, Jan 13, 2005 at 02:51:55PM +0100, Erik Bruchez wrote:
Well, only a far as their inputs are available, I guess ;-). I assume this step is repeated (for all remaining processors) at some point, maybe each time an output-producing processor has finished or only at the end?
No, this happens only once per pipeline. Their inputs are just read, they don't have to be particularly "available" ;-)
Huh... look at this example:
<p:processor ...> ... <p:output ... id="mydoc"/> </p:processor>
<p:processor name="oxf:file-serializer"> <p:input name="config"> ... </p:input> <p:input name="data" href="#mydoc"/> </p:processor>
Now I hope the file-serializer will be executed *after* the other processor in this example, as this first has to make "mydoc" available.
Yes of course, there is a dependency. It's really lazy evaluation: File serializer needs to run (because it doesn't have any output), so its input has to be read, so the processors it depends on are run, etc. There are a couple of scenarios in the tutorial.
-Erik
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ orbeon-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/orbeon-user
