|
From: Juergen H. <ju...@in...> - 2005-05-05 14:50:10
|
Well-spotted, I have deliberately kept this out up to now, because TopLink has its own Connection acquisition rules (by default lazy; within a write transaction, not before actual commit). I've spent some time today to research this a bit further: for a read-write transaction, TopLink can be forced to start the database transaction early, which makes it stick with a single JDBC Connection upfront. That JDBC Connection can be retrieved (through some API hoops), so I've added support for exposing it as transaction for JDBC access code. A DataSource needs to specified on TopLinkTransactionManager's "dataSource" property to enable this. To be committed later today :-) Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Erwin Vervaet Sent: Thursday, May 05, 2005 8:57 AM To: spr...@li... Subject: Re: [Springframework-developer] TopLink support > It's modeled somewhat analogously to our Hibernate support, although with > the important difference that we use a custom SessionFactory interface for > TopLink (because TopLink does not define such a resource out of the box). > There are the usual suspects: LocalSessionFactoryBean, TopLinkTemplate, > TopLinkCallback, TopLinkTransactionManager. Just wondering, is it possible to mix TopLink DB access and straight JDBC use in the same transaction, like with the HibernateTransactionManager? If I understand the JavaDoc this doesn't seem to be the case? Erwin ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |