[Seaside] Re: Glorp Sessions in ajax requests

Bart Veenstra bart.veenstra at gmail.com
Fri Sep 10 18:27:07 UTC 2010

And another thing is bugging me during the development.

How do I cope with glorp objects that are stored in a WAComponent, like the
current user, and use that when I update other glorp objects. It keeps
pushing me a DuplicatePrimaryKeyException because the object is not in the
current session. I need to reinstantiate the current user in the session
with a database lookup, before I can use it again...

So, How to properly mix glorp objects coming from different sessions? This
could be resolved, if the glorpFilter stays put in the WASession in each
ajax request.

Should I drop the glorp filter and put the glorp session in the WASession
properties instance variable?



2010/9/10 Bart Veenstra <bart.veenstra at gmail.com>

> Hi,
> I am working on an Ajax heavy application with Glorp as my mapping
> framework. I use the Glorp filter to assign a glorpSession to my database
> objects. This works pretty well, but it seems that for each request within
> the same session (like an jQuery ajax callback) a new GlorpSession is
> created.
> When removing all sessions using WAAdmin clearAll, the Glorp Sessions still
> remain in the memory, (Checked with GlorpSession allInstances).
> Should I worry about this? And how do I get rid of the GlorpSessions?
> I tried GlorpSession allInstances do: [:each | each become:nil ] but the
> object is immutable...
> Using VW 77 with the latest seaside from the public repository.
> Regards,
> Bart Veenstra
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20100910/ced39637/attachment.htm

More information about the seaside mailing list