Where to store modified properties/config files for web apps?

[unomystEz]

Hi all,

I have a war file that includes default config files that should be
overridden by the user. However when a new war file is deployed it
will overwrite the files. Where would be a good place to store custom
config files used by servlets and/or webapps?

Thanks in advance

 

[Manish Pandit]

Hi,

Not sure if I got your question correctly, but are the properties
overridable by the user? If so, then you should be storing the
properties/configuration in the database against every user.

-cheers,
Manish

 

[Thomas Hawtin]

I have a war file that includes default config files that should be
overridden by the user. However when a new war file is deployed it
will overwrite the files. Where would be a good place to store custom
config files used by servlets and/or webapps?

Are you looking for JNDI, perhaps?

Tom Hawtin

 

[unomystEz]

Are you looking for JNDI, perhaps?

Tom Hawtin

Hi sorry for the delay. I have a war file that needs to be customized
not on a per-user basis but on a per-deployed basis - ie, the war file
needs to know the address of a smtp server, the addresses to other web
services, maybe it also opens up a dedicated TCP server socket and that
has to be configured. I don't like the idea of using a database to
store custom settings as you never know what may happen to the
database. Ini files or properties file seems to be much more simple.
JNDI I think is mostly used for configuring services on a
application-container scale.

This particular war file can also be deployed multiple times in a
single container and would need to be configured differently. So for
server apps that need custom config files, im not sure where or how you
would store the custom configs.

Thanks