Spring is like so much of IT you end up taking it on blind faith, the last
thing I would do is read the source code as it would just make it clear how
little I know or understand :) You also end up pulling Spring into projects
as you go as it has a lot of sub-systems that work together, at which point
you just live with it.
If you are building a simple wrapper solution, please keep posting as you
get it working with JOOQ. I can handle simple :) Such an approach also
works well for smaller projects where you don't want the learning curve or
support of a major framework. Even without nested transaction support your
model of
[name].transaction(() -> { work to be done }
Maps nicley on the unit of work design pattern I first picked up from being
around C# developers. Such a pattern also removes much of the need for
nested transactions in the first place.
I have to warn you that getting your solution accepted/used is going to be
slow, just because so many of us are stuck in Java 7 worlds. Your example
joot-playground is yet another example of what Java 8 will allow.
Roger
--
You received this message because you are subscribed to the Google Groups "jOOQ
User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
