Hi Marc, we provide a cocoon-environment which does not include the content. All content is retrieved from a different location in the filesystem.
Our war is to be used in different environments, and currently we use the convention that a "root"-sitemap is located/linked as <webapp-dir>/../sitemap.xmap, so cocoon.xconf currently contains <sitemap file="../sitemap.xmap"/> That's quite ugly, so I would like to let the admins configure this path via externalized properties. I do not want to have a fixed location given within the WAR anymore. Using servlet context params together with our own configuration library would allow us to do that (as we can replace the context param with our own value). But it seems to me there's no easy way to do this...? Thanks! Sebastian -----Ursprüngliche Nachricht----- Von: Mark Lundquist [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 11. Januar 2007 18:01 An: users@cocoon.apache.org Betreff: Re: Externalize sitemap.xmap location property On Jan 11, 2007, at 8:51 AM, Eichner, Sebastian wrote: > I have to modify the configuration of an Cocoon-based web application > (Cocoon 2.1.9, Tomcat 5.5.17, JDK5), and I am trying to externalize > some > configuration parameters. > > I would like to configure the location of the base sitemap.xmap via > servlet params or servlet context attributes. Hi Sebastian, Just out of curiosity, why do you want to do that? -ml- --------------------------------------------------------------------- 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]
