Hey Sasha, I have been wanting to do an iBATIS realm for a while. Glad to
see I am not alone. ;-)
You have a couple of options.
I use IDEA, and run tomcat externally. When I want to debug startup code, I
set JPDA_OPTS (in setenv.sh/bat) to this:
JPDA_OPTS=-Xdebug
-Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=y
Most of that is already there (in tomcat 5.0.27 line 141 of catalina.sh),
and tells the JVM to start the debugger in server mode using sockets, to
listen on address 8000, and to suspend immediately, until a debugger
attaches.
Then, set your breakpoints, and start tomcat using this:
$CATALINA_HOME/bin/catalina.sh jpda start
Once it starts, you can attach, and debug everything starting at the
beginning.
Java rocks! :-D
Larry
On Apr 1, 2005 12:57 PM, Sasha Borodin [EMAIL PROTECTED] wrote:
I'd like to solicit suggestions for debugging Tomcat startup -
specifically
various class initializations.
I've written a custom Realm implementation; in it, I use some data access
classes which use iBatis; these classes work great when used in a web
application (all jars residing in the apps WEB-INF/lib); but I'm getting
errors when these classes are initialized from jars in the server/lib
directory at startup.
If you have suggestions for how to debug the startup, especially from an
IDE
like Idea, please post. Also, if there are guidelines for where to place
certain types of jars (common vs. server), please post a link. Right now
I've got my jdbc jars in common/lib, and my custom Realm and data access
classes (including ibatis related jars) in server/lib.
Thanks for your help,
-Sasha Borodin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
