cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven D. Majewski" <>
Subject Re: view after aggregate
Date Thu, 08 Mar 2007 20:01:25 GMT

On Mar 8, 2007, at 2:31 PM, Bertrand Delacretaz wrote:

> On 3/8/07, Steven D. Majewski <> wrote:
>> Can anyone tell me how to set up a view to get the
>> results after a <map:aggregate>...
> Use <map:aggregate label="xyz">, assuming xyz is defined in <views>
> -Bertrand

Didn't work:

First I tried label="content" , since it was already defined.
My pipeline looked like this:

       <map:match pattern="*/*.aggregate">
         <map:aggregate  label="content" element="combine">
           <map:part src="cocoon:/{1}/{2}.banner" />
           <map:part src="cocoon:/{1}/{2}.menu" />
           <map:part src="cocoon:/{1}/{2}.document" />
         <map:transform src="xsl/combine-html.xsl" >
           <map:parameter name="QA" value="cocoon:/{1}/{2}.vivaQA"/>
         <map:transform type="xinclude" />
         <map:serialize type="html" />

What I get with  *.aggregate?cocoon-view=content is root element
<combine> wrapped around three copies of the same xml document
that those map:part sources should be styling differently.

My guess was that the cocoon-view=content was getting propagated
downward, because what I saw was the equivalent of instead calling:

	<map:part src="cocoon:/{1}/{2}.banner?cocoon-view=content" />

I then tried defining another label "aggregated-content" and using
that, but I get different wrong results. ( I'm not sure I can see
a pattern there yet to guess what it's actually doing. )

-- Steve Majewski

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message