I know of 3 Tools(4 if you can live with the idiosynchrasies of Visual Age)
that you can use to debug EJBs.
I can debug my WebLogic/EJB code(including the container code) in both
Symantec Visual Cafe 3.0 Enterprise Edition, and Visual J++ 6.0 Enterprise
Edition. I even step into my JSP(-generated servlet) code!
With J++, the limitation is obviously that you're restricted to JDK1.1. But
it's by far the best IDE that I've worked with. Setting up J++ is pretty
easy- except that I was foxed by the exception-NoClassDefFoundError- for a
long time, until I figured out that it was not being thrown by the IDE, but
the weblogic server! The reason- CLASSPATH!
The good thing about Cafe is that you can use JDK1.2. The bad thing is
everything else:~) There are very serious bugs in Cafe, so it will sometimes
crash and not come up again!
Setting up Cafe is not trivial. I use "java_g.exe" as a pluggable VM. The
most difficult problem to tackle in Cafe has to do with the fact that if
everything is not "right", the last thing you see in you output messages is
something like "loading weblogic.Server.class" for debugging" ... AND THEN
NOTHING! This gave me several nightmares until I cracked it. Again, the
reason- CLASSPATH!!
I've not personally used Kawa, by I have heard just too many good things
about it. You can compile,build,debug EJBs inside Kawa. I was told that in
terms of the IDE, it's not as powerful as J++, but far better than Cafe. And
there are no JDK restrictions.
If any of you need the instructions for setting up Cafe or J++, lemme know,
and I can mail them to you.
Here's a useful link for setting up Kawa:
http://www.synctank.com/developers/kawa.customize.shtml
Regards,
Murali Krishna Devarakonda
p.s. I've found that a ridiculous amount of time is wasted trying to tackle
CLASSPATH problems.
It's compounded an order of magnitude if you're using Cafe, because Cafe has
it's own CLASSPATH mechanism(it doesn't use the system classpath), then
there's Internal VM classpath, pluggable VM classpath, pluggable VM
excutable classpath, pluggable VM prepend classpath, and so on.
Repeat everything for each pluggable VM. Then there are project specific
include class file directories! It's just endless.
I think this classpath menace needs to be killed!
I propose a JNDI solution:~) Any comments?
===========================================================================
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".
