I'm doing already that with the following problem: I'm making a webapp which works for 30 websites with personnalized and localized (not langage but content) contents.
Besides some parts are protected or partially protected. So here is my architecture (I used Forrest Pattern but not Forrest itself). Site.xml Sitemap.xmap -> go look in site.xml if the URL exists and then configure and call a pipeline -> call the pipeline and all the "usual stuff" (navigation, header, path, and so on). The advantage of this approach is: -> site.xml contains the semantic of the website and can event be edited trough XSL and Cocoon (I'm doing that) -> sitemap.xmap contains "data type" with skins: what is a list for instance or a "normal" page: I defined some generic data types; the presentation is included in these but a skin layer could be introduced. Are you interedted in that? Anyway, to answer your question, go look in linkmap.xmap. Nicolas PS If my employer agrees and somebody interested I'll put that code open-source since it's not high confidentiality code for him I'm doing the same Le Vendredi 09 Janvier 2004 00:40, Janne Kario a �crit : > I'm using forrest 0.5.1 sample webapp as a basis for my web application. > What I'm trying to accomplish is a dynamic site.xml. I have a generator > that generates the site.xml dynamically from the database. However I'm > unable to override default forrest behaviour. site.xml is always > generated from filesystem no matter what I do. So my question is: > > 1. What is the exact place in forrest xmap-files which defines how and > by which generator site.xml is generated? > > * Janne Kario > * Mermit Business Applications Ltd > > > --------------------------------------------------------------------- > 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]
