Until your in a new request there can be state outside of the session that is
still seen in the current request.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910469#3910469
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply
In fact,
I dumped the XDoclet and written the jboss-web manually and inserted the
flushOnSessionInvalidation flag. It works fine.
The initial reason I moved to the 3.2.7 was that I read somewhere that maybe
3.2.7 solved a problem scheduling services not finding the scheduled class
after a rede
