So now you've got Tomcat remote debuggable right? Now you want to get your favorite IDE, Netbeans, ready for action right? So lets not waste time embelishing. Netbeans/Forte makes this really easy.
We're going to assume you have a project set up with all of the fixings and have some idea of what you're doing in this respect. If not then thats really outside the scope of this topic and more in the scope of you needing to go to eclipse.org and read up on how to use your ide, and maybe practice a little bit before you come back to this. We're also going to assume you have some idea of what a debugger is and how to use one. If not, then play around debugging a project locally first by going here and following the instructions.
Make sure tomcat is started and that your app is deployed and the sources, etc are all defined as resources in your app. If you have a servlet or something, set a breakpoint where its sure to hit on the next request. Go to Debug->Start Session->Attach. A dialog should pop up and use following options:
Default Debugger:JPDA
Socket Attach
Host:the ip address of the host your Tomcat installation is running on
(127.0.0.1 if it is your machine)
Port:The port of your tomcat debugging interface, which should be 8000
if you've followed the instructions correctly
Then press ok and you should have a debugging connection very similar to local debugging. (you can set breakpoints inspect variables etc.)
Netbeans/Forte however has a second option, you can debug JSP files and servlets locally. Nothing really exciting happens there, an integrated Tomcat server is started and a remote connection is opened. Note however that the integrated Netbeans Tomcat usually is a few versions behind the current Jakarta/Apache version.
|
|
|
| ||||
|
About Jakarta
Download Get Involved SubProjects
Project Management |
|
|||
|
| ||||
|
Copyright © 1999-2002, Apache Software Foundation
| ||||