- #Icefaces 3.3 documentation full
- #Icefaces 3.3 documentation code
- #Icefaces 3.3 documentation professional
The 2.x branch is also in maintenance mode. For users who are still on JSF 2.2, use 2.7.21 instead. Or when you’re using JSF 2.3, pick OmniFaces 3.14.1: Maven users can add OmniFaces by adding the following Maven coordinates to pom.xml of the WAR project:
It is a matter of dropping the OmniFaces 4.0.1 JAR file in /WEB-INF/lib. Note that OmniFaces is due to the mandatory Servlet API dependency not compatible with portlets. 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. If you encounter problems in combination with a specific component library, then by all means report an issue. Even more, the OmniFaces showcase application uses PrimeFaces. OmniFaces should principally integrate perfectly well with most other Faces component libraries. OmniFaces 4.x is since 4.0-M12 fully runtime compatible with Faces 4.0. 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).Īll OmniFaces versions have an optional dependency on JSR303 Bean Validation which is only required when you start to actually use or JsfLabelMessageInterpolator. OmniFaces 2.2 is not anymore backwards compatible with JSF 2.1. OmniFaces 2.0/2.1 is unofficially backwards compatible with JSF 2.1. 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. The CDI specific features remain in version 2.x whereby the CDI dependency is thus made required. 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. OmniFaces 1.x requires Java 1.6, JSF 2.0, EL 2.1, Servlet 2.5.OmniFaces 4.x requires Java 11, Faces 3.0, EL 4.0, Servlet 5.0, CDI 3.0, WS 2.0.Minimum requirementsĪn important design goal will be to have as few dependencies as possible and to be minimally invasive.
#Icefaces 3.3 documentation full
For a full overview of what’s all available in OmniFaces and several live examples, look at the showcase. CDI specific features are available such as transparent support for injection in and an improved which immediately destroys on unload, and web socket based push via. There are also specialized handlers, such as a full ajax exception handler and a combined resource handler. These will range from “all-or-none” validators to automatic converters. OmniFaces can just be used together with any component library.īesides utility classes for working with the Faces API from Java code, such as Faces and Messages, and utility and enhanced components, such as and, OmniFaces will include various general converters, validators and Facelets tag handlers. Such utilities and workarounds can be based on components, but OmniFaces does not necessarily strive to be a “component library” perse. OmniFaces is more geared toward “utilities” that solve everyday practical problems and workarounds for (small) shortcomings in the Faces API.
As such, OmniFaces does not and will never contain things like rich table components or tasty look’n’feels.
#Icefaces 3.3 documentation professional
OmniFaces is a response to frequently recurring problems encountered during ages of professional Faces development and from questions being asked on Stack Overflow.Ĭontrary to some of the other excellent Faces 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.
OmniFaces is a utility library for Faces that focusses on utilities that ease everyday tasks with the standard Faces API. Tired of reinventing JSFUtils or FacesUtils utility classes for every JSF / Jakarta Faces web application and/or homebrewing custom components, taghandlers, etc to workaround or enhance some general shortcomings in Faces? OmniFaces may be what you’re looking for! Take survey fullscreen What is OmniFaces? The below is actually a copy of the homepage.ĭownload - Showcase - API docs - VDL docs - GitHub - Issues - Twitter
#Icefaces 3.3 documentation code
The source code of this showcase can be found here. The UI which you see on this showcase is done by PrimeFaces 12.0.0, with a little bit of custom CSS. Please note that OmniFaces is a Faces utility library, not a Faces UI/component library. Live examples of the OmniFaces components and utilities can be tried out here.Ĭheck out the left side menu togglable menu behind the logo above for all of 'em! Welcome to the OmniFaces Showcase application!
0 kommentar(er)
