|
Hi, What is actually reading the forrest.properties data? I am trying to understand if there is more extendability for the parameters, for example: forrest.validate.skinconf.includes=${skinconf-file} i.e. what in the Forrest engine is parsing and using this or is it Cocoon? Taking the question a step further, is it possible then to define new settings in forrest.properties? example: project.data=""> and if so how might this be referenced in sitemap? For instance, say you have <map:part src=""/> which has a path project:content/data as noted above, what is the parallell between the naming convention in forrest.properties and the sitemap entries of: sitemap: {project:content.data} properties: {project:content.data} and thus might this work <map:part src=""-1">{project:data}/scaryalgorithms.xml"/> helps a bit in reusability of setting up new sites with Forrest. Thankyou, Helena |
- the forrest.properties-sitemap connection Helena Edelson
- Re: the forrest.properties-sitemap connection Ross Gardler
- Re: the forrest.properties-sitemap connection Helena Edelson
