I don't think you'll be able to convince the Infinispan of doing that:
one of the major burdens of using Infinispan for users is that it is
composed of so many jars, so we'll actually try to make the number of
dependencies smaller. Apparently a lot of people do not know how to
use dependency managers like Maven and struggle with such things.. :-(
I'd also question the usefulness of doing this: even if the platform /
container you're using does provide some JTA capability, it's not
necessary the same one as your JPA implementor is being configured to
use (some people really like to just use the JDBC transactions).
Hibernate ORM has a similar Service to abstract "how" exactly to
interact with transactions; I understand you don't want to rely on the
Hibernate specific one but other JPA implementors would probably have
a similar facility?
Maybe we should just make an Hibernate Search "Service" for this and
let users plug their custom one? You could provide a couple of
implementations to satisfy the needs of the main JPA implementations.
On 20 June 2015 at 17:33, Martin Braun <martinbraun123(a)aol.de> wrote:
I just stumbled upon the JTA TransactionManager lookup mechanism of
Infinispan and am now using this when a JTA transaction is needed.
This means I don't have hacky lookups of UserTransactions. Now I've been
wondering if it was possible to make the lookup mechanism
a separate module in Infinispan so I don't have to import the whole thing.
I am talking about
particular. Do you think that I can convince the Infinispan team
(which includes you :D) to keep that in a different place than