Beyond Java

OmniFaces 2.0 has been released today (Nov 24, 2014).

What is OmniFaces?

For those who don't know OmniFaces yet: OmniFaces is... different. It's a JSF library that doesn't focus on providing GUI widgets. Instead, it integrates into your existing JSF ecosystem and adds functions lacking in JSF. OmniFaces 2.0 offers 90 components, give or take a few, most of them dedicated to non-GUI components. My favorite OmniFaces features are the CombinedResourceHandler, which accelerates the delivery of most JSF pages tremendously, the SelectItemsConverter which makes JSF comboboxes a lot less scary and the FullAjaxExceptionHandler, which make exceptions occurring during an AJAX request visible.

What's new in OmniFaces 2.0?

Many things. In this article I'll focus on two interesting new features: Bean validation at class level and simplified display of images.

JSF 2.0 added support for the Bean Validation API (aka JSR 303). Sad thing it didn't support the API completely. Neither does the current version, JSF 2.2. To fill the gap OmniFaces adds <o:validateBean />. Among other things, this allows you to implement cross-field validations. Add <o:validateBean value="#{myBean}"> to your form to have the bean validated. In my opinion, this solution still doesn't fulfill the promise of JSR 303 (which says a simple annotation to the class does the trick), but to be fair, it's not easy to meet the requirements of the JSF lifecycle. The JSF specification requires that invalid values are not written to the bean. Therefore framework developers have to copy the bean to implement things like class level or cross-field validation. By this measure, OmniFaces does a pretty good job. Read the full story here.

Have you ever tried to display an image stored in a database? That's one of those things that are simple using basic servlets, but horrendously difficult using JSF. <o:graphicImage> saves you from learning about ResourceHandlers. All you have to do is to define a CDI bean returning the image as a byte array: