Type: New Feature
Resolution: Won't Fix
Affects Version/s: None
Fix Version/s: None
Last commented by a User:true
When creating beans such as a JNDITemplate it is often desireable to have a container supply the provider URL and other configuration options via Environment entries. I find it is generally not a great idea swap applicationContext files using a build script because it adds another layer of complexitity to the build process. Therefore I prefer having different deployment descriptors on different test/production servers with different Environment settings. The real benefit comes with the ability for certain containers to update these Environment entries during runtime such as if a provider URL becomes inaccessible. I propose a JNDI Property Placehold Configurer which will do java:comp/env/ lookups to fill in the appropriate property values.
Example usage would be as follows:
<bean id="jndiTemplate" class="org.springframework.jndi.JndiTemplate">
I will attach a working version I have been using for several months now.