I am not a fan of this. For a number of reasons. First this means added complexity to manage the list of listeners in regards to (1) not over-writing any explicitly registered listeners and (b) not duplicating listeners.
Second keep in mind that the hibernate3.jar from the release distribution we put on SourceForge contains all classes Some anyone using it would always "have envers on the classpath". On Mon, 2010-09-13 at 11:49 +0200, 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 > -- Steve Ebersole <st...@hibernate.org> http://hibernate.org _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
