<title>Re: [jsr-314-open] [2.0RevA-C071] none scoped beansand@PostConstruct</title><base href="https://webmail.consulting-fujitsu.com/exchange/Simon.Lessard/Sent%20Items/RE:%20[jsr-314-open]%20[2.0RevA-C071]%20none%20scoped%20beansand@PostConstruct-3.EML/"><div dir="ltr" id="idOWAReplyText4923">
<div dir="ltr"><font color="#000000" face="Arial" size="2">
</font><div dir="ltr" id="idOWAReplyText12207">
<div dir="ltr"><font color="#000000" face="Arial" size="2"><font color="#000000" face="Arial" size="2">Hi all,</font></font></div>
<div dir="ltr"><font color="#000000" face="Arial" size="2"><font face="Arial" size="2"></font> </font></div>
<div dir="ltr"><font color="#000000" face="Arial" size="2"><font face="Arial" size="2">I thought a bit more about this, and while
I still think @PostConstruct should be called for none scoped bean, I think we
should document @PreDestroy better as we won't have many way to call the
annotated method for none scoped bean. Of course, the managed bean engine could
be made very intelligent and know in what context the none scoped bean is
getting used. If injected into another bean, it could add the none scoped bean
in an hidden map in the same scope to detect destruction, but if the none scoped
bean is used directly, which is rare but possible, then I cannot think of any
way to enforce @PreDestroy.</font></font></div>
<div dir="ltr"><font color="#000000" face="Arial" size="2"><font face="Arial" size="2"></font> </font></div>
<div dir="ltr"><font color="#000000" face="Arial" size="2"><font face="Arial" size="2"></font> </font></div>
<div dir="ltr"><font color="#000000" face="Arial" size="2"><font face="Arial" size="2">Regards,</font></font></div>
<div dir="ltr"><font color="#000000" face="Arial" size="2"> </font></div>
<div dir="ltr"><font color="#000000" face="Arial" size="2">~ Simon</font><br></div>
</div></div></div>