One other curious aspect of this is that we don't get that error if we change the state_saving_method from client to server. However, we want to keep our state_saving_method as client to allow for pop-up windows and back-button functionality.
- Brendan -----Original Message----- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Monday, February 27, 2006 11:29 AM To: MyFaces Discussion Subject: Re: Running MyFaces on WebSphere 6.0 "com.sun.faces.saveStateFieldMarker" definitely indicates it's finding the JSF RI in your classpath. I don't have any direct experience with WebSphere, though. On 2/27/06, CONNER, BRENDAN (SBCSI) <[EMAIL PROTECTED]> wrote: > Question: Is anyone out there using MyFaces with WebSphere 6.0? Our > application works fine with WebSphere 5.1.1.3, but, for some reason, it > does not work on WebSphere 6.0. After googling around, I found that > WebSphere 6.0 ships with an integrated version of JSF, and I thought > that maybe we were encountering a conflict with their integrated > version, but then I also read that WebSphere 5.1.1 also has integrated > JSF, so maybe that's not the problem, since our application works fine > with that version of WebSphere. > > We're getting the following message on our screen the first time we try > to execute an action: com.sun.faces.saveStateFieldMarker > > Unfortunately, we don't seem to see anything else in the logs that can > help us. > > I seem to recall that we got that message on our screen in the past when > not all of our beans were declared as serializable, but we did another > check, and everything does seem to be serializable. > > Any thoughts? > > - Brendan >
