Envers works using *Hibernate* event listeners which are more fine grained
than JPA listeners/callbacks. JPA does not define all the events needed to
capture everything Envers does.
Also no other provider has this capability, which in my experience
sometimes makes it difficult to get into specs.
On Aug 31, 2012 8:05 PM, "Christian Beikov" <christian.beikov(a)gmail.com>
I wondered how envers works/could work in a JPA portable way. Are you
using somehow a entity listener approach or so? Does the the code needed
for envers really depend on the hibernate core stuff or does hibernate
just offer a more relaxed contract in respect to entity listeners?
I was just wondering why nobody proposed the auditing stuff to be
included in the jpa spec since there were already many requests for
auditing for other jpa impls. IMO it's a fairly common issue to address
auditing and therefore worth to, not necessarily be standardized but, at
least be provider independent.
I don't have a problem with hibernate at all, I will go on using it
since it's just great, but the question just came up in my head and I
wanted to know if you maybe already discussed something like that with
the jpa team?
hibernate-dev mailing list