Problem: Some clients such as Spring Security configure the filter via Spring configuration, meaning the handler's init method is not called vai the Filter#init method. Solution: For now, have an atomic boolean to determine if init was called or not and call it if necessary as part of the flow. |
||
|---|---|---|
| cas-client-core | ||
| cas-client-integration-atlassian | ||
| cas-client-integration-jboss | ||
| cas-client-integration-tomcat-common | ||
| cas-client-integration-tomcat-v6 | ||
| cas-client-integration-tomcat-v7 | ||
| cas-client-support-distributed-ehcache | ||
| cas-client-support-distributed-memcached | ||
| src/licensing | ||
| .gitignore | ||
| LICENSE | ||
| NOTICE | ||
| README.txt | ||
| assembly.xml | ||
| pom.xml | ||
README.txt
BUILDING THE CAS CLIENT FOR JAVA Please note that to be deployed in Maven Central, we mark a number of JARs as provided (related to JBoss and Memcache Clients). In order to build the clients, you must enable the commented out repositories in the appropriate pom.xml files in the modules (cas-client-integration-jboss and cas-client-support-distributed-memcached) or follow the instructions on how to install the file manually.