"osgi land" in general is a problem.
But yeah, I had even added a comment in this code that really we need to
allow passing in the ClassLoader to use. In fact this is not osgi
specific. In general JPA says we should use a specific ClassLoader for
these lookups in JEE deployments, namely the on
Hi,
Anyone know where http://www.hibernate.org/hib_docs/tools/* went after the
merge ?
/max
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
If this is done please make it super easy to disable that behavior - i.e. I
don't want envers, search nor validator to be enabled by default when I run
queries or reverse engineering from within tooling.
i.e. I believe Search has a property to disable the behavior which we use to
avoid classloa
