RE: [picocontainer-dev] RE: [picocontainer-scm] [5426] java/2.x/trunk/web/web-core/src/java/org/picocontainer/web: make stateless not hit session.setAttribute()

Actually Paul,

 

This is EXACTLY an issue in Tomcat.   Its why on NanoWAR branch, I made the
Session container optional (I never used it personally because of this).

 

I had made a couple of peeks at the Pico-web-2 code to see if I could easily see
how to work around it, but no dice --but when I saw the patch, I understood the
result of what you were working on and thus the "WOO HOO!"

 

So, sorry Paul, you're still going to get lots of appreciation from me for this
current branch of work...   and you can't stop me :)  

 

 
-Mike

 

 

From: Paul Hammant [mailto:[email protected]] 
Sent: Thursday, June 11, 2009 9:36 AM
To: dev-qxt/[email protected]
Subject: Re: [picocontainer-dev] RE: [picocontainer-scm] [5426]
java/2.x/trunk/web/web-core/src/java/org/picocontainer/web: make stateless not
hit session.setAttribute()

 

Not so much cool Mike, but necessary for AppEngine deployment.

 

There's a bug that remains that's exposed by AppEngine.  Session components that
dep on App Components that are serialized to the session at the end of a
request, will also serialize the app instance.  This is not a bug for non
session-serializing servlet containers (like Jetty/Tomcat standalone).

 

We're going to have to implement Guice's provider style injector (Provider
Injection as opposed to Dependency Injection) as well as an (alternate) ASM
mechanism to subvert the app scoped comps from being serialized (transient will
suffice) as well reconstitute the app-comp connections on de-serialization.

 

Regards,

 

- Paul

 

On Jun 9, 2009, at 5:19 PM, Michael Rimov wrote:





Woo hoo! :)

 

Very cool Paul!

 
-Mike