Howdy,
There have been several approaches mentioned, and all of them seem
reasonable to some extent, so I'm not going to offer any more.  I just
wanted to disagree with this statement:

>I think the decision about where the locally stored data should go
should
>be done at build time.

While that may be true for your particular organization / application,
it may not be true in general.  This type of decision is typically done
as deploy time, but the deployer or installer of the application.  The
server administrator is the one who decides where these files go, not
the developer.  The developer provides a mechanism for the deployer to
configure this.  So you should have a configuration setting somewhere,
e.g. a <context-param> or a outputDirectory property in a configuration
file, and the application will write to the location specified by this
configuration setting.

Personally, I like using Ant tokens for this, so I tend to have
@outputDirectory@ tokens in configuration files, and fill them in at
deployment times, as I have different deployment targets
(local/development, staging/QA, userAcceptanceTesting, production) for
different needs.

Yoav Shapira
Millennium ChemInformatics




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to