No.. RI just makes a test on the JSP-version and disables certain stuff, when it detects a J2EE 1.4 environment (as in TC 5 and WLS 9.2). It then relies on facelets to provide certain functionality...
Sounds like MyFaces is a bit harsher on the user here than the RI. OK... JSF 1.2 officially needs JEE 5. BUT... 1:0 for RI to allow for the gracefull degradation. Just set up a 1.2 RI-app in TC 5.x and watch the log when starting up. You will notice some entries like INFO: JSF1027: [null] The ELResolvers for JSF were not registered with the JSP container. See what I mean? regards Alexander -----Original Message----- From: Andrew Robinson [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 7:24 PM To: MyFaces Discussion Subject: Re: Does MyFaces 1.2 require JSP 2.1? I would ask the facelets list then. According to the JSF specification, JSP 2.1 and Servlet 2.5 support is required for JSF 1.2. On 7/19/07, mraible <[EMAIL PROTECTED]> wrote: > > I am using Facelets - that's why I find it strange. I'm able to use Sun's RI > (the latest version) in place of MyFaces in the same application and > everything works fine. > > Matt > > > Andrew Robinson-5 wrote: > > > > JSF 1.2 requires JSP 2.1 unless you use facelets. > > > > I believe you have to run Tomcat 6 as a minimum version (servlet 2.5 > > support is required) > > > > On 7/19/07, mraible <[EMAIL PROTECTED]> wrote: > >> > >> I should mention: I get the error below on startup when deploying on > >> Tomcat > >> 5.0.25. If I change from MyFaces to Sun's RI and deploy on Tomcat 5.0.25 > >> again, no error. > >> > >> Matt > >> > >> > >> mraible wrote: > >> > > >> > From what I can tell, MyFaces 1.2 requires JSP 2.1. I developed a quick > >> > prototype using MyFaces 1.2 + Facelets 1.1.13 and I get the following > >> > error on startup: > >> > > >> > Exception sending context initialized event to listener instance of > >> class > >> > org.apache.myfaces.webapp.StartupServletContextListener > >> > java.lang.NoSuchMethodError: > >> > > >> javax.servlet.jsp.JspFactory.getJspApplicationContext(Ljavax/servlet/Ser vletContext;)Ljavax/servlet/jsp/JspApplicationContext; > >> > at > >> > > >> org.apache.myfaces.webapp.DefaultFacesInitializer.initFaces(DefaultFaces Initializer.java:102) > >> > at > >> > > >> org.apache.myfaces.webapp.StartupServletContextListener.contextInitializ ed(StartupServletContextListener.java:57) > >> > > >> > If I deploy my app to Tomcat 6, this problem doesn't exist. If I change > >> > from MyFaces 1.2 to Sun's RI 1.2_04, this problem doesn't exist either. > >> > For this reason, it appears to me that MyFaces 1.2 requires JSP 2.1. > >> > > >> > Cheers, > >> > > >> > Matt > >> > > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/Does-MyFaces-1.2-require-JSP-2.1--tf4112432.html#a 11693503 > >> Sent from the MyFaces - Users mailing list archive at Nabble.com. > >> > >> > > > > > > -- > View this message in context: http://www.nabble.com/Does-MyFaces-1.2-require-JSP-2.1--tf4112432.html#a 11693795 > Sent from the MyFaces - Users mailing list archive at Nabble.com. > >
