RE: Parameters

> So by pipeline user, do you mean the person typing the command line?
> If so, it's the same way s/he knows today to write
> 
>   calabash . . . -p struct=@foo.xml
> 
> S/he does it because the documentation of the pipeline says that
> there's an xslt step in the pipeline with 'struct' as a param.
> 
> And, to carry on the example, that there's a _different_ xslt step
> whose parameters are set from the 'other' parameter map, which has a
> foo param.

I guess what I am after is whether the pipeline declares the parameter maps that it 'accepts' in any way. Is the idea that the unnamed ('') parameter map is always available on any pipeline, and if you want additional parameter maps (for example, 'struct'), the pipeline must declare an option named 'struct' of type map, something like below?

<p:declare-step>
  <p:option name="struct" as="map:map(xs:QName, item()*)"/>
  ...
  <!-- the sub-pipeline can access two parameter maps here: '' and 'struct' -->
</p:declare-step>

Also, what about pipelines invoking other pipelines? Suppose a pipeline A invokes a pipeline B. How does A pass parameters to the parameter map '' of B? (I assume that for named parameter maps, such as 'struct', you would simply use <p:with-option name='struct'.../>.)

Regards,
Vojtech

--
Vojtech Toman
Consultant Software Engineer
EMC | Information Intelligence Group
vojtech.toman@emc.com
http://developer.emc.com/xmltech

Received on Friday, 21 February 2014 08:23:00 UTC