On 29/05/2015 15:14, Michael Musgrove wrote:
On 29/05/15 13:22, Tristan Tarrant wrote:
> Hi all,
>
> I'm reworking the Infinispan Server package so that it is built around
> WildFly Core as I want to keep it as lean as possible.
> I need to pull in a couple of additional subsystems from WildFly proper
> and one of them is causing some head-scratching: the transactions
> subsystem. It has a bunch of hard dependencies on a ton of modules which
> really sound optional. Examples:
>
> - the IIOP stuff
> - Narayana compensations (JAX-WS, JAX-RS, Servlet API, Weld)
> - HornetQ
We need IIOP for JTS support (we use the same jars for JTA and JTS so we
need it regardless of whether you enable JTS) .
We need hornetq to leverage their fast journal (for our transaction logs).
I agree that Naryana compensations should not be required by the
subsystem and this seems to be bringing in the bulk of the extra
dependencies. I will look into why we need to include it in the subsystem.
Do you have more examples or do you agree that if we addressed the need
for compensations in the subsystem then that would be good enough.
Thanks for explaining the others, but yes, if anything can be made
optional, I'm all for it.
Tristan
--
Tristan Tarrant
Infinispan Lead
JBoss, a division of Red Hat