[seam-dev] How to reduce UserTransaction lookups

[Jay Balunas]

https://jira.jboss.org/jira/browse/JBSEAM-3519

On Mon, Oct 6, 2008 at 9:52 AM, Gavin King <gavin at hibernate.org> wrote:

> Correct.
>
> On Fri, Oct 3, 2008 at 6:14 PM, Emmanuel Bernard <emmanuel at hibernate.org>
> wrote:
> > On  Oct 3, 2008, at 17:35, Jay Balunas wrote:
> >
> > What is the risk of caching this transaction instance in the event scope?
> >
> > Does seam components support something like the REQUIRES_NEW semantic of
> > SessionBeans? If so, then caching might not be appropriate.
> > Generally speaking if something use the TransactionManager to create new
> > transactions or suspend them, you are screwed.
> >
> >
> > How can we determine when/if the transaction is not valid anymore - do we
> > need to?
> >
> > Does the behavior need to be different for UTTransaction vs
> CMTTransaction?
> >
> > Thanks,
> > Jay
> >
> >
> > --
> > blog: http://in.relation.to/Bloggers/Jay
> > <Transaction.txt>_______________________________________________
> > seam-dev mailing list
> > seam-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/seam-dev
> >
> >
> > _______________________________________________
> > seam-dev mailing list
> > seam-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/seam-dev
> >
> >
>
>
>
> --
> Gavin King
> gavin.king at gmail.com
> http://in.relation.to/Bloggers/Gavin
> http://hibernate.org
> http://seamframework.org
>



-- 
blog: http://in.relation.to/Bloggers/Jay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20081006/d6c43e83/attachment.html