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

[Smith, Matt]

> 1. whether the split of the files currently in the configuration
> directory in Subversion is sufficient (of if we should be more
> fine-grained)

The granularity is appropriate -- much more granular, and you'll have
one file for each attribute/value pair.  Your current breakdown seems to
successfully reflects one file per common point of extension.

> 2. whether we should split up the deployerConfigContext.xml also.

It may be useful to split the wiring up here, but not necessary.  For
example, I only modify the "authenticationHandlers" property of
AuthenticationManager, and the "attributeRepository" bean is rather
unrelated, so these could be separated.  But, #1 by itself is a great
step forward.

> If we do #2, then we'll definitely need to do a 3.2 release instead of
> 3.1.2.  Its still up in the air right now whether these configuration
> changes and addition of the Stats/auditing tool are sufficient for a
> 3.2 release.  Opinions?

Nope -- they're just numbers to me. :)

-Matt




-- 
Matt Smith
matt.smith at uconn.edu
University Information Technology Services (UITS)
University of Connecticut
PGP Key ID: 0xE9C5244E
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://tp.its.yale.edu/pipermail/cas-dev/attachments/20080131/27346217/attachment.bin