DECAFFMEYER MATHIEU wrote:
Thank u !
Something still confuses me though ...
I have a factory (configfactory.xml) which contains the path to the
applciation configuration (ApplicationConfig.xml) :
<configuration>
<xml fileName="ApplicationConfig.xml"/>
</configuration>
So I don't think I can put a path in the classpath since the path is
specified in my factory configuration .
__________________________________
Matt
Commons Configuration searches for configuration files in several
locations including the class path. So if the configuration file cannot
be located relative to the configuration factory, the class path should
be searched, too.
HTH
Oliver
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Cimballi
Sent: Wednesday, March 21, 2007 8:06 PM
To: Jakarta Commons Users List
Subject: Re: [Configuration] Where to store the config ?
***** This message comes from the Internet Network *****
Hi,
Configuration files should be stored outside your archive, which means
outside the web application folders in order to be able to redeploy a
new version without overriding configuration files. So, you should put
your configuration files (the one which can change in the production
environment, not the one which never change) in a folder outside your
web application folders, and you add this folder to your classpath.
HTH,
Cimballi
On 3/21/07, DECAFFMEYER MATHIEU <[EMAIL PROTECTED]> wrote:
Hi,
I have a factory config in a java package "ress"
<configuration>
<xml fileName="ApplicationConfig.xml"/>
</configuration>
My Configuration file ApplicationConfig.xml is in the same package.
The problem is that I allow a user to modify the configuration via a
JSP
form, and save it, but then when I recompile the application the user
settings are lost !
I can see the changes in the "WEB-INF/classes/ress" directory,
but not in the JavaSources ...
So when I recompile the project, I lose the newest configuration.
How do I need to handle this ?
Thank u.
__________________________________
Matt
============================================
Internet communications are not secure and therefore Fortis Banque
Luxembourg S.A. does not accept legal responsibility for the contents
of
this message. The information contained in this e-mail is confidential
and
may be legally privileged. It is intended solely for the addressee. If
you
are not the intended recipient, any disclosure, copying, distribution
or any
action taken or omitted to be taken in reliance on it, is prohibited
and may
be unlawful. Nothing in the message is capable or intended to create
any
legally binding obligations on either party and it is not intended to
provide legal advice.
============================================
---------------------------------------------------------------------
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]
============================================
Internet communications are not secure and therefore Fortis Banque Luxembourg
S.A. does not accept legal responsibility for the contents of this message. The
information contained in this e-mail is confidential and may be legally
privileged. It is intended solely for the addressee. If you are not the
intended recipient, any disclosure, copying, distribution or any action taken
or omitted to be taken in reliance on it, is prohibited and may be unlawful.
Nothing in the message is capable or intended to create any legally binding
obligations on either party and it is not intended to provide legal advice.
============================================
---------------------------------------------------------------------
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]
