<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Oct 3, 2008, at 17:35, Jay Balunas wrote:</div><blockquote type="cite"><div dir="ltr"> <br>What is the risk of caching this transaction instance in the event scope? </div></blockquote><div><br></div><div>Does seam components support something like the REQUIRES_NEW semantic of SessionBeans? If so, then caching might not be appropriate.</div><div>Generally speaking if something use the TransactionManager to create new transactions or suspend them, you are screwed.</div><br><blockquote type="cite"><div dir="ltr"><br><br>How can we determine when/if the transaction is not valid anymore - do we need to? <br><br>Does the behavior need to be different for UTTransaction vs CMTTransaction?<br> <br>Thanks,<br>Jay<br><br clear="all"><br>-- <br>blog: <a href="http://in.relation.to/Bloggers/Jay" target="_blank">http://in.relation.to/Bloggers/Jay</a><br> </div> <span><Transaction.txt></span>_______________________________________________<br>seam-dev mailing list<br><a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/seam-dev">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br></blockquote></div><br></body></html>