There are actually several different ways to run Tomcat under Eclipse.
Probably the most powerful but least common is to simply launch a stand-alone Tomcat with the debugger enabled and attach from Eclipse as a Remote Debugging project. That's basically what a startup.bat launch would be.
More often, Tomcat is launched internally from Tomcat using an Eclipse plugin.
I know offhand of 2 different plugins. One is the one that comes with the JEE spin of Eclipseand it's absolutely horrible. The other is a third-party plugin originally from sysdeo, more recently renamed to mongrel and I'm not sure what it is now, since people aren't presently paying me for my Tomcat expertise.
The reason I despise the JEE spin's webapp server manager (WTP) is that it constructs a mangled Tomcat environment. It copies over some, but not all of the Tomcat runtime configuration into its own opaque internal storage, which then, in addition to being incomplete, has been prone to go stale and require extra work to update.
The reason why I prefer the sysdeo/mongrel plugin is that it uses the original Tomcat configuration and environment, so it doesn't lose any of the various add-ons that some of my more complex webapps have required.
When it comes to destroying a civilization, gas chambers cannot hold a candle to echo chambers.
posted 6 months ago
Sweet post. Ill try both mongrel and this debug project method you've mentioned! Thanks a lot
The world's cheapest jedi mind trick: "Aw c'mon, why not read this tiny ad?"
global solutions you can do at home or in your backyard