Like many have said, actions work. Also,
I usually do the processing in the XSL, so when dealing with "what request
gets what what XSL", it's possible to have ALL
requests go to the SAME xsl. Of course it depends on
your demands. Liam Morley -----Original Message----- As far as I've understood C2, there
is now a quite static sitemap which tells what request gets what XSL. This
is too static for my needs, I would like to do a bunch of
calculations and then decide on what XSL to use. Is there any way I can accomplish
this with C2? I have my own producer today with
Cocoon 1 which creates Documents from data in my database, and these are
then assigned an XSL depending on a bunch of parameters (from the database and
user environment as well), ie I add PI:s to the Document DOM dynamically. So - is it possible to use
"classic" cocoon1.8 processing instructions with cocoon2, instead of
specifying processing stages in the sitemap? If not, can I do my own implement of
the Sitemap interfaces and get C2 to use those instead? My classes would
act just like a sitemap (as the interfaces are the same) but get it's daata
from database instead of a XML file in the filesystem. |
- how to implement a dynamic sitemap? Christer Lindh
- Re: how to implement a dynamic sitemap? Mario Muja
- Re: how to implement a dynamic sitemap? Martin Man
- Re: how to implement a dynamic sitemap? Piroumian, Konstantin
- Re: how to implement a dynamic sitemap? Sergio Carvalho
- Liam Morley