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

[Galder Zamarreño (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579805#comment-12579805 ] 

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 at 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.
  
> Configuration.setTransactionManagerLookup() is ignored 
> -------------------------------------------------------
>
>                 Key: ISPN-883
>                 URL: https://issues.jboss.org/browse/ISPN-883
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 4.0.0.Final, 4.1.0.Final, 4.2.0.Final
>            Reporter: Sanne Grinovero
>            Assignee: Mircea Markus
>             Fix For: 4.2.1.Final, 5.0.0.ALPHA3
>
>
> opposing to being able to set the classname only, it should be able to pass existing instances. I'm dealing with a case in which I have to create and configure a TransactionManager before starting the cache.
> If it's simple enough, it would be very nice to have this in 4.2.1 too - feel free to remove the version if it doesn't fit.
> Providing a testcase.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira