Posted By:
Anonymous
Posted On:
Monday, July 11, 2011 10:36 AM
Hi, I have recently upgraded to the latest Eclipse (Indigo) Java EE for web developers, from Eclipse Ganymede. However after installing Indigo, it appears that my existing webapp project fails to start on tomcat (running within eclipse). On starting tomcat it keeps erroring with class not found exceptions. Even though the classes are actually in the project build path. In an attempt to get around this, I tried to add the relevant "jars" into the "classpath/User Entries" of the tomcat launch configuration, even though they were already in my project build path. This would result in it getting past a previous error, but to then error with another classNotFoundExceptio
More>>
Hi,
I have recently upgraded to the latest Eclipse (Indigo) Java EE for web developers, from Eclipse Ganymede.
However after installing Indigo, it appears that my existing webapp project fails to start on tomcat (running within eclipse).
On starting tomcat it keeps erroring with class not found exceptions. Even though the classes are actually in the project build path. In an attempt to get around this, I tried to add the relevant "jars" into the "classpath/User Entries" of the tomcat launch configuration, even though they were already in my project build path.
This would result in it getting past a previous error, but to then error with another classNotFoundException, where I would add the relevant "jar" file again to the "User Entries", to get another classNotFoundException, and so on. Where I found that I was adding pretty much all the jars that are in my project build path (including servlet-api.jar and el.jar which are a part of the tomcat libraries as standard).
I am therefore convinced that tomcat on Eclipse is not looking in the right place for it's libraries. This was all working fine on a previous install of Eclipse (Ganymede).
Can anyone help me with this?
Thanks,
Glen
<<Less
