John, Volker, I was about to ask the same question.
> > Dear colleagues, > > > > does anybody know the difference between: > > > > <map:pipeline> > > <map:match>...</map:match> > > <map:match>...</map:match> > > </map:pipeline> > > > > and > > > > <map:pipeline> > > <map:match>...</map:match> > > </map:pipeline> > > > > <map:pipeline> > > <map:match>...</map:match> > > </map:pipeline> > http://xml.apache.org/cocoon/faq/faq-sitemap.html#faq-3 I re-read the entire user doc package last night and came across that section but, with all due respect, that documentation doesn't explain the benefits of one approach or the other. Sure, one pipeline can be hidden but what other reasons exist for separating into multiple pipelines? [Note: Volker's example didn't specify an internal pipeline] - for example, in the default sitemap (which is quite large), why are there so many pipelines? Couldn't it be done with all the matchers inside one pipeline? - in there a performance difference? - in cases where you aggregate XML parts using <map:aggregate> and the cocoon:/ protocol, are serializers skipped perhaps? Thanks, Per. --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
