Description Yury Kats 2011-01-06 11:09:45 EST

This is a follow up to bug 308092. While 308092 resolved the problem of "view" scope not being handled, custom scopes are still reported as invalid.

JSF 2.0 supports custom bean scopes, that are EL expressions pointing to maps.

With the managed bean defined like:

<managed-bean>
	<managed-bean-name>bean1</managed-bean-name>
	<managed-bean-class>java.lang.String</managed-bean-class>
	<managed-bean-scope>#{customScope}</managed-bean-scope>
</managed-bean>

The validator reports the following warning:
Managed bean scope must be one of: request, session, application, none

Note: The warning does not mention view scope, although the validator now supports it (via bug 308092).