Debugging, It seem that the most popular tip is it to use println().
If you want to actually trace into to EJB code you can do it in some servers
but the process is slow. And still you see only half of the picture, you
can't trace from the client code to the server code and back. Not to mention
the time it take to restart the server after every code change.
I agree, this is a sore spot I have with hollywood(don't
call us, we'll call you) technology. You have this
problem whenever you are using 3rd party software and don't have the
source code, but I find it gets even worse when you don't know when your own
code is getting called.
An options for a stack trace to automatically show up might be nice.
Btw, I never had any problems using JDB with weblogic.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
