Give Hint when CustomAnnotationProvider needed, ex. when
DefaultAnnotationProvider fails on jboss AS6 related to jboss-vfs urls
-------------------------------------------------------------------------------------------------------------------------------
Key: MYFACES-3212
URL: https://issues.apache.org/jira/browse/MYFACES-3212
Project: MyFaces Core
Issue Type: Improvement
Components: JSR-314
Affects Versions: 2.1.1, 2.0.7
Environment: JBoss AS6 and others
Reporter: Pablo Morales Mombiela
When scanning class files searching for annotatios, if
org.apache.myfaces.config.annotation.DefaultAnnotationProvider can not open URL
quietly do nothing. It's really difficult to discover what is going on and many
people may think that provided MyFaces can not be used on JbossAS6
I think that
org.apache.myfaces.config.annotation.DefaultAnnotationProvider._getAlternativeJarFile(URL
url) must report/log some error before 'return null' and point the user to
implement a CustomAnnotationProvider in order to make it work.
I didn't found any documentation that make this clear at any point. MyFaces
documentation should explain:
- why is needed
- How to provide custom DefaultAnnotationProvider in web.xml context param
or in META-INF/services/org.apache.myfaces.spi.AnnotationProvider
- Explain that in JBoss AS6 a custom implementation must be provided able to
use jboss-vsf and point to VSF documentation in
http://community.jboss.org/wiki/VFS3UserGuide. We implemented a scanner based
on VSF visitor pattern that work great but spent a huge amount of time on it.
Can't this provider be included because of license issues with jboss?
This will make migration from Mojarra much faster when using jboss and probably
others.
Thank you for your attention.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
