[
https://issues.apache.org/jira/browse/MYFACES-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15094966#comment-15094966
]
Bill Lucy commented on MYFACES-4022:
------------------------------------
Thanks for all the work on this, Hank; as discussed on the mailing list, I went
ahead and committed the patch here.
> Faces Flows are not discovered when the web application is packaged inside an
> EAR
> ---------------------------------------------------------------------------------
>
> Key: MYFACES-4022
> URL: https://issues.apache.org/jira/browse/MYFACES-4022
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.2.8
> Environment: WildFly 10.0.0, MyFaces 2.2.8, Weld 2.3
> Reporter: Hank Ibell
> Assignee: Leonardo Uribe
> Priority: Minor
> Fix For: 2.2.10
>
> Attachments: FacesFlowTest.ear, myfaces-4022.patch,
> myfaces-4022.patch, myfaces-4022.patch
>
>
> Faces flows built with the FlowBuilder API are not found when the web
> application is packaged inside an EAR. When deploying just the web
> application itself, the application's flows are discoverable however.
> A sample application has been provided to demonstrate the issue. The button
> 'Start Test Flow' should be clicked on the page /FacesFlowTest1/index.xhtml.
> The flow will not be entered and MyFaces will try to navigate to a view with
> the flow id instead:
> {panel:bgColor=#e8e8e8}
> [org.apache.myfaces.application.NavigationHandlerImpl] (default task-2)
> getOutcomeNavigationCase -> viewIdToTest: test-flow-1.xhtml
> [org.apache.myfaces.shared.resource.ResourceHandlerCache] (default task-2)
> Attemping to get resource from cache for test-flow-1.xhtml
> [org.apache.myfaces.application.NavigationHandlerImpl] (default task-2)
> handleNavigation fromAction=test-flow-1 outcome=test-flow-1 no matching
> navigation-case found, staying on current ViewRoot
> {panel}
> Mojarra supports Faces flow applications when they are packaged inside an EAR.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
