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">bart.veenstra@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">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>