RE: Try a different approach - What's wrong with catalina.session???

2001-12-14 Thread Cox, Charlie
Craig said... This kind of problem indicates that your Tomcat installation is somehow corrupted. If it were really a bug, it would be happening to everyone, not just to you. I suggest that you do the following: * Make sure you do not have anything in $JAVA_HOME/jre/lib/ext

RE: Try a different approach - What's wrong with catalina.session ???

2001-12-14 Thread Jim Cheesman
Actually you should use the CLASSPATH to compile code and not put things into $JAVA_HOME/jre/lib/ext. When you put things into this directory, the bootstrapper loads the classes(not tomcat) and tomcat cannot load newer versions of those libraries. Unless of course that's the behaviour you

Try a different approach - What's wrong with catalina.session???

2001-12-13 Thread Richard S. Huntrods
Greetings! Let's try this again. From the error message below, it would appear that there is something WRONG with org.apache.catalina.session.StandardSession. Note from the error that we get a java.lang.NoSuchMethodError - the method does not exist. After reading the Catalina Javadocs, it

Re: Try a different approach - What's wrong with catalina.session???

2001-12-13 Thread Mika Goeckel
Subject: Try a different approach - What's wrong with catalina.session??? Greetings! Let's try this again. From the error message below, it would appear that there is something WRONG with org.apache.catalina.session.StandardSession. Note from the error that we get

Re: Try a different approach - What's wrong with catalina.session???

2001-12-13 Thread Richard S. Huntrods
More stuff Here is the source code to a servlet that RUNS under Tomcat 4.0 but does NOT RUN under Tomcat 4.0.1. I can email (upone request) a zip file containing the full directory structure (with class file) that can be unzipped an placed directly under webapps. Put it in Tomcat 4.0 and

Re: Try a different approach - What's wrong with catalina.session???

2001-12-13 Thread Mika Goeckel
, 2001 6:05 PM Subject: Try a different approach - What's wrong with catalina.session??? Greetings! Let's try this again. From the error message below, it would appear that there is something WRONG with org.apache.catalina.session.StandardSession. Note from the error that we get

Re: Try a different approach - What's wrong with catalina.session???

2001-12-13 Thread Craig R. McClanahan
On Thu, 13 Dec 2001, Richard S. Huntrods wrote: Date: Thu, 13 Dec 2001 10:05:31 -0700 From: Richard S. Huntrods [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: Try a different approach - What's wrong with catalina.session

Re: Try a different approach - What's wrong with catalina.session??

2001-12-13 Thread Richard S. Huntrods
Hmmm the difference between these two constructors is, that the one which takes a StandardSession upcasts it to HttpSession before assigning it to it's session attribute, this should not cause this problem, as StandardSession does implement all HttpSession methods (otherwise the compiler

Re: Try a different approach - What's wrong with catalina.session???

2001-12-13 Thread Richard S. Huntrods
Greetings! Craig said... This kind of problem indicates that your Tomcat installation is somehow corrupted. If it were really a bug, it would be happening to everyone, not just to you. I suggest that you do the following: * Make sure you do not have anything in $JAVA_HOME/jre/lib/ext

Re: Try a different approach - What's wrong with catalina.session???

2001-12-13 Thread Mika Goeckel
: Friday, December 14, 2001 12:40 AM Subject: Re: Try a different approach - What's wrong with catalina.session??? Greetings! Craig said... This kind of problem indicates that your Tomcat installation is somehow corrupted. If it were really a bug, it would be happening to everyone, not just

Re: Try a different approach - What's wrong with catalina.session???

2001-12-13 Thread Richard S. Huntrods
Thanks, Mika. I tried this servlet in Tomcat 4.0.1: http://localhost:8080/examples/servlet/SessionExample and it works in 4.0.1 UNTIL I press the URL encoded link. Then I get the exact same error message as I've been reporting. Also, typing in the Name of Session... and pressing Submit Query