Hello marc,
That's not enough to simply add this: as the JVM will automatically create
one instance of this class (no arg constructor), we would end up with a UCL
that don't have an associated Repository. We will need to implement a new
classloader that delegates loading correctly. Do you think that delegating
to the context classloader is enough? In multi-Repository situations, does
the current repository is correctly associated with each thread? (maybe
that's one for Scott)
Cheers,
Sacha
> -----Message d'origine-----
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]De la part de marc
> fleury
> Envoye : mercredi, 2 octobre 2002 20:18
> A : [EMAIL PROTECTED]
> Objet : RE: [JBoss-dev] [ jboss-Bugs-617574 ] Classloader deadlock
>
>
> > I come back again with my old trick that hadn't much success
> > in the past.
> >
> > To solve the system class loader problem definitivly, at
> > least with JDK 1.4 and upper, why not use the
> > "java.system.class.loader" system property (see javadoc of
> > java.lang.Classloader.getSystemClassLoader).
>
> Sacha that is the solution, also it makes sure that cretins that don't
> delegate to context get this working properly. Can you add the System
> ClassLoader definition to the run scripts?
>
> thanks
>
> marc f
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
