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

RE: Secondary ports on pipeline need be explicitly declared non-primary?

From: <Toman_Vojtech@emc.com>
Date: Thu, 5 Mar 2009 09:01:51 -0500
Message-ID: <6E216CCE0679B5489A61125D0EFEC7870EC09128@CORPUSMX10A.corp.emc.com>
To: <xproc-dev@w3.org>
Hi,
 
You are right. If you do this:
 
<p:pipeline>
  <p:input port="extra"/>
</p:pipeline>
 
the port "extra" should be non-primary. That you have to do
primary="false" seems like a bug in Calabash.
 
Regards,
Vojtech


________________________________

	From: xproc-dev-request@w3.org [mailto:xproc-dev-request@w3.org]
On Behalf Of Leif Warner
	Sent: Thursday, March 05, 2009 2:05 PM
	To: xproc-dev@w3.org
	Subject: Secondary ports on pipeline need be explicitly declared
non-primary?
	
	
	I made a p:pipeline that had a secondary input port,
	called it with "calabash -i source=doc.xml -i what=elem.xml
test.xpl", and it gives me:
	

		Error  : Pipeline failed: err:XS0030: null  It is a
static error to specify that more than one input port is the primary.
		

	I try a few options, then try Example #2 in
http://www.w3.org/TR/xproc/
	Same thing, same error message.
	Turns out if I put <p:input port="schemas" sequence="true"
primary="false"/>, it works.
	This is not the behaviour I expected after reading section 2.3,
and the description of implicit "source" input ports in p:pipelines...
	-Leif Warner
	
Received on Thursday, 5 March 2009 14:04:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 5 March 2009 14:04:47 GMT