what's the big secret to debug for external server??

[Elhanan]

hi..

been trying every combination i can think of to debug on tomcat.

i have a webapp (wtp web app with google sdk) which depends on several java projects (some are jpa, some are other java projects with gwt) . problem is i keep getting various ClassNotFoundException or No Persistence Provider found exceptions when i bring up the application, it seems that i launch the application not the regular servlet way it doesn't have any access to the server classpath, i tried updating everything i can think of in the class path of the server launcher (including the projects i'm wokring on) but it seems sketchy, there has to be a better way.

i need tomcat for things like injection of resources like persistence units. as jetty won't provide them. (this is tomcat 6). 

should i even touch the server launcher classpath? 

what am i missing? 

[divStar]

Hi there. I actually had pretty much the same issues you're
experiencing. The only thing I can recommend to you is to try and
setup a rather basic project first and get it to work first.
My application is certainly more simple than yours, but I first set up
a regular web application to run and debug with tomcat and eclipse
(using wtp). There is plenty of literature on how to accomplish that.
Then when you got it to work, you add the database functionality and
last but not least the GWT related stuff.

There is really no magic about getting GWT to work on tomcat. When I
get home I will tell you the configuration settings I use. However I
am not using JPA nor EJB or the likes. I use servlets, JNDI lookup for
database connection and GWT.

Maybe this suggestion will already help you, because that's also what
helped Me. Now I can debug both My server and client sides straight
from eclipse On tomcat.

On Jetty however you actually can define a custom server launching
class, which allows additional xml configuration files to be
interpreted. You then would use that custom class to launch the
server. However I'd certainly prefer a working tomcat configuration
over the built-in Jetty one, because that's most-likely what you will
be running your application later on in production mode.

I will report my configuration when I get home.

Cheers!