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 &quot;none&quot;, &quot;request&quot;, or &quot;session&quot;, or is unspecified. In these cases, the value of managed-bean-scope is assumed to be &quot;application&quot;. Otherwise, any value of managed-bean-scope supported by the implementation is allowed. Once instantiated, the bean must be placed in the proper managed-bean-scope. This instantiation and storing of the instance must happen before any requests are serviced If eager is unspecified or false, the default &quot;lazy&quot; instantiation and scoped storage of the managed bean happens.<br>
</div><div><br></div><div>I&#39;m wondering about the scope of an eager managed bean. The preceeding paragraph indicates that it&#39;s okay to specify view or custom scopes, but not none, request, or session for an eager managed bean--is that correct, or was that paragraph written before view and custom scopes were conceived?</div>
<div><br></div><div>Thanks,</div><div><br></div><div><br></div><div>david</div>