You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@myfaces.apache.org by Apache Wiki <wi...@apache.org> on 2011/02/12 14:01:20 UTC

[Myfaces Wiki] Update of "myfaces/Drafts/Site/Core" by BartKummel

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Myfaces Wiki" for change notification.

The "myfaces/Drafts/Site/Core" page has been changed by BartKummel.
The comment on this change is: Initial version.
http://wiki.apache.org/myfaces/myfaces/Drafts/Site/Core

--------------------------------------------------

New page:
The Apache MyFaces Core project is where it all started. It does not do much more than implement the JSF standard. There are currently three relevant versions of this standard:
 * JSF 1.1: This version of the standard fixes some bugs in the original 1.0 version. Both the 1.0 and the 1.1 versions were specified by the Java Specification Request (JSR) number JSR 127. The versions of MyFaces Core implementing this version of JSF are numbered 1.1.x.
 * JSF 1.2: This version of the JSF standard was specified by a separate JSR, with the number JSR 252. JSF 1.2 adds some important improvements over JSF 1.1. The MyFaces Core versions implementing JSF 1.2 are numbered 1.2.x.
 * JSF 2.0: This is the latest version of the JSF standard, part of the Java EE 6.0 platform. JSF 2.0 is specified in JSR 314, which had its final release on July 1, 2009. The versions of MyFaces Core implementing JSF 2.0 are numbered 2.0.x. 

The Core project currently has branches for each of these JSF versions. The 1.1, 1.2 and 2.0 versions are stable and are updated regularly. Every Java EE application server comes with a bundled JSF implementation. Often the reference implementation (RI), known as "Mojarra", is used for this. However, you can bundle an alternative JSF implementation to be used with your project. This way, you can use MyFaces Core as JSF implementation on every Java EE application server. One of the benefits of using MyFaces Core is that it generates more informative logging, which can be handy while debugging.