On Jan 25, 2011, at 1:16 PM, Marvin Addison wrote:
If you're like most dev/pprd/prod environments, your configurations
only differ in hostnames and credentials. Why invest in build/deploy
complexity when you can simply factor out the
host/environment-specific data to something external to the build,
e.g. properties file on filesystem, and use a single build tree.
Marvin++
I was hoping for something simple and declarative - thanks! I'm
reading up on some other examples now.
It looks like I'd setup PropertyPlaceholderConfigurer to just point to
wherever the properties file should be - does that go in
deployerConfigContext?
Also, in your environment, where do the properties files live? Can
you just drop them beside the cas.war file, and will Tomcat play
nicely, or do you keep them outside of that entirely? I'm still not
100% exactly sure how paths evaluate in these circumstances, so it
would be nice to figure out a relative path scheme now and stick with
it, so I don't have to worry about where/how Tomcat is installed on a
particular target system.
Thanks again for the suggestion.
-Aaron
---------------------------------
Aaron Fuleki
Senior Web Architect
Denison University
740.587.5752
---------------------------------
--
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
