[seam-dev] persistence module page drafted

[Lincoln Baxter, III]

Ok, yeah +1, I'm completely sold now.

On Wed, Apr 14, 2010 at 10:27 PM, Clint Popetz <cpopetz at gmail.com> wrote:

> On Wed, Apr 14, 2010 at 9:08 PM, Dan Allen <dan.j.allen at 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
>



-- 
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20100414/556c2fce/attachment-0001.html