The remaining problem is that session data does not seem to be preserved from page to page. That is, if on a simple .jsp I have something like:
myPackage.myClass ml = new myPackage.myClass(); session.putValue("ml",ml);
Then do a form-based submit to a second jsp which contains:
<jsp:useBean id="ml" scope="session" type="myPackage.myClass" />
Then I get an error saying
javax.servlet.ServletException: bean ml not found within scope
If I try to manually extract the ml attribute from the session in the second .jsp I find that it is not set.
I have done some Googling about this problem but I don't see anything that would help -- the hits were largely about clustering. In my case I do not have access to the Tomcat config (server.xml) and have to live with how things are configured at the ISP.
Has anyone else experienced this problem? If so, is there a solution?
To test this I have also installed Tomcat 5.0.24 on my laptop (Win2K) where it exhibits the same problem and on a Linux (Fedora Core 1) machine where it does not exhibit this problem. Both are running on Sun's 1.4 JDK with the stock (as shipped) server.xml.
The ISP which has been very responsive in the past is being not all that helpful and they had the active component of the sites down for the best part of a week!
Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]