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". 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 "lazy" instantiation and scoped storage of the managed bean happens. I'm wondering about the scope of an eager managed bean. The preceeding paragraph indicates that it'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? Thanks, david