Matthew J. Graham wrote:
> Thanks it does. I think that there are discrepancies between what is > in the tutorial disagrees with the online documentation: > >> * Pipeline outputs: Exactly 0, 1, or 2 outputs can be declared. > > The root element of a XPL document (config) defines: > > * Zero or more input or output parameters to the pipeline with > <p:param> > > No limit specified on the number of inputs or outputs.
There is no discrepancy. Imagine the same documentation about some Java code:
a) Your class must implement the Model interface with the following method:
public void run(String param1, String param2, String param3)
b) An inteface may declare methods. A method declaration can include any number of parameters.
This is exactly the situation you have. In one case, the documentation explains what the interface of a pipeline must be in the particular context of the PFC. In that case, your pipelines must have certain inputs and outputs with certain names.
In the other case, the documentation explains how XPL pipelines can expose inputs and outputs. The answer is: they can have any number of inputs and outputs, and they can be arbitrarily named. This is also in the tutorial:
"In general, pipelines can have zero or more inputs and zero or more outputs, each arbitrarily named. However, within the context of the page flow, as we are discussing here, a pipeline that wishes to participate as a model within the Presentation Server page flow architecture must adhere to specific conventions regarding the number and name of inputs and outputs. In the context of the page flow controller file, pipelines must: [...]"
Of course pipelines can be used in many situations, not just as components (actions, models, views) of the PFC. You can define your own pipelines and call them. There are many examples of this in the Presentation Server examples.
> No specification that there are restricted names on the inputs or > outputs. In fact, how would the <p:param type="output" name="bar"/> > in the example be referenced; not by: > > <p:output name="data" ref="bar"/>
Yes. The "name" attribute specifies an output of the processor. The "ref" attribute specifies the name of the output of the pipeline to connect to.
> but by: > > <p:output name="bar" ref="bar"/>
Only if your processor has an output named "bar".
> so the ref attribute is not really a connector mapping an output > from a processor to the output of pipeline as I had thought it was?
Yes it is :-)
-Erik
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
orbeon-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/orbeon-user
