Issues like this:
https://hibernate.onjira.com/browse/HHH-7084
are caused by a mismatch in how Hibernate choose to handle these
classloading issues versus the way another framework/API did
(GWT/Jetty in this case). I first thought GWT was to blame, but the
issue is more complex. Then you need to start configuring what you
shouldn't and all...
Thread Context ClassLoader is the de facto standard these days. If we
choose to actually defining and allowing classloading to be
customized, the default must be TCCL.
Regards,
Michael
On Mon, May 14, 2012 at 5:18 AM, Hardy Ferentschik <hardy(a)hibernate.org> wrote:
On May 14, 2012, at 9:51 AM, Emmanuel Bernard wrote:
> Can you elaborate on the issues that it has brought?
Yeah, I would love to hear more about this as well :-)
_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev