X

An Oracle blog about Java Technology

Initial milestone of JSF 2.3

David Delabassee
Software Evangelist
The JSF Expert Group has started to work actively on the next version of the JSF specification (JSF 2.3 - JSR 372) that is slated for inclusion in Java EE 8.  We are still far from the planned date for the finalisation of the specification but we can already see progress as they are being made.  The initial milestone of Mojarra (JSF Reference Implementation) has just been released (download it here).  The Release Notes describes the bugs fixed but also the new features introduced in this milestone.  And from that list, we can see that a lot of focus is put around improving the JSF/CDI integration.

So despite the fact that we are in the early days of JSF 2.3, it is already possible to test some of the new features.  And since Mojarra is open source, it is also possible to use, at any time, the current Mojarra snapshot.  Josh Juneau who is a JSF 2.3 EG member has written a post explaining how to build Mojarra directly from the sources.  So feel free to give JSF 2.3 a(n early) try and provide feedback, this is important for the evolution of the JSF specification. 

We have the usual fine print to conclude, we are still far from the finalization of JSF 2.3, a lot of things will evolve and this is clearly 'work in progress' but transparency is important!

Join the discussion

Comments ( 5 )
  • Abhishek Thursday, January 8, 2015

    Great to see this... First CDI 2.0 and then JSF 2.3 up for grabs. Talk about community driven development !


  • guest Thursday, January 8, 2015

    I hope FacesConverter and FacesValidator will be finally an eligible injection targets... (?)


  • guest Thursday, January 8, 2015

    wow does this mean failover will finally work with cdi viewscope?


  • Manfred Thursday, January 8, 2015

    Injection of FacesConverter and FacesValidator is indeed going to be looked at as a possibility.


  • guest Thursday, January 8, 2015

    Manfred: I meant injection _targets_ . You would then directly convert car's id from URL into Car object, using

    <viewParam id="carId" value="bean.car" converter="carFacesConverter">.

    But you can't access EJB inside CarFacesConverter, at least without hacks.

    Built-in support for ViewExpiredException during Ajax requests would be nice, without 3rd-party tools.

    I had simple use cases where there was a lack of access Flash scope inside JAX-RS.

    Because of long JEE release time, there must be done as much as can be before next release. IMO extracting EJB functionalities into separate annotations is most important. It would much simplify everything.

    Any future plans for JPA?


Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha