OmniFaces 4.3 has been released!
A couple of new things were introduced:
<o:importConstants>
and<o:importFunctions>
got a newloader
attribute where you can specify an object whose class loader will be used to load the class specified in thetype
attribute. In the end this should allow you to use a more specific class when there are duplicate instances in the runtime classpath, e.g. via multiple (plugin) libraries.- Inspired by this new
loader
attribute, a new<o:loadBundle>
taghandler was introduced which also allows you to useloader
attribute to load the bundle from a more specific library in case there are duplicate instances in the runtime classpath. Faces(Local)#isAuthenticated()
so that you can with less code check whether the current request is authenticated.
You can find the complete list of additions, changes and fixes at What's new in OmniFaces 4.3? list in showcase.
Installation
Non-Maven users: download OmniFaces 4.3 JAR and drop it in /WEB-INF/lib
the usual way, replacing the older version if any.
Maven users: use <version>4.3</version>
.
<dependency>
<groupId>org.omnifaces</groupId>
<artifactId>omnifaces</artifactId>
<version>4.3</version>
</dependency>
How about OmniFaces 3.x, 2.x and 1.1x?
OmniFaces 3.x got the same bugfixes as 4.3 and has been released as 3.14.4. This version is for JSF 2.3 users with CDI. In case you've already migrated to Faces 3.0 or 4.0, please use OmniFaces 4.x instead. OmniFaces 2.x got the same bugfixes as well and has been released as 2.7.24. This version is for JSF 2.2 users with CDI. In case you've already migrated to JSF 2.3, please use OmniFaces 3.x instead.
The 1.1x is basically already since 2.5 in maintenance mode. I.e. only critical bugfix versions will be released. It's currently still at 1.14.1 (May 2017), basically featuring the same features as OmniFaces 2.4, but without any JSF 2.2 and CDI things and therefore compatible with CDI-less JSF 2.0/2.1.
No comments:
Post a Comment