tag:blogger.com,1999:blog-4699667848216680716.post433069077084869031..comments2010-11-24T09:53:45.034+02:00Yaniv Kesslernoreply@blogger.comBlogger5125tag:blogger.com,1999:blog-4699667848216680716.post-48777711548648423712010-11-24T09:53:45.034+02:002010-11-24T09:53:45.034+02:00In this particular scenario the guice provider is simply a wrapper for the PersistenceManagerFactory, there is no telling whats going on inside there, its possible one is created for each request or not. The filter code doesn&#39;t do that, anyways.<br /><br />As for an &quot;off the shelf&quot; product, try the new <a href="http://code.google.com/p/google-guice/wiki/GuicePersist" rel="nofollow">Guice 3.0 persist module</a>. Guice 3.0 is still in an &quot;unreleased&quot; state thought.<br /><br />If you work on app engine, I suggest you take a look at other alternatives to JDO, like objectify.Yaniv Kesslerhttp://www.blogger.com/profile/04361523048975960236noreply@blogger.comtag:blogger.com,1999:blog-4699667848216680716.post-44562507970584567152010-11-24T01:38:09.778+02:002010-11-24T01:38:09.778+02:00Would using OpenPersistenceManagerInView be as simple as changing from Request to Session scope?Sir Christopherhttp://www.blogger.com/profile/03600139814092755398noreply@blogger.comtag:blogger.com,1999:blog-4699667848216680716.post-33100836537890053512010-11-24T00:58:08.590+02:002010-11-24T00:58:08.590+02:00Is that using an open PersistenceManager per session or does it create a new one for each individual request?<br /><br />Opening up a new one for each request means that there is no caching of objects in the L1 cache between requests - which can reduce performance if each session has lots of objects.<br /><br />I have a home grown filter which does keep the PM open for the life of a session and the performance is excellent. I&#39;m just looking around for third party &#39;off the shelf&#39; alternatives.Sir Christopherhttp://www.blogger.com/profile/03600139814092755398noreply@blogger.comtag:blogger.com,1999:blog-4699667848216680716.post-38909760408158434522010-08-31T01:18:20.220+03:002010-08-31T01:18:20.220+03:00Sessions expire after a timeout. If you wish to expire a session deliberately, you should call <a href="http://download.oracle.com/docs/cd/E17802_01/products/products/servlet/2.2/javadoc/javax/servlet/http/HttpSession.html#invalidate()" rel="nofollow">HttpSession.invalidate()</a> in your logout code. <br /><br />Also there are some restrictions on sessions in AppEngine, for additional details, please read <a href="http://code.google.com/appengine/docs/java/config/appconfig.html#Enabling_Sessions" rel="nofollow">this section</a> in AppEngine docsYaniv Kesslerhttp://www.blogger.com/profile/04361523048975960236noreply@blogger.comtag:blogger.com,1999:blog-4699667848216680716.post-86108179362979060142010-08-30T18:14:14.001+03:002010-08-30T18:14:14.001+03:00Great article!<br />I had a problem with session scoped objects, which Guice (or Appengine) didn&#39;t wanted to store in a session. It happened only with objects, which were injected in a class together with UserService. And injection of session scoped provider for User instead of UserService really helped me. <br /><br />But another problem occured. After user has logged out using UserService logout URL, injected User object still contains user info. It happens because User is now a session scoped object and guice doesn&#39;t inject a new User object, which suppose to be null. Session doesn&#39;t expire after user has logged out. Is there any workaround for that?Dmitri Semirenkohttp://www.blogger.com/profile/15057657468102061770noreply@blogger.com