|
Spring TopLink support is now being addressed by the TopLink team at Oracle. It's more likely to be shipped by them rather than as Spring. I referred the guy working on it there to this issue, so he's seen the contribution. Thanks. What I've seen coming out of this so far from Oracle looks great. TopLinkTemplate, TopLinkDaoSupport, TopLink interceptor, TopLinkTransactionManager, and a special TopLink Session implementation for Spring. Also some good documentation. I'll post here when there's a public URL/download for this. In the meantime, a minor update to make current code work with JTA transactions both Spring and CMT driven. And another minor patch to remove a redundant field. Are there any plans to add an OpenSessionInViewInterceptor for this under the support package? I believe it's really easy to add. I'd do it, but Oracle is doing major rewrites of the TopLink support and I bet the latest version will have this and much more. An overhaul of the TopLink support as provided by Oracle is available as part of core Spring now. Thanks to everybody who has helped to make this happen, in particular to Slavik and to Jim from Oracle! A note on JTA: The JTA support now builds on TopLink's built-in JTA support, which is necessary for proper integration with JTA anyway (due to the need for JTA transaction synchronization of the active UnitOfWork, which we can't provide with pure Spring means). Fortunately, an OpenSessionInViewFilter or OpenSessionInViewInterceptor is not necessary to make TopLink's lazy loading or instance caching work. Simply touch the lazy fields and they are gonna load themselves, even without the original Session or UnitOfWork that loaded the root object. TopLink's architecture is significantly different from Hibernate, which shows here too. Juergen |
|||||||||||||||||||||||||||||||||||||||||||
All the source for the TopLink support and build script for both TopLink and petclinic example. The build scripts assume that the spring directory is on the same level as the project directory.