On Fri, Apr 10, 2009 at 2:25 PM, David Geary
<clarity.training@gmail.com> wrote:
The javadocs for the @ManagedBean annotation states:
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".
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.
-Dan
--