fixed encoding

expose an onSuccessfulValidation method to do things (if you want)

upgrade inspektr

Leverage JPA2 pessimistic locking to avoid deadlocks caused by lock upgrade
(escalation) cases like the following:

 1. Tx1 obtains SHARE lock on TGT row P prior to creation of child ST C1
 2. Tx2 obtains SHARE lock on TGT row P prior to creation of child ST C2
 3. Tx2 attempts to upgrade SHARE lock to EXCLUSIVE in order to update P
 4. Tx1 attempts to upgrade SHARE lock to EXCLUSIVE in order to update P

Since Tx2 and Tx1 depend on each other in a way that will never resolve
naturally, the database reports a deadlock.

By querying for TGTs with lock type PESSIMISTIC, an exclusive lock is
obtained for P _prior_ to step 1 and Tx2 blocks on Tx1 at step 2 in a way
that will resolve naturally.

switch to using ElementCollection which was added with JPA 2.0

Add lock expiration test.

Add JpaLockingStrategy Lock entity to persistence context.

Add @NotNull annotation to facilitate identification of component wiring
problems that should manifest at deployment time instead of runtime.

Deprecate JdbcLockingStrategy.

JpaLockingStrategy feature completed with verifying test cases.
Concurrent tests only execute upon request when cas.jpa.concurrent system
property is set to true and do _not_ work against HSQL due to lack of
complete support for pessimistic locking (at least when using Hibernate).

Initial support for JPA 2.0 locking strategy

set precedence pretty high

added timings around authentication handler calls

changed english version to username

applied patch for IE6 stylesheet

support for alternative remember me attribute names

Chinese translation

added new ES translation

removed extra code that came out of wgthom/battags code review.

added debug logging

added protected getter

updated all configs to use Spring 3 namespaces

applied patch to refactor UI

Log warning when non-printable characters are detected in redirect URL.  Add documentation to sanitizeUrl method.