One way to simplify the debugging setup is to use the remote debugger feature of the
JPDA debuggers. In the start script for JBoss you just add the following to the windows
run.bat:
set DEBUG=-classic -Xdebug -Xnoagent
-Xrunjdwp:transport=dt_socket,server=y,address=12345,suspend=y
java %DEBUG% -classpath "%CLASSPATH%" org.jboss.Main %1 %2 %3 %4 %5 %6 %7 %8 %9
In your debugging client you just add the JBoss source paths and don't have to
worry about getting the classpath right which is the tedious and error prone part.
To attach to the waiting JBoss vm you configure the debugger client to use the
equivalent transport setup.
By the way, a great little stand-alone debugger I have found very useful is BugSeeker
See, http://www.karmira.com
----- Original Message -----
From: "Charles Brault" <[EMAIL PROTECTED]>
To: "Jboss" <[EMAIL PROTECTED]>
Sent: Thursday, December 14, 2000 2:58 PM
Subject: [jBoss-User] Debugging apps in Jboss
> If any one has managed to successfully used an IDE like CodeGuide or
> Jbuilder to debug an app running in Jboss, I would sure appreciate it if
> you could provide a detailed cookbook. I've refered to the documentation
> page on using Jbuilder 3.5 (I have 4.0) but haven't been able to make
> headway.
>
> I would imagine that there are others out there who would appreciate it
> also.
>
> Thanx
>
> chaz
> --
> Charles E Brault
> [EMAIL PROTECTED]
> 202-342-8070x238 202-342-8078 (f) 301-351-9186 (c)
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
