<div class="gmail_quote">On Fri, Apr 10, 2009 at 2:25 PM, David Geary <span dir="ltr"><<a href="mailto:clarity.training@gmail.com">clarity.training@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The javadocs for the @ManagedBean annotation states:<div><br></div><div>If the value of the eager() attribute is true, the runtime must instantiate this class when the application starts. In this case, managed-bean-scope is ignored if its value is "none", "request", or "session", or is unspecified. In these cases, the value of managed-bean-scope is assumed to be "application".</div>
</blockquote><div><br>A question about this very statement was brought up at a JSF 2.0 talk presented yesterday at the NEJUG (by Jay Balunas). The question was whether a session scoped bean could be marked as eager. Seam implements this by listening for the HttpSession create event and instantiating any session scoped managed beans marked as eager. Thus, session+eager would be a valid combination.<br>
<br>-Dan<br><br></div></div>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</a><br><br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>
from my email. If you contact me, but don't hear back for more than a week,<br>it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters. Please don't hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>