Reputation: 1637
This question has been asked many times, but I have yet to see anyone discuss it regarding debugging GWT with Eclipse.
I started getting this error after upgrading from GWT 2.6.0 to 2.6.1 and now 2.7.0.
I can add tomcat-juhli.jar, which is now found in the bin directory, to the classpath and make the error go away, but then I may get a variety of other errors. (Jasper, Permissions, JSTL).
After many hours of moving jars from the classpath into the WEB-INF/lib folder and back again, I no longer can get the eclipse debug perspective to open.
Upvotes: 0
Views: 414
Reputation: 4602
The tomcat-juli file is required by Tomcat to do its logging, usually not required by either eclipse or your app.
the correct location in that case is the tomcat lib folder, next to jakarta etc.
there should also be a juli adapter jar.
not sure if this is really related to gwt.
Update: Check this page regarding logging in Tomcat: http://tomcat.apache.org/tomcat-7.0-doc/logging.html
If I understand your problem correctly, your chapter is the log4j chapter. Esp. the part with the juli jars. You need to fix the classpath for the tomcat adapter in eclipse to fix it.
Upvotes: 0
Reputation: 41099
All jars that you use in your server code must be both on the build path and in the WEB-INF/lib folder.
If you get other errors when you do that, you have to deal with those errors.
Upvotes: 1