[wildfly-dev] Transaction subsystem dependencies

[Michael Musgrove]

Thanks,

I have added JBTM-2424 to get the dependency moved to hornetq-journal 
(instead of hornetq-core).

Mike
> I believe it could.  If memory serves me correctly, when the transaction team added this, the HornetQ team had not yet split out the journal.
>
> Andy
>
> ----- Original Message -----
>> From: "Tristan Tarrant" <ttarrant at redhat.com>
>> To: "Andrig T. Miller" <anmiller at redhat.com>
>> Cc: "WildFly Dev" <wildfly-dev at lists.jboss.org>
>> Sent: Friday, May 29, 2015 8:11:09 AM
>> Subject: Re: [wildfly-dev] Transaction subsystem dependencies
>>
>> Couldn't this depend on org.hornetq:hornetq-journal only ? Depending
>> on
>> the whole hornetq module means we're pulling in all of the JMS
>> functionality and APIs as well
>>
>> Tristan
>>
>> On 29/05/2015 15:42, Andrig T. Miller wrote:
>>>
>>> ----- Original Message -----
>>>> From: "Tristan Tarrant" <ttarrant at redhat.com>
>>>> To: "WildFly Dev" <wildfly-dev at lists.jboss.org>
>>>> Sent: Friday, May 29, 2015 6:22:39 AM
>>>> Subject: [wildfly-dev] Transaction subsystem dependencies
>>>>
>>>> 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
>>>>
>>> The HornetQ dependency is for using the HornetQ journal as the
>>> transaction journal.  For transactions, you definitely want that
>>> for performance reasons.
>>>
>>> Andy
>>>
>>>> None of the above are really needed by Infinispan Server. I guess
>>>> I
>>>> could apply manual surgery to the module.xml file to remove stuff
>>>> I
>>>> think is unnecessary and let my testsuite verify if I'm being too
>>>> aggressive, but I was wondering whether it would be better for the
>>>> upstream project to be a bit more careful with the dependencies.
>>>>
>>>> Thanks for any suggestions
>>>>
>>>> Tristan
>>>> --
>>>> Tristan Tarrant
>>>> Infinispan Lead
>>>> JBoss, a division of Red Hat
>>>> _______________________________________________
>>>> wildfly-dev mailing list
>>>> wildfly-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>
>>>
>> --
>> Tristan Tarrant
>> Infinispan Lead
>> JBoss, a division of Red Hat
>>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev


-- 
Michael Musgrove
Red Hat UK Ltd, Transactions Team
e: mmusgrov at redhat.com
t: +44 191 243 0870

Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Michael O'Neill(Ireland)