Hi Nico. Is isn't really serialization per se, its more that to stuff it in a http session it is expected to be serializable.
In my case, I would simply like to keep the Session around for a little while in a servlet container. On 9/8/06, Nicolas <[EMAIL PROTECTED]> wrote:
Hi, Why is Session not serializable? Is there a specific reason we didn't implement Serializable? It depends: what is the expected behavior of the user (read, write, read/write,...)? BR Nico my blog! http://www.deviant-abstraction.net !! On 9/8/06, Michael Neale <[EMAIL PROTECTED]> wrote: > > Hi All. > > This may (hopefully) have an obvious answer, but I was planning on putting > a > JCR Session in a server side (HTTP)session - for the duration of the users > interaction with the app. > > a) is this a good/bad idea? (I don't have to worry about a massive number > of > concurrent users) > b) Session is not serializable - so this may cause some issues with some > containers (I believe I can work around that anyway). > > Thoughts? > > Michael. > >
