On 2 févr. 2011, at 16:21, Galder Zamarreño wrote:
>>
>>
>> I take Hibernate's TM and hook it into Infinispan. The way I did it is create
a HibernateTransactionManagerLookup class that implements
org.infinispan.transaction.lookup.TransactionManagerLookup and looks up the transaction
manager with Settings.getTransactionManagerLookup().getTransactionManager(properties)
>>
>> Maybe we should look into consolidating this code?
>
> Definitely; in which project would you store the common
> TransactionManagerLookup wrapper?
> I would be fine in depending to the second level cache module, I'd
> assume that anybody having setup Infinispan and Hibernate would use
> the second level cache too, or at least have no issues having to
> depend on it being classpath.
I don't think you should depend on the 2LC module. Instead, maybe we should have an
infinispan-int/ or infinispan-core/ module for shared Infinispan stuff that several
Hibernate modules might benefit from?
Not sure it makes any difference in practice as all modules of core are released in sync
with the same version number. I'd probably go for a single module as it's
simpler.