-
Feature Request
-
Resolution: Done
-
Major
-
3.2.0.CR1, 3.3.0.M1
-
Documentation (Ref Guide, User Guide, etc.)
-
-
Documented as Feature Request
According faces-config 2.0 scheme:
"Attribute : metadata-complete
The metadata-complete attribute defines whether this JavaServer Faces application is complete, or
whether the class files available to this module and packaged with this application should be examined
for annotations that specify configuration information. This attribute is only inspected on the application
configuration resource file located at "WEB-INF/faces-config.xml". The presence of this attribute on any
application configuration resource other than the one located at "WEB-INF/faces-config.xml", including any
files named using the javax.faces.CONFIG_FILES attribute, must be ignored. If metadata-complete is set
to "true", the JavaServer Faces runtime must ignore any annotations that specify configuration
information, which might be present in the class files of the application. If metadata-complete is not
specified or is set to "false", the JavaServer Faces runtime must examine the class files of the application
for annotations, as specified by the specification. If "WEB-INF/faces-config.xml" is not present, the
JavaServer Faces runtime will assume metadata-complete to be "false". The value of this attribute will
have no impact on runtime annotations such as @ResourceDependency or @ListenerFor.
Data Type : boolean
Enumerated Values :
- true
- false"
- is blocked by
-
JBIDE-5045 JSF 2: Support annotated manage beans in EL
- Closed