Spring for transaction management and database (via JDBC) access?
I'm on a project where I have a LOT to do and not a lot of time to do it. We (well...make that me as the lone web person) will be using JSF generated via Java Studio Creator (love that tool) as the presentation layer.
This is all well and good, and I feel confident in both the tool and JSF to do that, but for things like transaction management, us JSF folks seem to be out of luck!
So, my thought was to use Spring for transaction management, and to aid in the JDBC access (not going for an O/R mapping like Hibernate).
The thought is to build much of the business logic and data access code inside of Spring beans. These beans will be used by the presentation logic to perform queries that at times will be transaction oriented.
I have read that Spring integration with JSF can be done without too much problem (just change the bean resolver), but after reading a book on Spring, I'm sort of in a state of shock .
Spring, after reading the book, looks as complicated as EJB (even though I keep reading that it is not). Each part is easy enough to understand, but to use it the book made it sound like you have to assemble so many parts that the plumbing code will exceed the source code!
So, has anyone had luck integrating the two and how difficult did it end up being?