I could see a few ways to do this. The first is the simplest, but depends on you having access to the script that starts WLS. I would add something like "-Dmy.property.dir=/usr/local/bea/properties" to the command line that starts up WLS. Then, within the class that needs to find the property files/resource bundles, do something like:
This allows you to have different directories and switch between them at startup time.
Another way would be through the WLS MBean system. This is somewhat more complex but would ultimately allow you create a custom console extension for GUI configuration and so on. The data would ultimately get stored in config.xml. The
docs for JMX detail what is required to implement this.
Lastly, you can access the
embedded LDAP server. However, that is a little dicey as you run the risk of really hosing something up in your security system. Additionally, as it is embedded I would not think that BEA would guarantee that it will exist in the future.
The second and third options are very likely to be overkill for what you are describing. As a general statement JNDI is mostly read-only externally and so putting random bits in there is more difficult than it should be. The LDAP server, while accessable, is a bit dangerous in my mind for what you need.
[ October 25, 2004: Message edited by: Scott Dunbar ]
