I just posted another revison 2 of the plugin (Resinplugin-2.0.5_2). In the ealier versions, I tried to clear the Resin cache when a new web application is deployed. This was causing me some mysterious problems with Cactus and perhaps this is also affecting maintaining the JSESSIONID.
Anyhow with the Rev 2 of the plugin, I am developing a web application that tracks session holding. I am not seeing a problem maintaining the session. I am using Tapestry for my web UI which may be introducing a difference.
Please let me know more details if Version 2 of the plugin does not fix your problems.
I did use release 2 of your plugin when I was trying Resin with JBoss.
I am happy to investigate if you send me a sample or more details of what is happening.
Strange, but true. I did nothing and application works ok. Now I'm unable to get previous symptoms which was:
- login to application - login servlet checks user passwd and name , if corect then creates user object and add it to session.
- Next request - servlet checks if there is user object in session if not - sends redirect to login JSP.
After successful login everey next request redirected to login JSP - there were no user object in session. But now it works fine, so sorry for bothering you.
I am glad to hear that it is working but troubled that you ever had a problem.
Please do not hesitate to send me error reports in the future. We are planning to use this plugin here at work and I want to hear about any issues (the sooner the better).
Best of luck...