[wildfly-dev] Transaction subsystem dependencies

[Tristan Tarrant]

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

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