Package javax.faces.bean

These javadoc files constitute the “Faces Managed Bean Annotation Specification for Containers Conforming to Servlet 2.5 and Beyond”

See: Description

  • Annotation Types Summary 
    Annotation Type Description
    ApplicationScoped

    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.

    CustomScoped

    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.

    ManagedBean

    The presence of this annotation on a class automatically registers the class with the runtime as a managed bean class.

    ManagedProperty

    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.

    NoneScoped

    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.

    ReferencedBean

    The presence of this annotation on a class is equivalent to the referenced-bean element in the application configuration resources.

    RequestScoped

    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.

    SessionScoped

    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.

    ViewScoped

    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.

    javax.faces.bean (Java(TM) EE 7 Specification APIs) Home of API Java Contents Haut

Package javax.faces.bean Description

These javadoc files constitute the “Faces Managed Bean Annotation Specification for Containers Conforming to Servlet 2.5 and Beyond”

At the time of this writing, a forthcoming JCP effort is being planned to extract the specification for managed beans from JSF and place it into its own specification. To account for this effort and to avoid introducing classes into JSF 2.0 that would have to be deprecated when this effort is complete, implementations of JSF 2.0 are not required to implement the “Faces Managed Bean Annotation Specification for Containers Conforming to Servlet 2.5”. However, JSF implementations are strongly encouraged to implement this specification, as it provides significant improvements in ease of use.

The annotations must be processed as specified in section JSF.11.5.1.

Document created the 11/06/2005, last modified the 18/08/2025
Source of the printed document:https://www.gaudry.be/en/java-api-javaee-rf-javax/faces/bean/package-summary.html

The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.

References

  1. View the html document Language of the document:fr Manuel PHP : https://docs.oracle.com, javax.faces.bean (Java(TM) EE 7 Specification APIs)

These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author of this site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.