Hide Forgot
Description of problem: Spring Web Flow 2.3.0 does not work with JSF 2.1 bug in Springsource JIRA: UnsupportedOperationException for isReleased on FacesContext when using JSF 2.1 https://jira.springsource.org/browse/SWF-1467
Created attachment 565641 [details] FlowFacesContext.java
Created attachment 565642 [details] FlowViewStateManager.java
Solution: Include listed classes in any Spring Webflow 2.3 application that uses JSF 2 running on JBoss AS7. Also fixes https://jira.springsource.org/browse/SWF-1461 Add to Release Notes
Can I have a bit more info on this bug, please? In what way does Spring Web Flow 2.3.0 not work with JSF 2.1? What behaviour presents?
This is actually referring to a couple if Spring WebFlow known issues https://jira.springsource.org/browse/SWF-1461 https://jira.springsource.org/browse/SWF-1467 Both of them are essentially incompatibilities between Spring WebFlow and the JSF API. The former causes a NPE (shown in the JIRA item) to be thrown when a JSF 2 page is accessed outside a Spring Web Flow flow. The second is caused by an incompatibility between Spring Web Flow and the JSF 2.1. Simply put, the two cannot be used together because this will always result in the java.lang.UnsupportedOperationException shown in the JIRA item.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Some elements of Spring WebFlow and the JSF 2 API are incompatible. In one instance, a NullPointerException is thrown when a JSF 2 page is accessed outside of a Spring Web Flow flow; in a second instance, Spring Web Flow and JSF 2.1 cannot be used to together because it results in a java.lang.UnsupportedOperationException error. These issues can be worked around by including listed classes in any Spring WebFlow 2.3 application that uses JSF 2 and it is running of JBoss Enterprise APplication Platform 6.
Verified usage of attached classes and release notes in ER2.
* BOM upgraded to reference Spring Webflow 2.3.1 * Workaround classes deleted in commit 46c97e0bd3f86e8fd525432596d3c7f4ae87aa88 * Technical notes need to be removed Added Marek for productization work
Deleted Technical Notes Contents. Old Contents: Some elements of Spring WebFlow and the JSF 2 API are incompatible. In one instance, a NullPointerException is thrown when a JSF 2 page is accessed outside of a Spring Web Flow flow; in a second instance, Spring Web Flow and JSF 2.1 cannot be used to together because it results in a java.lang.UnsupportedOperationException error. These issues can be worked around by including listed classes in any Spring WebFlow 2.3 application that uses JSF 2 and it is running of JBoss Enterprise APplication Platform 6.
Verified in WFK 2.0.0.ER8
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: In JBoss Web Framework Kit 2-Beta, some elements of Spring WebFlow and the JSF 2 API were incompatible. In one instance, a NullPointerException was thrown when a JSF 2 page was accessed outside of a Spring Web Flow flow; in a second instance, Spring Web Flow and JSF 2.1 could not be used together because it resulted in a java.lang.UnsupportedOperationException error. Spring WebFlow 2.3.1 is certified with JBoss Web Framework Kit 2 and does not have this issue, so it is fixed with this release.
Fixed in WFK 2.0.0.GA.