Thanks Mike. Yes, I remember that jsf 1.2 provides a windowId. Do you have an idea when a myFaces implementation (a release) of the 1.2 spec will be available?
Client Side state saving is a big performance downside and not useable for me. Another question to jsf 1.1: Would I face problems if both screens use their own backing beans and the backing beans are able to update each other? The second page should just fetch data for detail display and should be refreshed from the master window via javaScript. What would you advise me to do? Switch to Sun RI 1.2 or try to build a prototype with MyFaces 1.1.X and server side state saving. Thanks for any help and comments Michael -----Original Message----- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 10. August 2006 16:20 To: MyFaces Discussion Subject: Re: 2 screen mode On 8/10/06, Michael Heinen <[EMAIL PROTECTED]> wrote: > I just want to know whether it is generally possible to work with 2 screens > simultaneously in a JSF application. For JSF 1.2, this is generally true (although I don't know the details). For JSF 1.1, this is generally not true. > The 2 screen mode should be optional depending on user preferences. > State saving mode should be server side. The only way JSF 1.1 will work is with client-side state saving. > Can I handle this with JSF or are there any special pitfalls? For 1.1, you need to use client-side state saving and avoid having any session-scoped data.
