This week's book giveaway is in the Mac OS forum.
We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line!
See this thread for details.
The moose likes Object Relational Mapping and the fly likes Transaction handling in 3-tier layered application using Wicket + Spring + Hibernate Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Databases » Object Relational Mapping
Bookmark "Transaction handling in 3-tier layered application using Wicket + Spring + Hibernate" Watch "Transaction handling in 3-tier layered application using Wicket + Spring + Hibernate" New topic
Author

Transaction handling in 3-tier layered application using Wicket + Spring + Hibernate

P Kuling
Greenhorn

Joined: Aug 07, 2008
Posts: 10
Hi,

I'm thinking about using the Open Session In View (OSIV) filter or interceptor that comes with Spring, as it seems like a convenient way for me as a developer. If that's what you recommend, do you recommend using a filter or an interceptor and why?

I'm also wondering how it will mix with HibernateTemplate and if I will loose the ability to mark methods as @Transactional(readOnly = true) etc and thus loose the ability to get some more fine grained transaction control?

Is there some kind of best practice for how to integrate this kind of solution with a three tier architecture using Hibernate and Spring (as I suppose my decision to use Wicket for presentation shouldn't matter much)?

If I use OSIV I will at least never run into lazy loading exceptions, on the other hand my transaction will live longer before being able to commit by being uncommitted in the view as well.
 
GeeCON Prague 2014
 
subject: Transaction handling in 3-tier layered application using Wicket + Spring + Hibernate