myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonardo Uribe (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Created] (MYFACES-3082) faces-config.xml metadata-complete="true" on jar files under META-INF are recognized, but not documented
Date Thu, 24 Mar 2011 22:04:05 GMT
faces-config.xml metadata-complete="true" on jar files under META-INF are recognized, but not
documented
--------------------------------------------------------------------------------------------------------

                 Key: MYFACES-3082
                 URL: https://issues.apache.org/jira/browse/MYFACES-3082
             Project: MyFaces Core
          Issue Type: Bug
          Components: JSR-314
    Affects Versions: 2.0.4
            Reporter: Leonardo Uribe
            Assignee: Leonardo Uribe


The spec javadoc section 11.5.1 says this:

"... If the <faces-config> element in the WEB-INF/faces-config.xml file
contains metadata-complete attribute whose value is "true", the implementation must not perform
annotation
scanning on any classes except for those classes provided by the implementation itself. Otherwise,
continue as
follows. ..."

On the Appendix A, the schema says this about 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. ..."

In Mojarra, it seems this value is also applicable for
faces-config.xml files under META-INF/ folder, making it
possible to prevent scan annotations on such cases.

The documentation must be corrected to reflect the implemented
behavior.

Alternate issue on spec created:

http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-952

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message