I'm not doing the work, but I think this is a blocker issue for anyone using server-side state saving. Fortunately, that's not the case for me. I don't think telling people to switch to client-side state saving is realistic, nor is expecting them to "guess" a number big enough to avoid the bug -- and what kind of memory issues are going to result in having basically unlimited view retention?
On 5/3/06, Dennis Byrne <[EMAIL PROTECTED]> wrote:
Well, I am just as frustrated as anyone else w/ this release, but to me this is asking a lot from users. I am not going to take back my +1, but if anyone does get the urge to compile a new 1.1.3 or a 1.1.4, I can retest it Friday night at the latest. Dennis Byrne >-----Original Message----- >From: Sean Schofield [mailto:[EMAIL PROTECTED] >Sent: Wednesday, May 3, 2006 04:20 PM >To: 'MyFaces Development' >Subject: Re: [VOTE] Release MyFaces Core 1.1.3 > >> Pssst ... what's the work around? > >See the JIRA issue. Use client side state saving or "[change] >org.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION parameter to a large >(500) value" > >> Dennis Byrne > >Sean >
