We also successfully use the spring PropertyPlaceholderConfigurer for this purpose. If you are using spring in your application arlready, this is probably the easiest path.
David Ohsie Software Architect EMC Corporation From: Andrew Chandler [mailto:[email protected]] Sent: Wednesday, March 13, 2013 9:51 AM To: [email protected] Subject: Re: [cas-user] cas client properties On a side note we managed to get it working with the spring property configurer bean. I'll post more detail tonight but we are doing substitution of server names on the client for Cass On Mar 13, 2013 8:21 AM, "Marvin Addison" <[email protected]> wrote: > How are other people dealing with this? I don't want to build a new war for > each environment that I have to push to if that is possible. I looked at the > JNDI method: > https://wiki.jasig.org/display/CASC/Configuring+the+JA-SIG+CAS+Client+for+Ja va+using+JNDI > and if I am not mistaken this approach to using the context was abandoned > with Tomcat 7.0, but I could be wrong on that. Unless you're leveraging a centralized JNDI store (e.g. LDAP directory with a config branch), then I think there's little to be gained from JNDI-based configuration. I would recommend you consider putting host or environment-based configuration in a context.xml file, which has been supported for a long time and is still available for Tomcat 7.x. The following section provides a good start: http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Context_Paramete rs 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
smime.p7s
Description: S/MIME cryptographic signature
