Re: [infinispan-dev] [hibernate-dev] Have Infinispan share Hibernate's TransactionManagerLookup strategy

2011/2/2 Galder Zamarreño <galder(a)jboss.org&gt;: > Hmmm, I already did a similar thing for Infinispan 2LC a while back: > > https://github.com/galderz/hibernate-core/blob/master/hibernate-infinispa... Nice, you're taking it from the Settings, I like your approach more. But be aware of ISPN-883, just solved. > 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.

We could add a simplified EmbeddedCacheManager constructor to maintain most of the complexity of building a cache via a configuration but overriding components via provided instances, this relates to a brief chat I had yesterday with Vladimir about a forum thread [1]. Maybe easies way is to expose the GlobalComponentRegistry during the configuration phase, as overrides for internal components? 1 - http://community.jboss.org/thread/161913?tstart=0