MyFaces Core 3.0 Project

This project provides an implementation of the Jakarta Server Faces 3.0 (JSF (Faces) 3.0) specification.

• The API submodule implements all of the classes that are defined in the specification. If you are looking for API documentation about the classes that your JSF application needs to use, then see the javadoc for the API module.
• The Impl submodule provides "invisible" support classes that user code does not directly invoke, but which is needed for a working JSF framework. Examples are the renderer classes for the standard JSF components.

These two libraries (myfaces-api.jar and myfaces-impl.jar) are deployed together with your code to form a JSF web application.

Additionally, there are other submodules:

• The Shared internal submodule provides support "invisible" classes "shared" between other projects in MyFaces land like Tomahawk, Orchestra and Portlet Bridge. A copy of these classes are added to Impl submodule.
• The Bundle submodule provides both API and Impl classes into a single jar file with a OSGi MANIFEST.MF.

If you want to know more about how Jakarta Server Faces works, take a look at the documentation referenced from the main MyFaces site.

Requirements

JSF (Faces) 3.0 requires Java 1.8 or later, JSP (Pages) 3.0, JSTL 2.0, CDI 3.0, WebSocket 2.0 and a Jakarta Servlet 5.0 implementation.

Specifications

MyFaces implements EE4J Jakarta Server Faces Specification

As the Jakarta Server Faces 3.0 TCK has not yet been released, no certification has yet been performed to assure compliance.

Check the download page or you can check the nightly builds here.