[MYFACES-4022] Faces Flows are not discovered when the web application is packaged inside an EAR

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.2.8
• Fix Version/s: 2.2.10
• Environment: WildFly 10.0.0, MyFaces 2.2.8, Weld 2.3
• Assignee: Bill Lucy
• Reporter: Hank Ibell
• Created: 07/Dec/15 19:27
• Updated: 19/Mar/16 04:08
• Resolved: 12/Jan/16 21:17

Description

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:

[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

Mojarra supports Faces flow applications when they are packaged inside an EAR.