One
other thing we were thinking was using the JSF implementation supplied by WAS
6.0, along-side the MyFaces Tomahawk components. However, WAS 6.0 only
support JSF 1.0 "out of the box." :( I assume that wouldn't work with the
Tomahawk components, correct?
-
Brendan
-----Original Message-----
From: Gary VanMatre [mailto:[EMAIL PROTECTED]
Sent: Monday, February 27, 2006 1:20 PM
To: MyFaces Discussion
Subject: Re: Running MyFaces on WebSphere 6.0
From: Gary VanMatre [mailto:[EMAIL PROTECTED]
Sent: Monday, February 27, 2006 1:20 PM
To: MyFaces Discussion
Subject: Re: Running MyFaces on WebSphere 6.0
The classpath probably wouldn't effect the auto loading of the faces-config's. I think this is ordered by the name of the jar. I wonder if they could all live together if you renamed the myfaces impl jar to zz-myfaces.jar so it's registered last?The safest bet would be to just remove the jars. I'm not sure how that would effect their component library. The "inputRichText" is a really sweet control.Gary-------------- Original message --------------
From: "Cagatay Civici" <[EMAIL PROTECTED]>
Hi,
Hi,
We are using WAS 6 and had the same problem in the past, I remember deleting jars like ws-jsf solved the problem.
Cagatay,
On 2/27/06, Gary VanMatre <[EMAIL PROTECTED]> wrote:In WAS 6, the JSF runtime is packaged in with the server. In the WAS_INSTALL_ROOT\lib you will find jsf-api.jar and ws-jsf.jar.It looks like the ws-jsf.jar is a mix of the RI and the IBM JSF runtime/extensions. I belive that the jsf-ibm.jar only contains there custom component layer.I would try using the "Order and Export" tab on the "Java Build Path" dialog to move the myfaces jars up in the classpath ordering above "WebSphere v6.0 Runtime".Gary-------------- Original message --------------
From: "CONNER, BRENDAN (SBCSI)" < [EMAIL PROTECTED]>
> 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
& gt;
>
> "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) 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
> > wi th 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.
> & gt;
> > 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
> >
