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 >
