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 con
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 co
Hi Tony,
I think so, but new TransactionalUnitWorker works the same as default one (
CommitAfterWorker).
It won't start a transaction unless you have @CommitAfter on execution path.
Maybe you're talking about starting transactions if no DB calls were made
from method annotated with @CommitAfter?
This does look very interesting.
A while back, Howard built a custom commit handler for me, that delays creating
the transaction until a method with @CommitAfter is seen. Does your library
have a similar side effect, of not starting the transaction because only
methods marked with @CommitAfter
Hey !
All those features seems nice... I'll take a look at it !
Thanks a lot.
Cheers
Le jeu. 23 juil. 2015 à 23:05, Dmitry Gusev a
écrit :
> Hello Tapestry users!
>
> I would like to share with you a new small tapestry5 library that may be
> helpful for tapestry JPA applications:
>
> https://
