Adam Warski wrote: > Hello, > >>> Though I'd have to do some adaptation changes. As I was originally >>> targeting Envers to support JPA mappings, I assumed that it will be >>> working in an enviroment with Hibernate Annotations/EntityManager. So >>> I used ReflectionManager to read the @Versioned annotations. In a >>> pure Hibernate environment, this will not work. >> >> I don't think that making Envers a module in Core means that you >> cannot use >> Hibernate Annotations/EnityManager. In fact these two projects are >> about to be >> moved back into Core. As their own (maven) modules of course. > > Ah, ok. Then Envers would have a dependency on the annotations module (+ > users would have to use AnnotationConfiguration instead of > Configuration). Makes sense, as you configure Envers through annotations > (mark classes as versioned/historized), so you probably also use > Annotations/EntityManager then, not "pure" Hibernate.
Personally, I'm still a fan of plain Hibernate non-JPA config. Could the integration be done with a mind to making it possible to configure Envers via a standard Configuration in a future release? Max.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
