JSF 2.3 released!

-
After a long and at times intense spec and development process the JSF 2.3 EG is proud to announce that today we've released JSF 2.3.

JSF (JavaServer Faces), is a component based MVC framework that's part of Java EE. JSF 2.3 in particular is part of Java EE 8.

Major new features in JSF 2.3 are a tighter integration with CDI, support for WebSockets, a really cool component search expression framework (donated by PrimeFaces), basic support for extensionless URLs, and class level bean validation.

The age old native managed beans of JSF 2.3 have finally been deprecated (although they are still available for now) in favour of CDI. It's expected that these will be fully removed (pruned) in a future release.

The JSF 2.3 EG would like to thank everyone who contributed to JSF in whatever way, by creating bug reports, testing builds, providing comments and insights on the mailinglist and contributing code. Without those community contributions JSF 2.3 would not have been possible! Thanks to all our fantastic community members!

JSF 2.3 (Mojarra 2.3) can be downloaded per direct from the project's download page.

Maven coordinates for the implementation (includes API) are: 

<dependency>
    <groupId>org.glassfish</groupId>
    <artifactId>javax.faces</artifactId>
    <version>2.3.0</version>
</dependency>

The full implementation can be used for Servlet containers such as Tomcat and Jetty.

Maven coordinates for just the API are: 

<dependency>
    <groupId>javax.faces</groupId>
    <artifactId>javax.faces-api</artifactId>
    <version>2.3</version>
</dependency>

The API jar can only be used as a compile time dependency.

Application servers Payara and GlassFish can be trivially updated by replacing the JSF 2.2 glassfish/modules/javax.faces.jar with the 2.3 version. It's usually a good idea to clear the OSGI cache after that (e.g. rm -rf [payara/gf gome]/ glassfish/domains/domain1/osgi-cache/felix/)

Arjan Tijms

Comments

  1. fxtestxMarch 28, 2017 at 5:56 PM

    Oh, that's amazing. I really like JSF =)

    Now, just for curiosity, is there any plans for JSF on Java EE 9? xD

    ReplyDelete
    Replies
    1. Arjan TijmsMarch 29, 2017 at 2:11 AM

      Great that you like JSF ;)

      Lots of plans for JSF in Java EE 9. Among others actually removing all the deprecated stuff is considered, as well as making extensionless URLs more automated, improving the component model, having a unified repeat (base) component and lots more.

      Work on Mojarra 2.4 has already started, but no new spec features can be added right now as this requires a new EG to be assembled.

      Delete
    2. AlbertoApril 6, 2017 at 3:54 AM

      I think the "Open EntityManager In View" or "Open Extended Persistence Context In View" patterns should be added to JSF 2.4.

      Delete
    3. Ronald van KuijkJuly 30, 2017 at 4:20 AM

      Would https://github.com/omnifaces/omnifaces/issues/394 require a new EG? And https://myfaces.apache.org/wiki/core/user-guide/configuration-of-special-features/view-pooling.html?

      Delete
    4. Arjan TijmsJuly 30, 2017 at 2:41 PM

      >Would https://github.com/omnifaces/omnifaces/issues/394 require a new EG? And https://myfaces.apache.org/wiki/core/user-guide/configuration-of-special-features/view-pooling.html?

      That would indeed mostly require a new EG, although it's possible to add features in an implementation specific way (so you can enable them via a com.sun param, for instance)

      Delete
  2. TomkMarch 31, 2017 at 7:29 AM

    Thanks for the heads up. Good work on it to all those who contributed.

    ReplyDelete
  3. armenApril 4, 2017 at 7:02 AM

    I am going to test with Tomcat. As I understand no one application server support jsf 2.3 at the moment? Do I need integrate weld with tomcat?:((((

    ReplyDelete
    Replies
    1. Arjan TijmsApril 4, 2017 at 8:22 AM

      Payara and GlassFish 4.1.x as well as JBoss/WildFly support JSF 2.3, given that you update the jar, or jars (in case of JBoss) yourself.

      For Tomcat a CDI implementation needs to be present indeed, but it does not necessarily have to be Weld.

      Delete
    2. armenApril 4, 2017 at 10:41 AM

      This comment has been removed by the author.

      Delete
    3. armenApril 4, 2017 at 10:59 AM

      Hi Arjan, Many thanks.
      I was wait this release of JSF, from 2008 all my projects in JSF :))), used all versions.
      I am integrating all kind of technologies with JSF:))

      Delete
    4. Arjan TijmsApril 4, 2017 at 2:39 PM

      Great, thanks for the head ups! :)

      Delete
  4. SamuazMay 10, 2017 at 10:44 PM

    Excuseme, i want to try jsf2.3 websocket and others new features, i add the
        org.glassfish
        javax.faces
        2.3.0


    to my pom but when i try to use its not there.. is there any procedure to use 2.3?

    thanks.

    ReplyDelete
    Replies
    1. SamuazMay 10, 2017 at 10:46 PM

      the f:websocket tag is not there and also all others feautres

      Delete
    2. MikeJuly 13, 2017 at 10:47 AM

      It would be really helpful if this question was answered. For me, it's the f:validateWholeBean that is not there.

      Delete
    3. Arjan TijmsJuly 13, 2017 at 11:50 AM

      It basically should work of course, as we developed examples and test using Mojarra as well including f:validateWholeBean.

      If you want, could you post a question about this on stackoverflow with details about the environment and a reproducer if possible? That site is much better suited to answering questions than the comment section here.

      Thanks!

      Delete
  5. UnknownJune 27, 2017 at 5:55 AM

    It would be great if JSF would have support for:
    -json objects in its components (tables, forms, inputs, outputs)
    -rest calls from the components (buttons, links & tables)
    -access to the local storage via a component (write/read to/from)
    -support for restfull urls (like: /user/1234/orders)
    -exception mapping/handling (when exception A occurs then go to page X and show msg M)
    -more advanced navigation rules:
    * support for authentication and authorization tags (example page X requires loggedIn=true or rolesAllowed=#{allowedRoles or identity.hasRole('admin'), login-page=/login.xhtml}
    * support for (starting/ending) conversation (example: page X requires conversation, no-conversation-page=/main.xhtml)
    * support for page actions. Put f:viewParam and f:action in the navigation rules.
    * regex matching of urls.

    Basically, the world is moving to stateless architectures and JSF should make it possible to build web clients that can connect to backend systems that run somewhere else and retrieve data from it, validate it and show it on the screen.

    I see a huge improvement in this area.

    ReplyDelete
  6. AnonymousSeptember 6, 2017 at 3:16 AM

    Does JSF 2.3 supports HTML5 fully? In JSF2.2 there is way to write HTML5 tags . Is it still XHTML or HTML?

    ReplyDelete
  7. UnknownSeptember 28, 2017 at 2:27 PM

    This comment has been removed by the author.

    ReplyDelete
  8. repelisJanuary 20, 2020 at 2:37 PM

    Thanks for post this. The information is very useful for all the reades.

    ReplyDelete

Post a Comment

Popular posts from this blog

Jakarta EE Survey 2022

-
At OmniFaces we poll the community from time to time and again about Jakarta EE (previously Java EE) and related technologies. With the transfer of Java EE to Jakarta EE now fully completed and Jakarta EE 10 released , people are now starting to think about Jakarta EE 11 , the second Jakarta EE feature release. As such it's a good time to poll the community again. This year we're doing so in cooperation with OmniFish . In the 2022 edition, there are 4 categories of questions again: Current usage of Jakarta EE Servlet containers APIs related to Jakarta EE The future of Jakarta EE Compared to 2020, we simplified some of the questions once more; again omitting some of the less popular options to make it more manageable. We kept the questions about the future of Jakarta EE and MP together as this issue still isn't resolved. We also ask about the preferred Jakarta EE cadence. As Jakarta EE 10 is the first feature release, we haven't really established a cade...
Read more

Implementing container authentication in Java EE with JASPIC

-
This article takes a look at the state of security support in Java EE 6, with a focus on applications that wish to do their own authentication and the usage of the JASPI/JASPIC/JSR 196 API. Update: the further reading section has been moved to my ZEEF page about JASPIC . This contains links to articles, background, questions and answers, and more.   Declarative security is easy In Java EE it has always been relatively straightforward to specify to which resources security constraints should be applied. For web resources (Servlets, JSP pages, etc) there is the <security-constraint> element in web.xml, while for EJB beans there's the @RolesAllowed annotation. Via this so called 'declarative security' the programmer can specify that only a user having the given roles is allowed access to the protected web resource, or may invoke methods on the protected bean. The declarative model has a programmatic counterpart via methods like HttpServletRequest#isUserInR...
Read more

Counting the rows returned from a JPA query

-
Despite being almost ten years old, the JPA specification to this day has rather poor support for basic paging/sorting/filtering. Paging/sorting/filtering is used in a lot of (CRUD) applications where the result from a query is shown in a table, and where the user can scroll through the results one page at a time, and where this result can be sorted by clicking on any of the table column headers. In order to support this a number of things are generally needed: The total number of rows (or entities) in the full result must be known There should be support for an offset in the full result and a limit for the amount of rows that will be obtained The column (attribute) on which to sort must be dynamically added to the query Search expressions must be dynamically added to the query As it appears, only offset/limit is directly supported in JPA. A sorting column can only be added dynamically when using the overly verbose and hard to work with Criteria API. Search expressions...
Read more