Try a third set of resources, that are not packaged in the war file, in addition to internal and external. The path to them can be configured as I described. The sitemap does something like:
<map:pipeline id="non-war-resource"> <map:match pattern="resource/nonwar/**"> <map:read src="{path.to.non.war.resources}/{1}" /> etc Robin -----Original Message----- From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED] Sent: 03 July 2008 12:45 To: users@cocoon.apache.org Subject: Re: How to access configuration files and properties after packaging Robin Rigby schrieb: > Here is one way that seems to work. Make a separate set of configuration > for development and the default for production. > > \src\main\resources\META-INF\cocoon\properties\config.properties > \src\main\resources\META-INF\cocoon\dev\properties\config.properties > > and run during development with > > mvn -Dorg.apache.cocoon.mode=dev jetty:run > > It is documented somewhere _if_ you can find it. I suppose the same would > work in Tomcat, ect Thank you for your answer Robin, but your configuration files are still packaged in in the jar file, or? Thats what I want to pretend. --------------------------------------------------------------------- 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]