<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=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@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;}
/* 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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>I’m just now trying to upgrade to Weld 3.0.0 Alpha 16 (from Alpha10) and I’m finding a significant change in the way the proxies are generated. This seems to be the result of this ticket: <a href="https://issues.jboss.org/browse/WELD-2092">https://issues.jboss.org/browse/WELD-2092</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In short, it seems that decorated beans that have private methods that @Observe events are invoked on the wrong instance. They get invoked on an uninitialized proxy instance instead of the properly initialized bean instance.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’m still working to put together a small project that reproduces this problem, but that may take me until tomorrow. My actual project is too large.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Has anyone else reported this type of problem? Where an @ApplicationScope bean with a decorator and a private method with arguments that @Observe some event are invoked on the wrong object instance? In this case, I’m enabling RunnableDecorator, and one of my AppScope beans implements Runnable, and it has a private observer method.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I did my best to search for any other posts on this problem, but didn’t find anything relevant (other than the JIRA ticket I referenced above).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks,<o:p></o:p></p><p class=MsoNormal>Larry.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>