When this annotation, along with ManagedBean is found on a class, the runtime must act as if a
<managed-bean-scope>application<managed-bean-scope>
element was declared for the corresponding managed bean.
When this annotation, along with ManagedBean is found on a class, the runtime must act as if a
<managed-bean-scope>VALUE<managed-bean-scope>
element was declared for the corresponding managed bean, where VALUE is the
value of the CustomScoped.value() attribute, which must be an EL expression that
evaluates to a Map.
These javadoc files constitute the “Faces Managed Bean Annotation Specification for Containers Conforming to Servlet 2.5 and Beyond”
The presence of this annotation on a class automatically registers the class with the runtime as a managed bean class.
The presence of this annotation on a field of a
class annotated with ManagedBean instructs the system to inject a
value into this property as described in section JSF.5.3 of the spec prose
document in the <managed-property> subsection.
When this annotation, along with ManagedBean is found on a class, the runtime must act as if a
<managed-bean-scope>none<managed-bean-scope> element
was declared for the corresponding managed bean.
The presence of this annotation on a class is equivalent to the referenced-bean element in the application configuration resources.
When this annotation, along with ManagedBean is found on a class, the runtime must act as if a
<managed-bean-scope>request<managed-bean-scope>
element was declared for the corresponding managed bean.
When this annotation, along with ManagedBean is found on a class, the runtime must act as if a
<managed-bean-scope>session<managed-bean-scope>
element was declared for the corresponding managed bean.
When this annotation, along with
ManagedBean is found on a class, the runtime must act as if a
<managed-bean-scope>view<managed-bean-scope> element
was declared for the corresponding managed bean.
Copyright © 2002-2009 Sun Microsystems, Inc. All Rights Reserved.