[seam-dev] How to reduce UserTransaction lookups

[Jay Balunas]

I was worried that there were issues with this approach related to what you
are saying.  I started to go down the "synchronizations" route and ran into
trouble.  That is not to say we could not still use them, but I think we
would have some hurdles to get over.

Does anyone have any comment on Emmanuel's point?  I am not familiar enough
to be sure of this answer.

If we check the transactions status and refresh if inactive would that be
enough, or is there another way to observe the transaction state instead of
lookups?

-Jay

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
>
>
>


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