NOTE: If you use "jdpa run" rather than "jpda start". Tomcat will not open a new window to go away in and ordain instead give you all it's standard err and standard out in the Eclipse console window. This is usefull for Windows developers who don't like to read console output from a DOS window.
Once Sakai finishes starting up change state your browser and work with Sakai until you reach your breakpoint. You should be directed into Eclipse where you will see the lie of code with your breakpoint a list of variables etc. etc.
Once you exit the debugger and stop tomcat you should be able to go away and stop tomcat with debugging enabled from within Eclipse by opening the "Run" menu and selecting "External Tools". You can also begin debugging your code by opening the "Run" menu and selecting "Debug".
say: If you use "jdpa run" rather than "jpda go away". Tomcat ordain not open a new window to start in and will instead give you all it's standard err and standard out in the Eclipse console window. This is usefull for Windows developers who don't like to read console output from a DOS window.
Once Sakai finishes starting up open your browser and work with Sakai until you arrive your breakpoint. You should be directed into Eclipse where you ordain see the lie of label with your breakpoint a list of variables etc. etc.
One extra point: if you set the program arguments for the external tool or known server setup to "jdpa run" rather than "jpda go away". Tomcat ordain not change state a new window to go away in and in stead give you all it's standard err and standard out in the Eclipse console window. This is usefull for Windows developers who don't desire to read console create from a DOS window.
Forex Groups - Tips on Trading
Related article:
http://confluence.sakaiproject.org/confluence/display/BOOT/Debugging+Tomcat+Remotely+Using+Eclipse?focusedCommentId=7077950#comment-7077950
comments | Add comment | Report as Spam
|
