[
https://issues.apache.org/jira/browse/MYFACES-4289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16830719#comment-16830719
]
Thomas Andraschko commented on MYFACES-4289:
--------------------------------------------
comitted a fix to 2.3.x - need to rereun integration tests on thursday and port
it to 3.x.
> 404 Resource Errors after MyFaces-4270
> --------------------------------------
>
> Key: MYFACES-4289
> URL: https://issues.apache.org/jira/browse/MYFACES-4289
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.3.3
> Reporter: Volodymyr Siedlecki
> Assignee: Thomas Andraschko
> Priority: Major
> Fix For: 3.0.0-SNAPSHOT, 2.3.4
>
> Attachments: sample.war, source.zip
>
>
> Hello,
> I have an application that works with JSF 2.3.2, but doesn't work with JSF
> 2.3.3. The RichFaces resources do not load.
> I looked at the commits of what changed, and I've narrowed it down to this
> one:
> https://github.com/apache/myfaces/commit/cb75b5a6486c61c6bd3e3befc62cce58576f6be0
>
> This issue, from my understanding, is caused by incorrect mappings.
> After investigating, I noticed that getFacesServletRegistration returns a
> ServletRegistration that doesn't contain mappings to the resources. I believe
> this is because of the isFacesServlet check on line 53 of
> FacesServletMappingUtils.java (of the commit mentioned). Prior to the
> commit, there was code to handle non-FacesServlet Mappings ( line 194-207 on
> FacesServletMappingUtils.java ).
> I would appreciate any help into this.
> Thank you.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
