We use JNDI over here at Rutgers. Its served us well. We also make use of Spring's import option to place some of the Spring Configuration external to the web application.
Cheers, Scott On Mon, Mar 22, 2010 at 10:07 AM, Marvin Addison <[email protected]>wrote: > > I would like to remove this configuration data from the build > > process such that we could deploy the same cas.war file to all > environments > > with the need to edit, commit and then build. > > We use > http://static.springsource.org/spring/docs/3.0.x/api/org/springframework/beans/factory/config/PropertyPlaceholderConfigurer.html > as the cornerstone to our strategy to accomplish this. We have a > custom properties file that contains all environment and host-specific > configuration that we suck into the Spring context via > PropertyPlaceHolderConfigurer. I'm a big fan. Putting the data in > JNDI would be another good option. > > M > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
