MyFaces is great at beginning, but now I don't think goto right direction, why I say this, because I am using myfaces, I don't want change my code and give up it change to IBM, Oracle or WebLogic something. MyFaces can extends JSF, but have to follow JSF standards. If you go too far, we will be scare to follow it.
On 9/2/05, CONNER, BRENDAN (SBCSI) <[EMAIL PROTECTED]> wrote:
That's a good point about redirect; we don't do that. ;-)
Regarding the "browser back" button, I believe that that works OK if you
set "client-side" state saving, rather than "server-side." Have you
tried that? We have to do "client-side" state saving anyway, because
otherwise JSF gets confused when we return from our pop-up windows.
- Brendan
-----Original Message-----
From: Mario Ivankovits [mailto: [EMAIL PROTECTED]]
Sent: Friday, September 02, 2005 12:43 AM
To: MyFaces Discussion
Subject: Re: more on architecture really confused on something
(shocker:)
CONNER, BRENDAN (SBCSI) wrote:
> <t:saveState>
The bad thing with saveState is that it wont work if one use <redirect
in its navigation rule.
I already tried to address this and it worked partly.
Wouldnt it be nice if (on redirect) myfaces will collect all
saveState-Beans and put them in session scope and after redirect to put
them back?
The thing I didnt managed to work nicley is "browser back".
I have to maintain a LRU or simmilar and once the user pressed back e.g.
20 times I lost all saveState beans.
---
Mario
