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

Paul Robinson (JIRA) jira-events at lists.jboss.org
Fri Jan 11 04:11:09 EST 2013


     [ https://issues.jboss.org/browse/JBTM-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Robinson updated JBTM-1398:
--------------------------------

    Description: 
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
* JBossWS

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

h5. XTS
* All Current Stuff

h5. RTS (new)

h5. Blacktie (new)

  was:
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
* JBossWS

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

h5. XTS
* All Current Stuff

h5. RTS (new)

h5. Blacktie (new)


    
> 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: 6 hours
>  Remaining Estimate: 1 day, 2 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
> * JBossWS
> 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
> 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


More information about the jbossts-issues mailing list