> > Hi list members, > in my first year of develop with cocoon I used the 'cocoon.xconf', > sitemap global variables and a own configuration files (with > XMLFileModule) to provide parameter for my Components and XSL > stylesheets. > This configurations contains also customer specific data. > Unfortunately I got a lot of problems with this kind of inner > configuration (inside the webapplication) in the case of > updates. If I > need to update my application in the system of our customers > I lose all > configurations as a result of overwriting the existing files.
The XMLFileModule gets a <file src=""/>, right? Your src could be a location outside the application, right? You could get it from anywhere. You could right your own sourcefactory, making the file location anything, like: <file src="database://configuration.xml"/> Regards Ard > To solve this problem I start to configure my application over the > tomcat context configuration files. Inside of my cocoon based > application I use 'ServletContext.getInitParameter' to access the > parameters. I plan that this will be the only way to configure my > application. > Does I ignore some well known problems with this solution? > I'm also interested how do you handle this problem in your > application? > I wonder a little bit that I fall into that trap. But I can't > remember > that I have read about problems with inner configuration in > any cocoon > doc. Or does I generally misunderstand the cocoon > configuration options? > > Thanks > Eiko > > > --------------------------------------------------------------------- > 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]
