Igor,
I think you can do what you want with a map:aggregrate, but not in
every pipeline. Try somehting like this:
<map:match pattern="**">
<map:aggregate element="site">
<map:part src="cocoon:/part/{1}"/>
<map:part src="cocoon:/menu.xml"/>
</map:aggregate>
<map:transform src="something.xsl"/>
<map:serialize/>
</map:match>
This will match every url and then aggregate it with your other
matchers. Then just have all your other matchers start with "part/".
Of course, I've never used views, so I don't really know if it's easier
or even possible with them.
Justin
On Tuesday, August 20, 2002, at 07:10 AM, Per Kreipke wrote:
>> Hi!
>>
>> I'm about to start using views. I'm trying to do something that I'm not
>> sure can be done.
>>
>> Can I use <map:aggregate> in views?
>>
>> What for? Well, this way I would be able to add my side-menu XML
>> elements after the content generation, but before the final
>> transformation. I'm looking for a way to add content to *all* of my
>> pages before their final transformation to HTML, without having to use
>> <map:agregate> in every pipeline.
---------------------------------------------------------------------
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]>
