[jboss-jira] [JBoss JIRA] Commented: (JBAS-8098) Annotation scanning not working for JSF

[Remy Maucherat (JIRA)]

    [ https://jira.jboss.org/browse/JBAS-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12535715#action_12535715 ] 

Remy Maucherat commented on JBAS-8098:
--------------------------------------

You could add the functionality to your scanner plugin, but I'm not sure it is the most convenient thing to do. Since you apparently have to do processing per classpath element, you could maybe take advantage of the ResourcesIndex that is in the web plugin.

> Annotation scanning not working for JSF
> ---------------------------------------
>
>                 Key: JBAS-8098
>                 URL: https://jira.jboss.org/browse/JBAS-8098
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JSF
>    Affects Versions: 6.0.0.M4
>            Reporter: Stan Silvert
>            Assignee: Ales Justin
>            Priority: Blocker
>             Fix For: 6.0.0.M4
>
>         Attachments: annotest-webinflib.jar, jbosstest-jsf.war
>
>
> The JBossAnnotationProvider is now integrated so that JSF can take advantage of the new annotation scanning.  However, it doesn't find any annotations.  I've verified that it is called, but it seems to have no effect.
> For reference, here are the requirements from the JSF spec.  I think the first two requirements are taken care of by the JSF impl, but we need to confirm that.  I'm attaching WARs to test the second two.
> 11.5.1 Requirements for scanning of classes for annotations
> ■ 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.
> ■ If the runtime discovers a conflict between an entry in the Application Configuration Resources and an annotation, the
> entry in the Application Configuration Resources takes precedence.
> ■ All classes in WEB-INF/classes must be scanned.
> ■ For every jar in the application's WEB-INF/lib directory, if the jar contains a "META-INF/faces-config.xml"
> file or a file that matches the regular expression ".*\.faces-config.xml" (even an empty one), all classes in
> that jar must be scanned.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira