Did we now loose the lazy session initialization/creation or not?
johan On 2/2/07, Al Maw <[EMAIL PROTECTED]> wrote:
Hi, There's code in SecondLevelCacheSessionStore.SecondLevelCachePageMap which checks if a page is stateless when it is put() and doesn't bother calling dirty() if so. However, dirty() is always called from various constructors (for example the Session constructor calls setLocale() which calls dirty()). This doesn't seem right. Should stateless pages never have dirty() sessions? If that's the case, should we fix these and have a call to Session.dirty() trigger a bind()? I've just fixed Session.bind() so it actually persists the session, which it didn't before (this normally doesn't matter, but causes oddness if you redirect from a stateless page to a stateful one, expecting bind() on the stateless page to propagate the session to the stateful redirect page like the javadoc says it will). Thoughts welcome. Al
