[cas-dev] easier configuration in CAS 3.1.2-SNAPSHOT

[William G. Thompson, Jr.]

Not sure how I feel about loading *.xml files...seems like it could
lead to some unintended consequences.  Isn't it better, safer maybe,
to have these explicitly identified?  I'm curious how others feel
about this change.

Bill


On Jan 30, 2008 11:56 AM, Scott Battaglia <scott.battaglia at gmail.com> wrote:
> For the first time in a long time, I've actually had to do a deployment of
> CAS from scratch (shocking, yes, I know).  So its the first time I've had
> the pleasure of using the WAR overlay method of keeping track of your
> customizations.  [side note, if you're not using it I recommend it].
>
> However, when using it I noticed a few things that could be done more
> easily, so I've made a few modifications to the way we handle configuration
> files:
>
> Except for the files that we reference constantly or need to be in a
> particular spot (I'm looking at you, deployerConfigContext.xml and
> cas-servlet.xml), all other Spring XML configuration files are either
> located in WEB-INF/spring-configuration/ or WEB-INF/unused-configuration/
>
> The web.xml is set up to load deployerConfigContext.xml and
> WEB-INF/spring-configuration/*.xml.  You need to add a configuration file or
> enable one?  Just put it in that directory (preferably using the WAR overlay
> method).  Some of the things that are more frequently modified have been
> broken out into their own configuration files.
>
> This is going in for the CAS 3.1.2 release.  If you have any suggestions on
> breaking up the configuration files some more, etc. please let me know
> within the next day or two.
>
> Thanks
> -Scott
>
>  --
> -Scott Battaglia
> LinkedIn: http://www.linkedin.com/in/scottbattaglia
> _______________________________________________
> cas-dev mailing list
> cas-dev at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas-dev
>
>