> 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.
Unfortunately for us it's not that simple. We have this big-ass application that includes 5-10 processes, which are started by a shell script, and communicate via RMI. That's why I called it "servlet-type"... really, what I meant was "processes that I gotta attach to". Thanks tho. scott
