It makes sense, that was my hunch as well. I needed an expert opinion. Thanks a bunch for the detailed feedback.
________________________________ From: Scott O'Bryan [mailto:[EMAIL PROTECTED] Sent: Wed 5/14/2008 3:53 PM To: MyFaces Discussion Subject: Re: Myfaces + Websphere 6.1 > How to fetch ResponseStateManager? There is a slight mixup here and these MTR's are not easy. Let me try to explain. JSF 1.2 requires JSP 2.1 which is in J2EE 5. Furthermore, it requires J2SE5 because of all the coolness in J2SE5... Trinidad 1.2.x requires JSF1.2 and J2SE5. Facelets (which is not part of J2EE) is an alternative display technology to JSP. In other words, when using Facelets, you don't use the JSP engine at all. Facelets added a "hack" which allowed JSF 1.2 to run on pre-J2EE 5 branches. It did this by implimenting the EL-Resolver functionality from the JSP 2.1 specification that was required by JSF 1.2 inside of the Facelet's engine. While this is not an "officially" supported configuration, there are a lot of people using it so it's pretty well tested. It is, however, off spec. As such, without Facelets, you cannot get JSF 1.2 to run on a pre-J2EE5 server. Therefore, had the subject been "MyFaces + Websphere 6.1 + Facelets" instead of just "MyFaces + Websphere 6.1", I would have probably stated that 1.2 was possible on such a container... :) I hope that all makes sense. Scott Murtaza Goga wrote: > Just a parallel question Scott. We do have a successful deployment with > using MyFaces 1.2.2, Trinidad 1.2.7 and Facelets 1.1.14 within WAS 6.1. The > MyFaces documentation says that it needs a JEE5 engine. WAS 6.1 is not at > that spec level, and we are running fine. I am wondering what features > require the JEE5 spec. > > Thanks for your response, > Murtaza. > > -----Original Message----- > From: Scott O'Bryan [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 14, 2008 12:48 PM > To: MyFaces Discussion > Subject: Re: Myfaces + Websphere 6.1 > How to fetch ResponseStateManager? > > Yes, if your using JSF 1.2 and Facelets, that will allow you to work on > WAS. And you can either set the classloader policy or you can simply > take the JSF1.1 libraries out of your root classpath. :) > > Scott > > Zheng, Xiahong wrote: > >> Did you set the "Class Loader Order" policy at the module level as well? >> Under Enterprise Applications -> yourEAR -> Managing Modules -> yourwar? I >> recently had some API conflict when I use Sun's RI 1.2 (with facelets, of >> course) on WAS6.1 and setting the above "Class Loader Order" to "Classes >> loaded with application class loader first" at the module level resolved the >> problem. >> >> -----Original Message----- >> From: Christian Koelle [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, May 13, 2008 5:04 PM >> To: [email protected] >> Subject: Myfaces + Websphere 6.1 > How to fetch ResponseStateManager? >> >> Hello, >> >> I am trying to migrate my jetty:run-alike myfaces application to Websphere >> 6.1, i.e. the Websphere bundled in IBM's Rapid Application Developer. >> >> No matter wether I use Myfaces 1.1.5 or Myfaces 1.2.2, I get the following >> error if I deploy and start the application: >> >> "java.lang.NoSuchMethodError: >> javax/faces/render/ResponseStateManager.getState(Lj..." >> >> Please note that I have set the classloading to "Classes loaded with >> application class loader first". >> >> Any ideas? Every hint appreciated and thanks in advance. >> >> Regards >> Christian Kölle >> >> > >
<<winmail.dat>>
