Starting with 3.2, CAS supports adding arbitrary Spring configuration information to the WEB-INF/spring-configuration directly and having it automatically detected by CAS without having to modify the web.xml.

In addition, if you are using the Maven2 WAR Overlay method of deploying CAS, you can override any of the specific Spring configuration files that already exist in the spring-configuration directory by replicating the structure in your overlay.

For example, if you wanted to deploy another TicketRegistry your overlay would just have its own WEB-INF/spring-configuration/ticketRegistry.xml that defined the appropriate information.

For backwards compatibility purposes (and for documentation purposes) the deployerConfigContext.xml continues to exist in its current location.