se to
bootstrap the whole thing.
Thanks,
Rob
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:jboss-user-
> [EMAIL PROTECTED] On Behalf Of Scott M Stark
> Sent: Thursday, September 25, 2003 9:14 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] Re:[JBoss-user]ClassC
Version 2 still suffers from deadlock problems because is does not
reliquish the class loader lock. The only hack to workaround the vm
issue would be to retry loading after seeing a CCE.
Robert Cauble wrote:
Thanks - I really appreciate the help.
Also, is this problem something which you have wor
; with this approach such that you switched to UnifiedClassLoader3?
>
> Thanks,
> Rob
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:jboss-user-
> > [EMAIL PROTECTED] On Behalf Of Adrian Brock
> > Sent: Wednesday, September 24, 200
roach such that you switched to UnifiedClassLoader3?
Thanks,
Rob
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:jboss-user-
> [EMAIL PROTECTED] On Behalf Of Adrian Brock
> Sent: Wednesday, September 24, 2003 2:05 PM
> To: [EMAIL PROTECTED]
> Subject
On Wed, 2003-09-24 at 19:54, Robert Cauble wrote:
> > Multiple classloaders is more restrictive when it comes to
> > the security model. Classes in the same package cannot access
> > package private methods if the classes are in different classloaders.
>
> Got it. Thanks.
>
>
> > You can also ge
> Multiple classloaders is more restrictive when it comes to
> the security model. Classes in the same package cannot access
> package private methods if the classes are in different classloaders.
Got it. Thanks.
> You can also get errors when instances of the same class name
> but different cla
On Wed, 2003-09-24 at 16:21, Robert Cauble wrote:
> Thanks for your quick response. That helps a lot.
>
> I have a couple more questions though...
>
> In the parent-delegation model, as long as the class of the shared
> object is present in a parent class loader of the two classes which are
> sh
Thanks for your quick response. That helps a lot.
I have a couple more questions though...
In the parent-delegation model, as long as the class of the shared
object is present in a parent class loader of the two classes which are
sharing the object, there should be no need to marshall the object