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 classloading conflicts in osgi land. /max On Sep 13, 2010, at 11:49, Emmanuel Bernard wrote: > I would favor such model ie. an automatic event registration when the lib is > in the classpath. > We could generalize that actually to let any lib to register its event > listeners (maybe something a la service locator). > Today Search and Validator have a specific hook in Core. > > On 11 sept. 2010, at 09:20, Hardy Ferentschik wrote: > >> In Search and Validator we enable the listeners when we detect Search res. >> Validator on the classpath (with an option >> to explicitly not enable it). Maybe we could do the same with Envers? >> >> --Hardy >> >> On Fri, 10 Sep 2010 20:40:04 +0200, Steve Ebersole <st...@hibernate.org> >> wrote: >> >>> What do you think of an option that says "enable envers", rather than >>> explicitly needing to set up each listener? >> >> >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev > > > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
