Hi Kalle, In JPA 2.1 it's BeanManager that is responsible for creating objects of entity listeners. BeanManager implementation from this library uses ObjectLocator.autobuild() to create these instances, so you may @Inject pretty much everything as you do with regular tapestry services.
As for configuration property, maybe this: https://docs.oracle.com/middleware/1213/toplink/java-reference/org/eclipse/persistence/config/PersistenceUnitProperties.html#CDI_BEANMANAGER On Fri, Jul 24, 2015 at 8:12 PM, Kalle Korhonen <kalle.o.korho...@gmail.com> wrote: > Thanks Dmitry, looks excellent. Even so that I don't see any reason we > shouldn't merge this to tapestry's core JPA integration at some point. I > didn't read the code that carefully, but do the injectable JPA > entitylisteners also support (totally non-spec) constructor injection? Do > you know if the corresponding > org.hibernate.jpa.AvailableSettings.CDI_BEAN_MANAGER > is available in EclipseLink configuration and if so, what's the name of the > property? > > Kalle > > On Thu, Jul 23, 2015 at 2:03 PM, Dmitry Gusev <dmitry.gu...@gmail.com> > wrote: > > > Hello Tapestry users! > > > > I would like to share with you a new small tapestry5 library that may be > > helpful for tapestry JPA applications: > > > > https://github.com/satago/tapestry-jpa-transactions > > > > 1) It overrides @CommitAfter annotation with support for nested calls > (only > > top-most method will actually commit transaction) > > 2) Simple service for wrapping Runnable/Invokable objects with > transactions > > when you need precise control over transactions > > 3) Before/after commit callbacks > > 4) Support @Injects in entity listeners when used with JPA 2.1 > > > > Please see GitHub readme for details. > > > > It's built against tapestry 5.3.7, but should also work with latest 5.4 > > versions (not tested). > > > > > > -- > > Dmitry Gusev > > > > AnjLab Team > > http://anjlab.com > > > -- Dmitry Gusev AnjLab Team http://anjlab.com
