On Friday, November 14, 2014 10:42:08 PM UTC, Garret Wilson wrote:
>
> Thanks so much, Lukas. I'm immediately going to be hitting the books.
>
> I want to mention that we are *not* using Spring. We are using an
> embedded Jetty instance with a RESTEasy REST interface on one side and a
> Wicket web interface on the other. As you know I'm a bit behind on the
> latest JavaEE database stuff, so if Servlet 3 and Jetty help us out, great.
> (I will know more after reading this weekend.) Otherwise, the only thing
> "taking care of things for us" will be jOOQ and JDBC, so I'm not sure if
> @Transactional et. al. is going to help us out.
>
While Spring looks very much like a complete platform that in your case
would cause issues as you are already using Jetty, you can use parts of
Spring such as their transaction library within your own environment.
All the examples on the JOOQ site try and simplify the code by not
including all the imports (at times I find this just complicates things).
There is an example on the Spring page at the following link, that does
show a more complete basic example of adding Spring TX to JDBC based code.
http://spring.io/guides/gs/managing-transactions/
The page also gives example build scripts so you can see what is needed
where.
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.
