"Scott Evans" <[EMAIL PROTECTED]> writes:
> Oh, wait. Looks like JDEE doesn't provide a mechanism to attach to a
> running process if you're using jdb? Shoot. If that's true, I guess
> I'm back to the command line for now...
If your servlet container is written in Java (most are), another
alternative is to start your container from within JDEE, so that you
don't need to attach to a process.
To step through a servlet deployed with Tomcat, for example, the
following variables should do the trick.
(jde-set-variables
'(jde-db-source-directories (quote ("/usr/local/jdk/src" "./src" "~/src/struts"
"~/src/tomcat" "~/src/servlet")))
'(jde-db-option-properties (quote (("tomcat.home" . "/usr/local/tomcat"))))
'(jde-run-option-properties (quote (("tomcat.home" . "/usr/local/tomcat"))))
'(jde-global-classpath (quote ("/usr/local/tomcat/lib" "/usr/local/jdk/lib"
"/usr/local/tomcat/webapps/{YOUR_APP_NAME_HERE}/WEB-INF/classes" "./lib")))
'(jde-run-application-class "org.apache.tomcat.startup.Tomcat"))
This assumes that your classes reside under Tomcat's 'webapps'
directory (or your server.xml refers to their directory if
elsewhere).
