While the JA-SIG Java client is relatively new to the pantheon of CAS client libraries, the Yale Java CAS client is older and its understanding and documentation more pervasive. Therefore, it may be useful to understand the new JA-SIG Java client in terms of the older Yale CAS client.

How is the client configured?

The Yale CAS Client is configured directly in web.xml. This is intended to provide simplicity and central configuration.
The JA-SIG CAS client is factored in terms of filters that delegate to Spring-configured beans. This is intended to provide more powerful pluggability and configurability. As of release 3.1, the JA-SIG Java CAS client can also be configured as a set of filters in web.xml in a way that is similar to the Yale CAS client.

Single Sign-Out support

Only the JA-SIG Java CAS client has support for the CAS Single Sign-Out. That support may be enabled in the client by configuring it in web.xml as a JEE filter. Please see the Configuring Single Sign Out section for details.

Where does the source code of the client live?

The Yale CAS client distributions include source code, but the project never quite got it together to host the source code publicly or to make it possible for anyone outside of Yale to collaborate directly on the project. In hindsight, this probably limited the evolution of this distribution and was a factor in leading to a revolutionarily new Java CAS client outside the context of this client, out in JA-SIG public CVS. That client is the JA-SIG Java CAS client, which lives in and is collaborated upon in JA-SIG CVS.