On 2002.02.18 02:44:18 -0500 Scott M Stark wrote:
> 
> This is a different issue I'll look into as I get into the mbean
> behavior.
> The issue with Bug #516684  is not that the same classloader is used
> to load the original and redeployed mbean. This changes as you say.
> The problem is that the classloader used as the thread context
> classloader
> for mbean operation invocations is the same classloader across all
> mbeans. This will be a problem when MarshalledObjects are unserialized
> because, in the absence of security manger that allows for dynamic
> class loading, the thread context classloader is used. Its not sufficient
> to load the mbean with a unique classloader, this classloader also
> needs to be established as the thread context classloader.

So would bug 516684 be solved if

1. we used jbossmx

and

2. in jbossmx the interceptor stack for mbean invocation set the thread
context classloader as we do already for ejb invocations?

david jencks
> 

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to