Sysdeo Tomcat Launcher Plugin. Plugin features Starting and stopping Tomcat 4.x, 5.x, 6.x, 7.x Registering Tomcat process to Eclipse debugger Creating a WAR project (wizard can update server.xml file) Adding Java Projects to Tomcat classpath Setting Tomcat JVM parameters, classpath and bootclasspath Exporting a Tomcat project to a WAR File Capability to use a custom Tomcat classloader to load classes in several java projects at the same classloader level than classes in a Tomcat project, see readmeDevLoader.html (Thanks Martin Kahr) Support and contributions Contact email@example.com Download This plugin is free and open-source Warning : installing plugins on Windows 7 can fail without error message, see this article for more information and workarounds : 'Eclipse Plugin Installation and Windows User Access Control' Tomcat 4.x patch for JSP debugging (Thanks to Johan Compagner) Installation This plugin does not contain Tomcat.
Documentation and tutorials Official documation (french) : No catalina.bat in TOMCAT5.5 need to remote debug. MyEclipse Remote Debugging Tutorial. MyEclipse provides a special debug launch configuration, MyEclipse Externally Launched Server, that is designed to attach to remote application servers and support full application debugging.
To create a launch configuration for your external server, click on the Debug Launch Configuration toolbar button, as shown in Figure 4. Figure 4 - Opening the list of Debug Configurations Selecting "Debug... " will open the Debug Launch Configuration Management dialog, as shown in Figure 5. From this dialog, select the MyEclipse configuration then the New button to create a debug launch configuration that can be configured to attach to your application server. Figure 5 - Creating a New MyEclipse Remote Debug Configuration Figure 6 shows an example remote debugging configuration for JBoss 4, but the settings would be similar for any server. Figure 6 - Example JBoss Configuration Figure 7 - Configuring the Source Lookup Path Figure 8 - External Server Attached to Debugger. Debugging a servlet with tomcat and Eclipse tutorial - WikiJava, Eclipse, Tomcat, Debug, Servlet. From WikiJava The author suggests: buy this book This tutorial will guide you through the process setting up the debugging of a simple Servlet under Eclipse using Tomcat.
There are many plugins for Eclipse to help you configuring this, they all basically try to automatize the process explained in this tutorial. It's always good to know what's going on under the hood. note: this tutorial doesn't explain how to do the actual debugging, for information about this see the how to debug tutorial The article The configuration process for debugging a Java servlet may appear scary and complex to the beginner. Concepts The debugging of a web application involves several components: The Application Server Generally speaking all the application servers support the debug mode, you just have to enable it when starting up the application server. The IDE You can debug your application using the default command line debugger, which will give you complete access to the debugger and to the debugged software.
Deepak. Debugging Tomcat Remotely Using Eclipse - WG: Programmer's Cafe - Confluence. Debugging Tomcat as a Remote External Application Eclipse can be configured to provide debugging information for a running tomcat instance that is configured with JPDA support.
This approach may work better for users using Windows. Instructions for setting up tomcat to use JPDA. Once you have tomcat configured: Start tomcat manually from the command line. Icon If you do not see the console output when using this method, you can simply keep open a separate window that displays the last contents of catalina.out. Debugging Tomcat as an External Tool from within Eclipse You can also configure Eclipse to be able to start and stop tomcat as a program (this approach also seems to work well on Windows).
If you have already completed the above steps, you will need to stop tomcat to use the steps below. If you have not already done so, set a breakpoint somewhere in your code (preferably something not associated with startup) by left-clicking to the left of a line of code.