The general idea is good. But not really getting the point/purpose of
having both before and after hooks.
On 08/17/2012 01:12 AM, Strong Liu wrote:
> I'm thinking add the interface below, with it, modules like envers can choose
> either before or after the metamodel get processed to hook into i
Not really sure what you are suggesting really. But JPA is very
specific in how this is supposed to happen. Providers are passed an
instance of BeanManager. If present, the JPA provider must use the
BeanManager API.
On Sat 18 Aug 2012 05:06:30 PM CDT, Gunnar Morling wrote:
> Hi Steve,
>
>> u
Hi Steve,
> using JPA now has a dependency
> on the CDI API being available on the classpath. We need to decide if
> that is unreasonable.
I guess most Spring users (or more generally, people not using CDI)
wouldn't really like this dependency.
In BV 1.1, we have a similar requirement: CDI supp
Recently I just finished up adding JPA 2.1 support for CDI injection of
callback listeners. Couple of things about this:
1) Took this opportunity to refactor and clean up a lot of this code.
On benefit of this was I added a feature now where after transaction
hooks are not added as part of Act
