the classical example is the key for encryption.. where to put it ??
ejb-jar.xml is not a good idea unless all your developers can have
access to the password..
if I have Properties resources - perhaps also with encrypted features
- the admin can manage a few secret password and other installation
values without any relationship with the packaged artifacts.. just an
idea...... actuall a day-by-day missed feature..
On Tue, Mar 17, 2009 at 2:06 PM, Markus Karg <karg_at_quipsy.de> wrote:
> There is nothing like that because the Java EE way to store configuration params is to put them in the ejb-jar.xml file. The core idea of this originally was that all configuration is to be stored in a directory service (like ActiveDirectory, OpenLDAP etc) so administrators can modify the configuration easily with any LDAP- or JNDI-aware tool (or the native tools / GUIs of the directory vendor), while the value found in ejb-jar.xml will be just the defaults. Unfortunately it seems as if no server vendor supports this, at least officially. This some kind of strange, because in the Windows world for example, it is pretty usual to store anything in the AD...
>
>> as we have JDBC, JMS and JavaMail resources, why not to have a
>> Property resource ? a place where to write all configuration params
>> shared by applications ?
>
--
Please help to test this application:
http://fgaucho.dyndns.org:8080/cejug-classifieds-richfaces