My thought about the document is: Okay! It's logical, consistent, reasonable.<br><br>I'll let you guys fight over the eventual location of @TrasnactionScoped<br><br><br>Regards<br>fm.<br><br><br><div class="gmail_quote">
On Wed, May 23, 2012 at 1:28 AM, Reza Rahman <span dir="ltr"><<a href="mailto:reza_rahman@lycos.com" target="_blank">reza_rahman@lycos.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-US"><div><p class="MsoNormal">CDI enthusiasts,<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Pete, I and Nigel (JMS 2 spec lead) have been discussing the issue of the transaction scope behind the scenes the past few weeks. Attached is what we came up with and feel it meets the various related use-cases the most effectively. The downside is that it is quite involved (conceptually) and might take a bit of patience to absorb. Please give it a read and let me know your thoughts.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Cheers,<u></u><u></u></p><p class="MsoNormal">Reza<u></u><u></u></p></div></div><br>_______________________________________________<br>
cdi-dev mailing list<br>
<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><a href="http://www.suntriprecords.com">http://www.suntriprecords.com</a><br><br>