Am Mon, 12 Oct 2009 18:57:43 +0200
schrieb Jesse Long j...@unknown.za.net:
Thanks for your answers Tobias. Unfortunately we have a very real use
case for multiple instances on one host, with different data paths.
So, /etc/app.properties is not usable, but /etc/app-context path
derived
Hi,
In my webapp I need persistent storage. I am building my webapp as a
.war file, and copying it into $CATALINE_HOME/webapps/
Tomcat extracts $CATALINA_HOME/webapps/app.war to
$CATALINA_HOME/webapps/app/
The war file contains an empty directory /WEB-INF/data . During
operations, data files
Jesse Long wrote:
Question: id /WEB-INF/ in the extracted directory the correct place for
persistent data storage? If not, where is?
No, WEB-INF is not a correct place app generated files.
You can use any directory outside of context root.
My goal is to find a consistent way of creating
Mikolaj Rydzewski wrote:
Jesse Long wrote:
Question: id /WEB-INF/ in the extracted directory the correct place for
persistent data storage? If not, where is?
No, WEB-INF is not a correct place app generated files.
You can use any directory outside of context root.
My goal is to find a
Jesse Long wrote:
Thanks for your answers. I still like the concept of having the
container allocate persistent storage space. Can I configure tomcat to
not delete from the javax.servlet.context.tempdir directory?
'persistent' and 'temp' sounds like opposite.
--
Mikolaj Rydzewski m...@ceti.pl
Am Mon, 12 Oct 2009 13:01:44 +0200
schrieb Jesse Long j...@unknown.za.net:
In my webapp I need persistent storage. I am building my webapp as a
.war file, and copying it into $CATALINE_HOME/webapps/
Tomcat extracts $CATALINA_HOME/webapps/app.war to
$CATALINA_HOME/webapps/app/
The war
Tobias Crefeld wrote:
Am Mon, 12 Oct 2009 13:01:44 +0200
schrieb Jesse Long j...@unknown.za.net:
In my webapp I need persistent storage. I am building my webapp as a
.war file, and copying it into $CATALINE_HOME/webapps/
Tomcat extracts $CATALINA_HOME/webapps/app.war to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jesse,
On 10/12/2009 12:57 PM, Jesse Long wrote:
Unfortunately we have a very real use case for multiple instances on
one host, with different data paths. So, /etc/app.properties is not
usable, but /etc/app-context path derived data.properties
So you have multiple contexts on a host, each of which needs separate,
persistent storage?
If you don't want to keep track of a property files, you could write a bean
with a method that takes a HttpRequest as a argument, and returns a file
path based on the info in the request. You would have to
So you have multiple contexts on a host, each of which needs separate,
persistent storage?
If you don't want to keep track of a property files, you could write
a bean
with a method that takes a HttpRequest as a argument, and returns a
file
path based on the info in the request. You would
10 matches
Mail list logo
