[infinispan-issues] [JBoss JIRA] Issue Comment Edited: (ISPN-883) Configuration.setTransactionManagerLookup() is ignored

[ https://issues.jboss.org/browse/ISPN-883?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño edited comment on ISPN-883 at 2/3/11 5:57 AM: --------------------------------------------------------------- Indeed very suttle, the reason 2LC code worked was cos the TransactionManagerLookup was set on top of an already defined configuration: {code} Configuration customConfiguration = cacheManager.defineConfiguration("aCache", new Configuration()); customConfiguration.setTransactionManagerLookup(new TxManagerLookupA()); Configuration definedConfiguration = cacheManager.defineConfiguration("aCache", customConfiguration); {code} That works, whereas what you guys did in the test didn't: {code} Configuration customConfiguration = new Configuration(); customConfiguration.setTransactionManagerLookup(new TxManagerLookupA()); Configuration definedConfiguration = cacheManager.defineConfiguration("aCache", customConfiguration); {code} The reason the first option works is cos I'm manually setting the TML instance and when the next config is created, it clones this initial config in which case it does pass over the TML. The issue you guys fixed is still correct, the difference was in the way I generate configurations. was (Author: galder.zamarreno(a)jboss.com): Indeed very suttle, the reason 2LC code worked was cos the TransactionManagerLookup was set on top of an already defined configuration: Configuration customConfiguration = cacheManager.defineConfiguration("aCache", new Configuration()); customConfiguration.setTransactionManagerLookup(new TxManagerLookupA()); Configuration definedConfiguration = cacheManager.defineConfiguration("aCache", customConfiguration); That works, whereas what you guys did in the test didn't: Configuration customConfiguration = new Configuration(); customConfiguration.setTransactionManagerLookup(new TxManagerLookupA()); Configuration definedConfiguration = cacheManager.defineConfiguration("aCache", customConfiguration); The reason the first option works is cos I'm manually setting the TML instance and when the next config is created, it clones this initial config in which case it does pass over the TML. The issue you guys fixed is still correct, the difference was in the way I generate configurations. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira