[jbossts-issues] [JBoss JIRA] (JBTM-1398) Review subsystem usage across Narayana

[Paul Robinson (JIRA)]

    [ https://issues.jboss.org/browse/JBTM-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749416#comment-12749416 ] 

Paul Robinson commented on JBTM-1398:
-------------------------------------

Pushing this back to 5.Final as the decision to have a TXF in it's own subsystem or combined with Transactions, will not impact the community using M2. If we decide to add configuration to TXF, we will then need to think about this as the configuration is located under the subsystem section of the standalone-*.xml

We will need to address this before Narayana 5.x is merged into AS7, as they are unlikely to want an explosion in the number of subsystems.
                
> Review subsystem usage across Narayana
> --------------------------------------
>
>                 Key: JBTM-1398
>                 URL: https://issues.jboss.org/browse/JBTM-1398
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: TXFramework
>            Reporter: Paul Robinson
>            Assignee: Paul Robinson
>             Fix For: 5.0.0.M2
>
>   Original Estimate: 2 days
>          Time Spent: 1 day, 7 hours
>  Remaining Estimate: 2 days, 6 hours
>
> h2. Components and their subsystem requirements:
> h5. Transactions
> * To Investigate
> 	
> h5. XTS
> * Bootstrap coordinator
> * Setup WS endpoints for coordinator
> * Setup WS endpoints for the participants
> * Respond to configuration from standalone-xts.xml
> h5. REST-TX
> * Boostrap the coordinator
> * Setup a REST endpoint for the coordinator
> * Setup a REST endpoint for the participants 
> h5. Blacktie
> * Register MDB
> * Register MBean
> h5. STM
> * To Investigate
> h5. TXF
> * Modify the WS handler chain on application deployment
> * Registers a CDI extension
> h2. Notable Dependencies
> h5. 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.
> h2. 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.
> h5. Transactions
> * All current stuff
> * STM
> * TXF (Unlikely to work due to dependency on Weld for loading a portable extension)
> h5. XTS
> * All Current Stuff
> h5. RTS (new)
> h5. Blacktie (new)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira