<p><br>
Am 19.05.2012 14:45 schrieb "Hardy Ferentschik" <<a href="mailto:hardy@hibernate.org">hardy@hibernate.org</a>>:<br>
><br>
><br>
> On May 18, 2012, at 4:38 AM, Michael Nascimento wrote:<br>
><br>
> > Issues like this:<br>
> ><br>
> > <a href="https://hibernate.onjira.com/browse/HHH-7084">https://hibernate.onjira.com/browse/HHH-7084</a><br>
> ><br>
> > Thread Context ClassLoader is the de facto standard these days. If we<br>
> > choose to actually defining and allowing classloading to be<br>
> > customized, the default must be TCCL.<br>
><br>
> Funny that you that. We had just had an Hibernate Validator issue not so long ago where<br>
> a modular system expert told us just the opposite. Don't use TCCL first ;-)<br>
><br>
> I think the bottom line is that there is no standard. Checking TCCL first and then the<br>
> current class loader was a strategy which Hibernate applied for quite some time.<br>
> It proved to be a good approach for quite some time. However, the current trend seems to be<br>
> to make the class loading more configurable and allow to for example pass a class loader.</p>
<p>Yepp, I think that's the best way.</p>
<p>The default behavior could be the one you describe, but if a specific classloader is configured by the user, this one should be taken to load user provided resources and classes.</p>
<p>AFAIK under OSGi it's not defined what CL is set as the TCCL, so one can't really rely on it there.</p>
<p>--Gunnar</p>
<p>><br>
> --Hardy<br>
><br>
><br>
> _______________________________________________<br>
> beanvalidation-dev mailing list<br>
> <a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev">https://lists.jboss.org/mailman/listinfo/beanvalidation-dev</a></p>