Why has JSF 2.2 low priority?

juergen.zimmermann Oct 24, 2013 3:33 AM

When developing a JSF-based web app, you typically don't use pure Mojarra (or MyFaces). Additionally a product like JBoss' RichFaces is often used.

However, the current RichFaces version 5.0.0.Alpha1 is based on Mojarra 2.1 (JSF 2.1), and support for JSF 2.2 is NOT scheduled for the next version.

Do you want that the WildFly users don't use JBoss' RichFaces, and instead any other product like PrimeFaces or Apache Trinidad? I don't think so. I'd appreciate if a "JBossian" could comment this.

1. Re: Why has JSF 2.2 low priority?

ctomc Oct 24, 2013 5:41 AM (in response to juergen.zimmermann)

Moved to RichFaces forum
Actions
2. Re: Why has JSF 2.2 low priority?

bleathem Oct 24, 2013 10:26 PM (in response to ctomc)

We currently compile RichFaces against JSF 2.1, but this does not in and of itself mean that you cannot run your RichFaces applications in a JSF 2.2 environment - they should work. If they do not, please file a jira issue. We are tracking some known JSF 2.2. issues in our jira:
https://issues.jboss.org/issues/?jql=project%20%3D%20rf%20and%20labels%20%3D%20jsf22%20and%20resolution%20%3D%20unresolved

We had initially targeted RichFaces 5.0.0.Alpha2 with these fixes, but we bumped them to Alpha3 as Alpha2 has already been too long in coming out (details why in an upcoming blog post). Alpha3 will have a much quicker turnaround time, with the groundwork that's been laid out in Alpha2, so you'll see some of these JSF 2.2 specific bugs resolved soon.
Actions

Go to original post