Hi,
because the Beans run in the process context of JBoss, JBoss must be started
in the debugger modus.
I can retrace your VA problems, because I had the same ;-). Switch to
JBuilder and then you got no memory Problems
like with this fat and overloaded WTE. I did it and hat a great time with
debugging beans over process limits.
You can have two main processes in JBuilder. On is JBoss in the Debugger and
the other is the client of your beans.
And when you got breakpoints in the Beans JBuilder will surely stop there if
the execution flow tries to pass the breakpoint.
So, I hope I could help you a bit.
Mo
----- Original Message -----
From: "jK.MkIII" <[EMAIL PROTECTED]>
To: "jBoss-user" <[EMAIL PROTECTED]>
Sent: Thursday, April 26, 2001 11:00 AM
Subject: [JBoss-user] EJB Debugging in jBoss?
> Hello,
>
> I have one question.
>
> What are possibilities for debugging beans running inside jBoss? I use
> VisualAge for Java 3.5 EE so I am used to debugger in that and if there
> is some way to use that debugger I would be really really happy :) I
> was even thinking about running jBoss inside VAJ, but that might kill my
> poor computer :) Would really need some solution how to keep this
> running at usable speed (WTE was horribly slow, propably because for
> some reason it totally reloaded all beans for every method call.. oh boy
> all those JNDI calls :) but in jBoss I don't know how to debug my
> beans..
>
>
>
> --
> jK.MkIII
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
