[
https://issues.apache.org/jira/browse/MYFACES-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616050#comment-13616050
]
Leonardo Uribe commented on MYFACES-3704:
-----------------------------------------
I have deployed the application uncompressing the war and removing the
duplicate libraries in WEB-INF/lib folder (if any, but the war file does not
have none).
Probably in this case, the problem is caused by TomEE, when the file is
deployed on the server. The default algorithm follows JSF spec, but it could be
possible that when the list of files under WEB-INF/lib is retrieved by the
annotation provider, the related files that needs to be scanned for annotations
are not retrieved and in that way the scanning is not done.
In that case there are these options:
1. write a custom AnnotationProvider that match with TomEE in this case.
2. try to fix the problem directly in TomEE
3. use org.apache.myfaces.annotation.SCAN_PACKAGES config param and indicate
the packages that needs to be scanned for annotations. See
http://myfaces.apache.org/core21/myfaces-impl/webconfig.html for details.
> Unable to find component when deployed on /demo/faces context
> -------------------------------------------------------------
>
> Key: MYFACES-3704
> URL: https://issues.apache.org/jira/browse/MYFACES-3704
> Project: MyFaces Core
> Issue Type: Bug
> Reporter: Manfred Riem
>
> To reproduce:
> 1. Download
> http://www.manorrock.com/repo/org/manorrock/faces/org-manorrock-faces-demo/2.1.1.0.0/
>
> 2. Deploy to /demo/faces on Tomcat
> It throws an exception. It should work.
> If you need more information please let me know!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
