W3C home > Mailing lists > Public > xproc-dev@w3.org > July 2009

RE: Difficulty overriding parameter values

From: <Toman_Vojtech@emc.com>
Date: Fri, 3 Jul 2009 05:19:20 -0400
Message-ID: <6E216CCE0679B5489A61125D0EFEC7871014899A@CORPUSMX10A.corp.emc.com>
To: <xproc-dev@w3.org>
It looks like a bug to me. Could you try to use p:pipeline instead of
p:declare-step for the top-level pipeline? I remember that in the older
versions of the spec, the default binding to the pipeline's primary
parameter input port happened only when p:pipeline was used. Perhaps
Calabash does not handle this properly with p:declare-step?


	From: xproc-dev-request@w3.org [mailto:xproc-dev-request@w3.org]
On Behalf Of Kevin Flynn
	Sent: Friday, July 03, 2009 11:06 AM
	To: xproc-dev@w3.org
	Subject: Re: Difficulty overriding parameter values
	No, that doesn't seem to work.
	The main pipeline has a primary parameter input port:
	<p:declare-step ...[ns-declarations]... name="import">
	      <p:input port="parameters" kind="parameter"/>
	and so does the called step eb:rng-ebk:
	  <p:declare-step type="eb:rng-ebk">
	        <p:input port="source"/>
	        <p:input port="parameters" kind="parameter"/>
	        <p:output port="result"/>
	This works:
	            <p:input port="parameters">
	                <c:param name="parent" value="book"/>
	This doesn't:
	            <p:input port="parameters"/>
	            <p:with-param name="parent" select="'book'">
	Explicitly connecting the port to the import/parameters port
makes no difference, as expected.
	Is this a bug in Calabash, perhaps?
Received on Friday, 3 July 2009 09:20:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:16:48 UTC