Re: p:pipeline

Norman Walsh wrote:
> / Rui Lopes <rlopes@di.fc.ul.pt> was heard to say:
> | I'm with Jenny on this one, I believe that component declarations
> | shouldn't occur inside a pipeline, but on a separate file (as in
> | configuration file).
> 
> That seems an unnecessary burden. I don't want to have to put each
> p:pipeline in a separate file, somehow I want to be able to combine
> them. Whether I do this by simply nesting or by adding a new wrapper
> is a separable question.

I agree. I want to be able to define two pipelines in the same file, as 
well as in separate files.

> Once I've got the ability to have two p:pipeline's in the same file, I
> want to be able to put a p:component-definition in that file too, so
> that I can define the three components I need (two pipelines and one
> extension component) in the same place.

For interoperability sake, I would prefer implementation-specific 
components to be defined elsewhere. Or, at least, if an extension 
component is defined but not used, an error isn't raised.


Cheers,
Rui