users@glassfish.java.net

Re: Surprising JPA (Toplink) Behaviour (glassfish v1 UR1)

From: Marina Vatkina <Marina.Vatkina_at_Sun.COM>
Date: Fri, 16 Mar 2007 16:12:01 -0700

The new interface was added for the cases when UserTransaction is not available.
And (IMHO) to simplify a complicated enough combination of configurations, it
was chosen as the only one for EMs obtained via Persistence.createEMF.

You can always replace an injection with JNDI lookup if the location is not that
of a component that supports the injection.

HTH,
-marina

glassfish_at_javadesktop.org wrote:
> Wow, thank you for pointing that out. I never would have discovered that on my own. I'm now wondering the same thing that this blogger asked over a year ago...
>
> http://trycatchfinally.blogspot.com/2006/01/why-entitytransaction.html
>
> ...Anyway, this is not at all an appealing prospect -- to have to go through all of these JSF managed beans and rewrite all of the persistence methods with uncertain outcome.
>
> At this point, it would be much nicer if I could get container-managed EMF injection to place nice.
> [Message sent by forum member 'pohl' (pohl)]
>
> http://forums.java.net/jive/thread.jspa?messageID=208527
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>