Welcome to the OmniFaces Showcase application!

Live examples of the OmniFaces components and utilities can be tried out here. Check out the left side menu togglable menu behind the logo above for all of 'em!

Please note that OmniFaces is a JSF utility library, not a JSF UI/component library. The UI which you see on this showcase is done by PrimeFaces 6.0, with a little bit of custom CSS.

This showcase shows the SNAPSHOT version of OmniFaces! For the showcase of the stable version of OmniFaces, please go to showcase.omnifaces.org.

The source code of this showcase can be found here. The below is actually a copy of the homepage.

Download - Showcase - API docs - VDL docs - GitHub - Issues - Twitter


23 January 2017: OmniFaces 2.6-RC2 is now available for testing! As long as no new issues are reported, the 2.6 final version will be released in a week or two.


This features among others a new @ViewScoped(saveInViewState=true) attribute which saves the entire bean in JSF view state when client side state saving is enabled (instead of in HTTP session). In fact, such bean never expires as long as the HTML page exists. And, several general purpose converters have been added, such as omnifaces.TrimConverter, omnifaces.ToLowerCaseConverter, omnifaces.ToUpperCaseConverter and omnifaces.ToCollectionConverter. Further several helper methods of Faces utility class are now directly available in EL as well via the new implicit EL object #{faces}, such as #{faces.development}, #{faces.requestBaseURL}, etc. See also What’s new in OmniFaces 2.6? section of the snapshot showcase.

What is OmniFaces?

Tired of reinventing JSFUtils or FacesUtils utility classes for every JSF web application and/or homebrewing custom components, taghandlers, etc to workaround or enhance some general shortcomings in JSF? OmniFaces may be what you’re looking for!

OmniFaces is a utility library for JSF 2 that focusses on utilities that ease everyday tasks with the standard JSF API. OmniFaces is a response to frequently recurring problems encountered during ages of professional JSF development of the JDevelopment team and from questions being asked on Stack Overflow.

Contrary to some of the other excellent JSF 2 component libraries out there (like PrimeFaces, BootsFaces, or ButterFaces), OmniFaces does not contain any of the beautiful visually oriented components that those other libraries are already known and loved for. As such, OmniFaces does not and will never contain things like rich table components or tasty look’n’feels. OmniFaces is more geared toward “utilities” that solve everyday practical problems and workarounds for (small) shortcomings in the JSF API. Such utilities and workarounds can be based on components, but OmniFaces does not necessarily strive to be a “component library” perse. OmniFaces can just be used together with any component library.

Besides utility classes for working with the JSF API from Java code, such as Faces and Messages, and utility and enhanced components, such as <o:highlight> and <o:viewParam>, OmniFaces will include various general converters, validators and Facelets tag handlers. These will range from “all-or-none” validators to automatic <f:selectItem(s)> converters. There are also specialized handlers, such as a full ajax exception handler and a combined resource handler. CDI specific features are available such as transparent support for injection in @FacesConverter and @FacesValidator, an improved @ViewScoped which immediately destroys on unload, and web socket based push via <o:socket>. For a full overview of what’s all available in OmniFaces and several live examples, look at the showcase.

Minimum requirements

An important design goal will be to have as few dependencies as possible and to be minimally invasive. So far, OmniFaces 2.x requires Java 1.7, JSF 2.2, EL 2.2, Servlet 3.0, CDI 1.1 and WebSocket 1.0 APIs which is already minimally available in a fairly modern servlet container serving a JSF 2.2 web application. Legacy OmniFaces 1.x only requires Java 1.6, JSF 2.0, EL 2.1 and Servlet 2.5 APIs which is already minimally available in a fairly modern servlet container serving a JSF 2.x web application.

Since OmniFaces 1.6 there was an optional dependency on CDI, which turned out to be troublesome in some outdated environments, so they were since version 1.10 removed from version 1.x for a better compatibility with those environments. The CDI specific features remain in version 2.x whereby the CDI dependency is thus made required. Version 1.x users who are already using CDI specific features on a JSF 2.1 environment should be able to effortlessly migrate to version 2.x. OmniFaces 2.0/2.1 is unofficially backwards compatible with JSF 2.1. OmniFaces 2.2 is not anymore backwards compatible with JSF 2.1.

Since OmniFaces 2.3 there is a required dependency on JSR356 WebSocket which is already available in any Java EE 7 container and in even earlier versions of servletcontainers (Tomcat supports it since 7.0.27 and Jetty supports it since 9.1.0).

All OmniFaces versions have an optional dependency on JSR303 Bean Validation which is only required when you start to actually use <o:validateBean> or JsfLabelMessageInterpolator.

OmniFaces should principally integrate perfectly well with most other JSF component libraries. Even more, the OmniFaces showcase application uses PrimeFaces. If you encounter problems in combination with a specific component library, then by all means report an issue. We’ll investigate if it’s caused by OmniFaces or the component library in question and fix it or propose a workaround solution, depending on the nature of the problem. Note that OmniFaces is due to the mandatory Servlet API dependency not compatible with portlets.


It is a matter of dropping the OmniFaces 2.5.1 JAR file in /WEB-INF/lib.

Maven users can add OmniFaces by adding the following Maven coordinates to pom.xml of the WAR project:


For users on outdated environments who can’t/won’t use CDI, use 1.14 instead. It doesn’t contain anything from CDI nor new things which were added in 2.x, but it does contain enhancements and bugfixes to existing 1.x things. Note that there is no 1.15. The 1.14 is latest version of the 1.x branch which is now in maintenance mode.

The OmniFaces UI components/taghandlers and EL functions are available under the following XML namespaces:


OmniFaces is designed as a WAR library (web fragment library) and therefore can’t be placed elsewhere in the webapp’s runtime classpath outside WAR’s own /WEB-INF/lib, such as EAR’s /lib or even server’s or JRE’s own /lib. When OmniFaces JAR file is misplaced this way, then the webapp will be unable to find OmniFaces-bundled JSF/CDI annotated classes and throw exceptions related to this during deploy or runtime. To solve it, put back OmniFaces in WAR’s /WEB-INF/lib. Also note that you shouldn’t have duplicate OmniFaces JAR files, otherwise CDI will throw exceptions related to ambiguous dependencies during deploy.


Version history can be found in “What’s new” page at the showcase.

OmniFaces 2.0 - 2.5

Required: Java 1.7, JSF 2.2, EL 2.2, Servlet 3.0, CDI 1.1 and since 2.3 WS 1.1
Optional: BV 1.1

OmniFaces 1.10 - 1.14

Required: Java 1.6, JSF 2.0, EL 2.1, Servlet 2.5
Optional: BV 1.0

OmniFaces 1.0 - 1.8

Required: Java 1.6, JSF 2.0, EL 2.1, Servlet 2.5
Optional: BV 1.0 and since 1.6 CDI 1.0



Mastering OmniFaces

Mastering OmniFaces

Mastering OmniFaces is since October 5, 2015 available at Amazon.com. This book was created in cooperation with the creators of OmniFaces, Bauke Scholtz and Arjan Tijms. From the beginning on, they worked together with Anghel Leonard and Constantin Alin to get this book ready, and have reviewed it from top to bottom.

A little over 500 pages, this book goes into depth identifying general JSF problems and describing how OmniFaces has solved it, hereby uncovering several patterns and tricks. Basically, the working of every OmniFaces component, taghandler, converter, validator, and several handlers and listeners is break down in the book in a problem-to-solution approach. Reading this book is a true learning exercise as to exploiting JSF API, creating custom components, renderers, tagfiles and what not provided by JSF API in order to solve common problems.

A must read if you also like Mastering JSF 2.2 from the same author!

PrimeFaces & OmniFaces powers combined

PrimeFaces & OmniFaces powers combined

PrimeFaces & OmniFaces powers combined is an e-book of Anghel Leonard containing complete examples showing off situations when the PrimeFaces UIs take advantage of OmniFaces help.


If you have specific programming problems or questions related to the OmniFaces library, feel free to post a question on Stack Overflow using at least the jsf and omnifaces tags.

If you have found bugs or have new ideas, feel free to open a new issue.

If you have general feedback that’s not either a question, bug report or feature request, or if you have a review/rating, please feel free to leave it at OpenHUB.

OmniFaces in the worldwide news and literature