[
https://issues.apache.org/jira/browse/MYFACES-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15488943#comment-15488943
]
Leonardo Uribe commented on MYFACES-4063:
-----------------------------------------
It is necessary to provide more information in order to see if something is
wrong or not. The algorithm implemented follows JSF spec in both faces flow and
resource handler. I guess the problem should be something related to how
"contracts" attribute is handled in your application, but besides that I do not
see anything else that can help to detect a problem. I'll close this issue a
cannot reproduce. Please reopen it again if you can provide more concrete
evidence about the problem mentioned.
> Facelet when loaded with navigation-case ignores contracts mapping
> ------------------------------------------------------------------
>
> Key: MYFACES-4063
> URL: https://issues.apache.org/jira/browse/MYFACES-4063
> Project: MyFaces Core
> Issue Type: Bug
> Components: General, Portlet_Support
> Affects Versions: 2.2.8
> Environment: WebSphere Application Server with JSF 2.2 myfaces
> Reporter: Nidhi Goel
>
> Create a JSF portlet using facelets flow using navigation-handler in
> faces-config. Define resource library contracts for various resources loaded
> in those facelets. Run the application to see contracts successfully resolved
> for initial view facelet. However, for all the later requests where
> facelet/view gets loaded from navigation-case defined, we see that contracts
> resources don't get resolved and resource not found error is thrown for
> those. The resource is tried to be resolved from the base default location
> and not in contracts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
