Jon -- yes, making changes in the deployed app configuration files will take effect after an app server restart. I would agree with Marvin, though, that following the recommended overlay method to deploy your CAS configurations will save you trouble in the long run...
- Bill On Thu, Jan 20, 2011 at 1:11 PM, Jonathan Soons <[email protected]>wrote: > > > "Note that all configuration should happen in > cas-server-webapp/src/main/webapp/WEB-INF/deployerConfigContext.xml" > > > > There is no src directory in my cas webapp deployment (but that file > exists in my downloaded package). > > That apparent discrepancy can be explained by our recommendation that > configuration be maintained and applied using the Maven WAR Overlay process, > described at > https://wiki.jasig.org/display/CASUM/Best+Practice+-+Setting+Up+CAS+Locally+using+the+Maven2+WAR+Overlay+Method > . > Although you can unpack the WAR, edit the file, then repackage, managing > any non-trivial configuration via Maven WAR Overlay is well worth the > investment of time to learn it. > > M > > Thank you. I am very willing to learn Maven. I cannot tell from your advice > whether trivial changes like AD server IP address changes can be done in the > deployed deployerConfigContext.xml or if they will not take effect with a > restart. > > Jon Soons > -- > 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 > > -- Bill Markmann Counterpoint Consulting, Inc. (p) 571-338-2455 (f) 202-403-3425 (e) [email protected] (w) http://www.counterpointconsulting.com/ -- 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
