[
https://issues.apache.org/jira/browse/MYFACES-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896990#action_12896990
]
Stan Silvert commented on MYFACES-2860:
---------------------------------------
The point of this interface is that we don't want MyFaces to do any scanning at
all. MyFaces should contain a default scanner in case the container doesn't
provide one. But if I implement this interfaces I expect that MyFaces will not
scan at all. It will only load the classes where I found JSF annotations. So
MyFaces doesn't worry about metadata-complete. The scanner implementation does
that.
Since MyFaces isn't doing the scanning, it also doesn't have to worry about
file type vs. jar file. JBoss has its own protocols for its virtual file
system. So you'd have more trouble navigating that anyway.
I'd rather see something like:
public Collection<Class<?>> getAnnotatedClasses(Class<? extends Annotation>
annotation, ExternalContext extCtx);
I see your point about ExternalContext and portlets. But like you, I'm not
sure if it's really needed. We need to think about that one some more.
> Provide AnnotationScanner interface
> -----------------------------------
>
> Key: MYFACES-2860
> URL: https://issues.apache.org/jira/browse/MYFACES-2860
> Project: MyFaces Core
> Issue Type: Improvement
> Components: JSR-314
> Affects Versions: 2.0.1
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
> Attachments: jboss-myfaces.zip, Myfaces-2.0-jsf.deployer.zip,
> MYFACES-2860-1.patch
>
>
> Looking integration of myfaces with JBoss AS6, it was notice myfaces does not
> have a way to override the annotation configurator.
> Ri has a class called AnnotationProvider with this methods:
> public AnnotationProvider(ServletContext sc)
> abstract public Map<?> getAnnotatedClasses(Set<URL> urls)
> the documentation says it is possible to override using this type of
> constructor.
> public AnnotationProvider(ServletContext sc, AnnotationProvider parent)
> We should provide something similar (let's call it AnnotationScanner because
> its objective is scan for annotations).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
