RE: [picocontainer-dev] NanoWAR and session madness in Tomcat 5

> We already know that it works with Tomcat in at least one case; using the
> groovy pico syntax rather than the builder syntax (maybe not with the
> context container, because I don't store a component in the context
> container,

Correct, that's probably why it works for you.

> but with the request container, which we also know fails
> serialization when using the builder syntax, so I presume it's the same
> problem being discussed).  And that's with no changes whatsoever to
> ServletContextListener.  

Right, but for me the non-builder script actually failed on my system
because of a race condition.  

Once I got the race condition fixed, then both behaved identically for me.  

I think actually what was happening was that the SessionContainer wasn't
getting properly hooked into the app container under the "straight syntax",
which is why you didn't get the serialization errors.  

But you actually SHOULD have gotten the serialization error even under
straight syntax. (No, I'm not making it up! ;) )

> If modifying ServletContextListener makes it all
> work with all syntaxes, that would be great.  However, the fact that it
> works with the pico syntax with no changes means that the change would
> simply be masking a more fundamental issue that should probably be solved
> first.

My guess is that I think it only superficially worked for you.   (My bet was
that because you never actually used the App container, your dependency
checks never failed.)

Does this clarify??

	
-Mike