Jos Vos wrote:
> Hmm... I'm afraid you are right ;-). My problem seemed to be that
> I was not (always) using (all) output docs of the subpipeline and
> then parts of the subpipeline (or the whole subpipeline) were not
> executed.
>
> What I tried to achieve:
>
> Call an "initialization" subpipeline in every model pipeline that
> initializes some documents in the session (using scope-serializer)
> if needed (or retrieve them) and results in some session documents.
>
> But these documents might not always (all) be used, dependent on the
> context (model). So, I'm afraid having such a generic subpipeline
> is only possible if I make sure all output docs are used in every
> model pipeline, maybe only in a null-serializer. Right?
This is a fairly typical scenario. If I understand well, you want an
initialization pipeline (say, "init.xpl") declaring an output (say,
"abc"). But, this output may or may not be read by the calling
pipeline.
So within init.xpl, just make sure a null serializer is reading the
data just before it is sent to the output. This way, you only have to
do this once in init.xpl, and the calling pipelines can do whatever
they want: read the output if they want to, or just ignore it.
E.g. something like:
<p:config>
<p:output name="abc" type="output">
...
<p:output name="..." id="abc-output" ref="abc"/>
</p:processor>
<p:processor name="oxf:null-serializer">
<p:input name="data" href="#abc-output"/>
</p:processor>
</p:config>
-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
