I have since gotten this to work. Oddly, user.dir _does_ impact
certain things but not others (i. e., some portions of jBoss' startup
sequence work when reading their properties files while others seem
to fail).
The hack I got to work is creating a JBuilder shortcut with
<jboss home>\bin\ as the working directory (the "start in" directory)
and launching that. It will then let you set breakpoints in
your bean code, etc. I'm still a bit unclear on the difference
between the working directory and user.dir, though.
David
P.S. FWIW, I'm using Windows 98.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of David Solum
> Sent: Wednesday, July 26, 2000 4:05 PM
> To: jBoss-User
> Subject: [jBoss-User] Running jBoss in JBuilder Debugger
>
>
> Does anyone know how to run jBoss in JBuilder's debugger?
> I got it to "start" by adding run.jar to the classpath,
> setting the main class to org.jboss.Main, etc.
>
> However, I had trouble with what appears to be file paths,
> causing InstantDB and auto-deploy to fail. I tried setting
> the user.dir system property to c:\Program Files\jboss2\bin,
> which is where I usually run jBoss from, but that didn't
> help.
>
> Any ideas?
>
> Thanks,
>
> David
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
