TransactionCachingInterceptor.java
TODO: This implementation does not take account of unshareable resources
TODO: This implementation does not take account of application security
where several connections with different security info are obtained.
TODO: This implementation does not take account of container managed security where,
within one transaction, a security domain boundary is crossed
and connections are obtained with two (or more) different subjects.
I suggest a state pattern, with the state set in a threadlocal upon entering a component,
will be a usable implementation.
The afterCompletion method will need to move to an interface, and that interface include the
security info to distinguish connections.
Created: Mon Sep 29 15:07:07 2003