Review subsystem usage across Narayana

Components and their subsystem requirements:

Transactions

• To Investigate

XTS

• Bootstrap coordinator
• Setup WS endpoints for coordinator
• Setup WS endpoints for the participants
• Respond to configuration from standalone-xts.xml

REST-TX

• Boostrap the coordinator
• Setup a REST endpoint for the coordinator
• Setup a REST endpoint for the participants

Blacktie

• Register MDB
• Register MBean

STM

• To Investigate

TXF

• Modify the WS handler chain on application deployment
• Registers a CDI extension

Notable Dependencies

TXF

• Weld -> EJB3 -> Transactions (Could check that each link is valid. Check if subsys or regular dep)
• JBossWS. Might be able to remove by putting the WS specific stuff into the XTS subsystem.

Subsystem Breakdown

Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems.

Transactions

• All current stuff
• STM
• TXF (Unlikely to work due to dependency on Weld for loading a portable extension)

XTS

• All Current Stuff

RTS (new)

Blacktie (new)