Howdy,
OK, so my question - if I want to do this, where in the file system
should
I stick the xml file so it doesn't get overwritten if the war is
redeployed? A user's home directory? That will force the user to mess
with the configuration.
I'm a out of my league on this, so I'd appreciate
On Thu, 18 Jul 2002, Will Hartung wrote:
This all came out of the fact that it seems essentially impossible to create
a webapp according to the 2.3 spec that uses file based storage and have it
be usable out of the box with zero basic configuration to start up. For
example, I don't think
From: Craig R. McClanahan [EMAIL PROTECTED]
Sent: Wednesday, July 17, 2002 11:19 PM
Subject: Re: io path information in servlets
On Wed, 17 Jul 2002, Will Hartung wrote:
It has CONVENTIONALLY been done this way, as it's a fairly obvious
optimization to handle a web app (who wants
I have a webapp that stores some data in an xml file. (I am using jdom to
read and write the xml files.)
Right now I am using a construct like:
String prefix = sc.getRealPath(/) + /WEB-INF/dirName/;
to get the path. I then concatonate that with the file name and it works
fine.
However, in
From: Paul Phillips [EMAIL PROTECTED]
Sent: Wednesday, July 17, 2002 5:20 PM
Subject: io path information in servlets
I have a webapp that stores some data in an xml file. (I am using jdom to
read and write the xml files.)
Right now I am using a construct like:
String prefix
With Tomcat, normally when you deploy a .war file, it gets expanded and the
context is run out of the directory created upon expansion, not the .war
file itself. For intance if you put a myapp.war file in
TOMCAT_HOME/webapps (and haven't defined the context in server.xml because,
if defined,
On Wed, 17 Jul 2002, Paul Phillips wrote:
Date: Wed, 17 Jul 2002 19:20:00 -0500
From: Paul Phillips [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: io path information in servlets
I have a webapp that stores some data
On Wed, 17 Jul 2002, Will Hartung wrote:
It has CONVENTIONALLY been done this way, as it's a fairly obvious
optimization to handle a web app (who wants to constantly grind through a
jar file for crying out loud). However, what is convention, and what is
specification are two completely
