> I thought the only way to use Turbine was with Tomcat, > therefore I am using Tomcat. What are you using?
I'm using JBoss 3.0.4 with Jetty as it's servlet container. I've been playing around with debugging in Eclipse. My solution is not perfect (because Eclipse does not allow you to make your build target somewhere outside of the project hierarchy, such as the deploy folder of your application server). Anyway, there are a few things that you can do. 1) Run your app server within the debugger! This is easy with JBoss, because JBoss is pure java. The easiest way to do this is to look at the script (or batch) file that you normally use to launch your app server, and then use Eclipse to build a debug target that matches. 2) Configure your application server to launch for remote debugging. This usually means changing the file used to launch the server, using settings similar to these: -classic -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n You should be able to find a page that describes more specifically how to setup remote debugging with whatever app server you are using. One the server is running, you can attach Eclipse's debugger to it using a Remove Java Application launch configuration (see debug perspective, run menu, Debug...). 3) See if an Eclipse plugin provides native support for your app server. It might with Tomcat, but I am not sure. You might also check out an Eclipse plugin called Lomboz (http://www.mycgiserver.com/~objectlearn/products/lomboz.html), which claims to provide J2EE component and web application management for Eclipse. I tried it out and didn't like the way it worked, but you might find it useful. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
