> 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@lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/seam-dev
>
>
> _______________________________________________
> seam-dev mailing list
>
seam-dev@lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/seam-dev
>
>