[
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 4:47 AM:
---------------------------------------------------------------
Sanne/Mircea, something odd is happening here.
I have a Hibernate 2LC example here that uses Infinispan 4.2.0.BETA1. In the 2LC
integration code, I do the following:
{code}
Configuration regionOverrides...
// Where transactionManagerlookup is
org.hibernate.cache.infinispan.tm.HibernateTransactionManagerLookup@74ae8af4
regionOverrides.setTransactionManagerLookup(transactionManagerlookup);
{code}
And when Infinispan's TransactionManagerFactory calls:
{code}
TransactionManagerLookup lookup = configuration.getTransactionManagerLookup();
// lookup is pointing to
org.hibernate.cache.infinispan.tm.HibernateTransactionManagerLookup@74ae8af4
{code}
And this is before this jira was fixed. FYI
org.hibernate.cache.infinispan.tm.HibernateTransactionManagerLookup implements
org.infinispan.transaction.lookup.TransactionManagerLookup. It's a TM lookup that
takes Hibernate's TM and puts it into Infinispan.
So, what exactly have you guys fixed to be precise?
was (Author: galder.zamarreno(a)jboss.com):
Sanne/Mircea, something odd is happening here.
I have a Hibernate 2LC example here that uses Infinispan 4.2.0.BETA1. In the 2LC
integration code, I do the following:
Configuration regionOverrides...
// Where transactionManagerlookup is
org.hibernate.cache.infinispan.tm.HibernateTransactionManagerLookup@74ae8af4
regionOverrides.setTransactionManagerLookup(transactionManagerlookup);
And when Infinispan's TransactionManagerFactory calls:
TransactionManagerLookup lookup = configuration.getTransactionManagerLookup();
// lookup is pointing to
org.hibernate.cache.infinispan.tm.HibernateTransactionManagerLookup@74ae8af4
And this is before this jira was fixed. FYI
org.hibernate.cache.infinispan.tm.HibernateTransactionManagerLookup implements
org.infinispan.transaction.lookup.TransactionManagerLookup. It's a TM lookup that
takes Hibernate's TM and puts it into Infinispan.
So, what exactly have you guys fixed to be precise?
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