Ok I found a solution (), seems you need to set the userTransaction to null on the JtaTransactionManager in order for the regular transaction manager to be used (don't know why spring isn't smart enough to auto-detect this), I added the ability to set this in the spring cartridge (next continous build will have it), so once you get this fix, add these two properties to your spring namespace (and uncomment the "dataSource" property so you have the JtaTransactions again):
<property name="userTransactionName">null</property> <property name="transactionManagerName">java:/TransactionManager</property> I tested it, and it works for me...let me know if it works ok for you as well. -- Chad Brandon - [EMAIL PROTECTED] http://www.andromda.org _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2452#2452 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
