Tag Archives: JSF1.1

Java Server Faces ( JSF 1.0 / JSF 1.1 / JSF 1.1_01 / JSF 1.2 / JSF2.0 ) Comparision Table

Version JSR Release What’s on the release? Support Release Date Additional Info
JSF 1.0 JSR 127 Initial release of the JSF specification. Separate release that wasn’t part of any Java EE/J2EE release. Servlet 2.3 and
JSP 1.2
11/03/2004 DEPRECATED
JSF 1.1 JSR 127 just bug fixes released and no changes to rendering HTML kit Servlet 2.3 and
JSP 1.2
02/05/2004 DEPRECATED
JSF 1.1_01 bug fixes and performance improvements. JDK 1.3.1 or later.
JSF 1.2 JSR 252 Many improvements to core systems and APIs. Coincides with Java EE 5. Initial adoption into Java EE. Servlet 2.5 and JSP 2.1
But minimum it supports Servlet 2.3 and JSP 1.2.
Tomcat support 6.0 not 5.5.version
11/05/2006
JSF 2.0 Major release for ease of use, enhanced functionality, and performance. Coincides with Java EE 6. 28/06/2009
JSF 2.1 Current version. Second maintenance release of 2.0. Only very minor amount of spec changes 22/10/2010


(WAS 6.1) Websphere application server 6.0(1)X supports JSF1.1 / JSF1.2 and Web application class loader settings to overcome JSF errors

Unexpected results will occurs, If the JSF application is developed on JSF v1.2 and then if running the application on 6.x which uses JSF 1.1 ( IBM WebSphere Application Server v 6.x uses faces 1.1).

Note: IBM WebSphere Application Server v 7.x uses JSF 1.2.

In IBM WebSphere Application Server v6.1 the IBM JSF implementation has been moved into the Web container in anticipation for J2EE 5 /1.5.This being so it is not possible to load the mixed IBM JSF implementation classes and MyFaces TDLs as was possible with v6.0

If the Web modules classloader is not set to PARENT_LAST, pages will not be displayed and may JSF errors will occur. The only supported solution to this issue is to package the MyFaces JAR files inside the WEB-INF/lib directory and set the Web module classloader to PARENT_LAST.