<div>Have a look at the Seaside-Glorp package. It should be in the public repository (and comes prepackaged with WebVelocity) provides for Seaside session-glorp session "persistence", accessor pooling, etc. The package comments say it is based on work by Ramon Leon so you might check his blog to see if you can glean some hints <a href="http://onsmalltalk.com/making-a-connection-pool-for-glorp-in-seaside">there</a><br>
</div>
<div>John<br></div>
<div class="gmail_quote">On Fri, Sep 10, 2010 at 2:27 PM, Bart Veenstra <span dir="ltr"><<a href="mailto:bart.veenstra@gmail.com">bart.veenstra@gmail.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">And another thing is bugging me during the development.
<div><br></div>
<div>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...</div>
<div><br></div>
<div>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. </div>
<div><br></div>
<div>Should I drop the glorp filter and put the glorp session in the WASession properties instance variable?</div>
<div><br></div>
<div>Regards,</div>
<div><br></div>
<div>Bart</div>
<div><br></div>
<div><br><br>
<div class="gmail_quote">2010/9/10 Bart Veenstra <span dir="ltr"><<a href="mailto:bart.veenstra@gmail.com" target="_blank">bart.veenstra@gmail.com</a>></span><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">Hi,
<div><br></div>
<div>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. </div>
<div><br></div>
<div>When removing all sessions using WAAdmin clearAll, the Glorp Sessions still remain in the memory, (Checked with GlorpSession allInstances).</div>
<div><br></div>
<div>Should I worry about this? And how do I get rid of the GlorpSessions? </div>
<div><br></div>
<div>I tried GlorpSession allInstances do: [:each | each become:nil ] but the object is immutable...</div>
<div><br></div>
<div>Using VW 77 with the latest seaside from the public repository.</div>
<div><br></div>
<div>Regards,</div>
<div><br></div><font color="#888888">
<div>Bart Veenstra</div></font></blockquote></div><br></div><br>_______________________________________________<br>seaside mailing list<br><a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br><br></blockquote></div><br><br clear="all"><br>-- <br>
<a href="http://john-mckeon.us/" target="_blank">http://john-mckeon.us</a><br>