got it http://tapestry.apache.org/tapestry4/tapestry/apidocs/org/apache/tapestry/SessionStoreOptimized.html
Still interested in a mechanism to drop actual entity references in favour of a primary ky, although I can probably just do so in the method provided by the interface above, since I bet it gets called only at the end of a request. Still, there's probably a less kludgy way to do it. --sam On 7/15/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
I want to store a mutable object in the session. I seem to recall that this will break in a clustered environment, since changes to the object won't be detected unless the reference itself is modified to a new reference. Is there some interface I can have my state object implement which will allow it to notify the session cache when the object has been modified? Also, I want to throw entire domain entities into the object, but only actually store primary keys between requests, since some of those domain entites may not be accessed very frequently.. I'm sure I can implement a servlet filter to call a method on the object at the end of every request, but perhaps there is a more tapestry-centric way to accomplish this? Perhaps to use a data squeezer on the members of the object being placed in the session? thanks --sam
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
