<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>It’s a good point and one that I’ve brought up myself more than once. As you pointed out though, it’s a bit too late already and there are practical reasons (noted in my previous email) why the current state actually makes some sense.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Lincoln Baxter [mailto:lbaxter@redhat.com] <br><b>Sent:</b> Tuesday, May 22, 2012 8:09 PM<br><b>To:</b> Reza Rahman<br><b>Cc:</b> cdi-dev@lists.jboss.org<br><b>Subject:</b> Re: [cdi-dev] Transaction Scope for CDI<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='color:black'>The only reason why I potentially object is because we already have several scope annotations specified in CDI itself, when these annotations really do not belong there in the first place.<br><br>There's no good reason I can think of why CDI should know what the "@RequestScope" or "@ConversationScope" is. AFAIK this was done as a convenience instead of doing work in the related specs, or as a separate deliverable of this spec.<br><br>But I won't stand in the way. We already have precedent, it's already messy, and we can't fix it now ;)<br><br>~Lincoln<o:p></o:p></span></p><div class=MsoNormal align=center style='text-align:center'><span style='color:black'><hr size=3 width="100%" align=center id=zwchr></span></div><div><p class=MsoNormal><b><span style='font-family:"Helvetica","sans-serif";color:black'>From: </span></b><span style='font-family:"Helvetica","sans-serif";color:black'>"Reza Rahman" <<a href="mailto:reza_rahman@lycos.com">reza_rahman@lycos.com</a>><br><b>To: </b><a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br><b>Sent: </b>Tuesday, May 22, 2012 7:28:13 PM<br><b>Subject: </b>[cdi-dev] Transaction Scope for CDI<br><br><br></span><span style='font-size:12.0pt;font-family:"Helvetica","sans-serif";color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>CDI enthusiasts,<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>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.<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Cheers,<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Reza<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Helvetica","sans-serif";color:black'><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">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:black'><o:p> </o:p></span></p></div></div></div></body></html>