For better understanding:
<map:pipelines>
<!-- This is the external matcher area , this are the links the customer should be able to create via GUI-->
<map:pipeline internal-only="false">
<map:match patter="foo.html"> <map:redirect-to uri="cocoon:template1_storyID10" />
</map:match>
</map:pipeline>
<!-- This is the internal match area, this are the templates generated by our company -->
<map:pipeline internal-only="true">
<map:match patter="template1_storyID*"> <map:generate .... />
<map:act .... />
<map:transform .... />
<map:serialize ..... />
</map:match>
</map:pipeline>
</map:pipelines>
My idea was to put the external pipelines in an seperate sitemap.xmap file. This file should be created by my application. As far as i know, cocoon has a treeProcessort which validates all the XML given to him. Short ... i want to use the Validator of Cocoon to create, read and validate the XML I produce while creating it.
Additional I asked if someone has experience in creating the Sitemap.xmap dyamically, because I do not know if i should store the Data (like indentlevel of the nodes, sort order of nodes) in a XML FIle an process an XSLT Transformation or if I should store the whole shit in a database.
Andreas
Andreas Hartmann wrote:
Andreas Schmid wrote:
I am currently developing a CMS based on Cocoon 2.1.4
The thing is changing contents is no problem.. but our users also want to add or delete pages on their webpage.
So i thought it would be great to create an sub sitemap which holds the pages for the webpage.
You mean you want to define single pages in a Cocoon sitemap? Could you explain why this approach is reasonable in your usecase?
-- Andreas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
