Hi,
that mechanism with the property file works. Thumbsup :) For a strange
reason I have the porty file in my jar file and in the expected folder,
although I have deleted it from my block.
My second question is still, how I can access some folders outside of my
jar by the pointed out
<map:pipeline id="non-war-resource">
<map:match pattern="resource/nonwar/**">
<map:read src="{path.to.non.war.resources}/{1}" />
I got a little bit confused about the protocol. Whats context://,
resource://, ... do I need this?
Barbara Slupik schrieb:
I use properties to define my database connection. I my development
environment I add my properties into block rcl.properties and I can
test blocks individually with jetty. rcl.properties file is not
included in block jar file. In my application I created
cocoon/properties/application.properties file in
src/main/webapp/WEB-INF. This file contains all properties from all
application blocks. When my application runs in tomcat I have
cocoon/properties/application.properties in my WEB-INF and I can edit
it without changing jar files.
Barbara
On 3 Jul, 2008, at 1:04 pm, Johannes Hoechstaedter wrote:
How can I access the web-inf folder?
Robin Rigby schrieb:
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]
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
