Setting Strategies

I wanted to post this out in the general forum to see how other people are handling this issue.

I have a webapplication. It makes an ip connection to a mainframe system (amoung other things) and the address for the mainframe is stored currently in a properties file. I would like to change my application so that no one who is deploying my app has to edit a file properties file directly....

If you have an application that has settings that change with each deployment.. please post how you handle this ... would love to learn what others are doing.

[570 byte] By [jmguillemette] at [2008-1-5]
# 1

Store that information into environment variable. You need to put an env-entry into you'r web.xml and users will be able to modify it via app. server specific tools (server console).

<!--

The env-entry element contains the declaration of a web application's

environment entry. The declaration consists of an optional

description, the name of the environment entry, and an optional

value. If a value is not specified, one must be supplied

during deployment.

-->

<!ELEMENT env-entry (description?, env-entry-name, env-entry-value?,

env-entry-type)>

best regards,

Maris Orbidans

Maris_Orbidans at 2007-7-7 > top of java,Enterprise & Remote Computing,AVK Portability...
# 2
would love to.. but ...a) want to avoid having the "deploy team" editing files directly.b) websphere does not support updating env-entry (ies) via the deployment console... (a feature every servlet server should have IMO)
jmguillemette at 2007-7-7 > top of java,Enterprise & Remote Computing,AVK Portability...