AW: ServletContextListener and HttpSessionActivationListener

2004-09-08 Thread Michael Sudkamp
 
 But it's not explicit enough, and for that you should ask the Servlet
 Expert Group (you can find a link for that on the JSR154 home page).

Yes, I sent them a comment.

Best regards

Michael


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



AW: ServletContextListener and HttpSessionActivationListener

2004-09-06 Thread Michael Sudkamp
Yoav, thanks for your understanding. I've just read the 2.4 spec regarding this and 
cannot any big clarifications. Can you point me to the chapter where you found it.

I find this issue logged as bug #30344. It's exactly what I mean. But IMO this not 
described in the spec, neither 2.3 nor 2.4.

Michael

 -Ursprungliche Nachricht-
 Von: Shapira, Yoav [mailto:[EMAIL PROTECTED]
 Gesendet: Freitag, 3. September 2004 15:14
 An: Tomcat Users List
 Betreff: RE: ServletContextListener and HttpSessionActivationListener
 
 
 
 Hi,
 I think this was clarified in Spec v2.4 to match Michael's 
 opinion, and
 there's an open issue for Tomcat 5 for this already. 
 
 Yoav Shapira
 Millennium Research Informatics
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



AW: ServletContextListener and HttpSessionActivationListener

2004-09-03 Thread Michael Sudkamp
 
 We can talk opinions all we want -- if it's a grey area in 
 the spec, and
 your container (Tomcat, in this case) does things a certain way then
 that's how it goes.

But if people would agree with me we could try to get a next spec more specific. 
That's my intention.

 
 Have you at least tried the 5.x series and/or checked Bugzilla?
 

Yes, Tomcat 5.0.24 does the same

Michael


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



AW: ServletContextListener and HttpSessionActivationListener

2004-09-02 Thread Michael Sudkamp
I asked for your opinion because I wanted to know if anyone can imagine for what 
purpose the sessionDidActivate event is useful if not for reinitilization work after 
the session has become deserialized.

It it is for that purpose, then IMO there must be fully initialized context at that 
point. I mean I must have had the chance to set up my own context attributes prior to 
this point.

Michael


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]