Originally posted by Michael Ernest:
Moving this to the Servlets forum.
All of the necessary jars are *definitely* still in the /WEB-INF/lib directory and they always have been. Nothing *at all* has changed!
Originally posted by Paul Sturrock:
No need to apologise.
Where in Hibernate 3.0.5 is HibernateUtil? Its not in hibernate3.jar...
Originally posted by Rick O'Shay:
>> Why did this get moved here?
Somebody made an error in judgement although this is obviously not a servlet problem so who knows why.
Anyway, how CLASSPATH can change is not a relevant question. Why? Because you should never use it. It's a mistake that was there in the beginning and it will be there forever. Use -classpath (or -cp for short) in javac or java commands.
Originally posted by Mark Spritzler:
Well, I can see why it was moved here is because your Servlet is the one that is throwing the exception, and the whole thing with how to get jar files in the classpath for servlet containers is a bit different than just plain ol Java.
OK, with that said. NoClassDefFoundError is a classpath related issue, but mostly when the version of the class that is in the library is out of date, and doesn't match what is actually trying to be called.
Can you rebuild your jar file and redepploy and see what happens?
Originally posted by Ernest Friedman-Hill:
OK, now, the lesson learned is: do you remember when you changed that file? Was it the last thing you changed before the last test? Probably not; the change probably didn't take effect until you bounced the server. Still, did you examine that file? Remember, you started this discussion saying that absolutely nothing had changed, but something really had: this file. Next time, you have to remember to do a thorough test after making a change like this -- or barring that, when something breaks, be sure to check everything you changed, even if it couldn't possibly be wrong.