- From: <Toman_Vojtech@emc.com>
- Date: Tue, 12 Feb 2008 08:24:58 -0500
- To: <public-xml-processing-model-comments@w3.org>
> / Toman_Vojtech@emc.com was heard to say: > |> Yes, you do, you just have to use the "full form". There's nothing > |> wrong with a pipeline document that begins: > |> > |> <p:declare-step type="my:pipeline" xmlns:p="..." xmlns:my="..."> > |> <p:input port="fred"/> > |> <p:input port="barney"/> > |> <p:output port="bedrock"/> > |> > |> <p:xslt ...> ... </p:xslt> > |> <p:xslt ...> ... </p:xslt> > |> <p:xslt ...> ... </p:xslt> > |> </p:declare-step> > |> > |> and a pipeline processor is expected to be able to run > that pipeline > |> just as if it had had "p:pipeline" as its document element. > | > | Except that neither of "fred", "barney" or "bedrock" can be > declared > | primary and that I always have to make sure that the last > step in the > | pipeline has a default readable port... > > Sez who? > > <p:declare-step type="my:pipeline" xmlns:p="..." xmlns:my="..."> > <p:input port="fred"/> > <p:input port="barney" primary="true"/> > <p:output port="bedrock" primary="false"/> > > <p:xslt ...> ... </p:xslt> > <p:xslt ...> ... </p:xslt> > <p:xslt ...> ... </p:xslt> > </p:declare-step> > > In the "full form", you can make any declaratiosn you like. > I'm not sure it makes a whole lot of sense for a pipeline to > have a single non-primary output, but there you go. Oh, I was talking about the case when using the p:pipeline element. Somehow I didn't notice you were using p:declare-step. Vojtech -- Vojtech Toman Principal Software Engineer EMC Corporation Aert van Nesstraat 45 3012 CA Rotterdam The Netherlands Toman_Vojtech@emc.com
Received on Tuesday, 12 February 2008 13:21:18 UTC