Yeh, it should - but I think that's overkill, and only available in the
Enterprise versions of tools such as JBuilder... i'm thinking along the
lines of a 'free', more accessible solution.
hmm...
-Rob
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Aaron Mulder
Sent: Sunday, August 06, 2000 6:30 AM
To: jBoss Developer
Subject: Re: [jBoss-Dev]
java.lang.ClassCastException:sun.misc.Launcher$AppClassLoader
This is a little unfortunate, since most IDEs want the classes
you're coding to be on the classpath when you debug... But heck, if they
support remote debugging, then we ought to be able to run jBoss separately
and then attach the debugger. I've never tried that with JBuilder, but I
think it's supposed to work...
Aaron
On Sun, 6 Aug 2000, Rickard [iso-8859-1] �berg wrote:
> The basic reason for this bug is (AFAICT) that the classes have been
> added to the classpath prior to launching jBoss. This is wrong since
> they should be loaded dynamically by the server. It may work now, minus
> some of these exceptions, but in the future when dynamic code updating
> is added it will lead to major breakage.
>
> I would suggest that you run the server as intended instead, i.e. with
> none of the jBoss classes on the system/app classpath.
>
> /Rickard
>
> --
> Rickard �berg
>
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
