Interesting, we should add that information in the integrator section of Hibernate Core 4's doc.
On 4 août 2011, at 10:34, Strong Liu wrote: > as Adam's post http://www.warski.org/blog/2011/08/using-envers-with-as7/ > if someone create an hibernate integrator, then he should follow adam's > approach > > create a module for that integrator, which depends on hibernate-core > add "Dependencies: ingetrator name services" to app's META-INF > > no need to change org.hibernate.module.xml i think > > > > ----------- > Strong Liu <st...@hibernate.org> > http://hibernate.org > http://github.com/stliu > > On Aug 4, 2011, at 1:44 AM, Emmanuel Bernard wrote: > >>>> This will not work for any other user provided Hibernate Core integrators >>>> I think. >>> >>> My reasoning for making it an optional module dependency isn't strong. Its >>> more so that the org.hibernate module can load, even if envers is missing >>> for some reason. I'm fine with not making it "optional="true"" for now. :) >> >> optional is good. What I am saying is that any user can write an Hibernate >> integrator that ought to be started by Hibernate upon SearchFactory or >> EntityManagerFactory construction. You can't force all these guys to change >> stuffs in org.hibernate.module.xml > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
