Re: [seam-dev] persistence module page drafted
On Wed, Apr 14, 2010 at 9:08 PM, Dan Allen <dan.j.allen(a)gmail.com> wrote:
Right. I'm imagining that we can inject the native
UserTransaction interface
or our extended interface, but either way you are getting the same bean
instance. Internally we stick the our extended interface to keep the code
readable, the user gets a choice.
It's not just about wrapping these few status methods and adding the enlist
method. It's about taring the transaction API to a single interface.
Basically, UserTransaction is the interface, the implementation could be
non-JTA.
This is also important in mock environments. We use JTA in J2EE
containers, but not in unit test land (or in development container
environments like Jetty), and Seam's transaction API allows us to
easily stub out the same API in the latter case.
-Clint