Taken from the JavaDoc (http://www.springframework.org/docs/...iewFilter.html):
A single session per request allows for most efficient first-level caching, but can cause side effects, for example on saveOrUpdate or if continuing after a rolled-back transaction. The deferred close strategy is as safe as no Open Session in View in that respect, while still allowing for lazy loading in views (but not providing a first-level cache for the entire request).
We do want to use the single session per request strategy, but we also to address the side affects. What can we do to continue from an exception (duplicate key or even other exceptions) ?