Freddy Wong wrote:Eclipse Galileo JEE already has a pretty good Tomcat server adapter.
Your opinion may vary. Mine does. I find that the WST Tomcat adapter knows more about Tomcat's internals than it should while simultaneously knowing less about them than it needs to. Plus warping the entire environment for the theoretical benefit of people working with a release of Tomcat that went end-of-life over 5 years ago.
I liked the sysdeo plugin a lot better, but it's no longer actively supported, and it doesn't seem to operate reliably under Galileo, so I generally end up launching an external Tomcat and attaching to it.
Customer surveys are for companies who didn't pay proper attention to begin with.
Tim Holloway wrote: I generally end up launching an external Tomcat and attaching to it.
Why don't you configure Remote Debugging in both Tomcat and eclipse.
Because that's doing it the hard way.
Actually, that's exactly what I am doing, and I don't like it. I much preferred sysdeo's approach where it would automatically launch Tomcat with debugging enabled, connect the app(s) under test to that Tomcat's debugger, and not muck around with internal config information so that the debugging config was essentially identical to the "real" config, refuse to pick up on webapps just because they hadn't been originally designed with a webapp-faceted project or lived in places other than where the plug-in wished to find them.
And for 100% certain, not go stuffing application config information inside server.xml, which has been discouraged since Tomcat 3 end-of-lifed, lo those many years ago.
In other words, I consider the WST Tomcat debugging feature to be vastly inferior to sysdeo. It's more cumbersome, more fragile, and less flexible, and I wish sysdeo were still maintaining their plugin so I didn't have to play ping-pong with the software everytime I needed to debug a webapp .
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com