Hi everyone,
While the transfer is technically still in progress for JSF / Mojarra, the code has been available on Github for some time now, and some work has already started.
The proposed theme for the next version is doing away with legacy things that have crept up over the years. As such the proposed new version number is *3.0*.
One of the initial things to be removed is JSP support. I've talked about this with various people individually over the last year and with few exceptions this change was welcomed. JSP support has practically been deprecated ever since JSF 2.0 was released, and for some time newer features in JSF were explicitly not supported in JSP. I think it's indeed time we let go of this old beast.
Note that JSP is still absolutely fine to be used by it self (outside JSF), but for JSF it has never been a good match.
The second thing to be removed is the native managed bean system. JSF 2.0 already came with a warning that one day the parallel effort in the JCP to create a separate managed bean system (now known as CDI) would take its place. Between 2.0 and 2.3 support for this native managed bean system was already diminished. Flows for example used CDI beans exclusively, and in JSF 2.3 the managed bean package was deprecated. In JSF 2.3 CDI based alternatives were introduced for the last remaining unique features of the native managed bean system. Issues about various improvements for this native managed bean system were closed a long time ago with the explanation that CDI was the way forward.
For 3.0 I think it's now time to let this go as well.
Furthermore, there's a variety of other deprecated stuff within JSF, for instance remnants of the ancient native _expression_ language that JSF once had. I'd like to remove these as well.
Another candidate for removal may be the full state saving mechanism. Ongoing support for this was once needed to allow older component libraries to work on JSF, but since partial state saving has been around since 2.0 as well, it may be time to let go of this one too.