March 2013 - jbossts-issues - Jboss List Archives

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1398?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-1398: ----------------------------------- Assignee: Tom Jenkinson > 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: Tom Jenkinson > 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-887) Simple WS-AT recovery quickstart

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-887?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-887: ------------------------------- Assignee: (was: Tom Jenkinson) > Simple WS-AT recovery quickstart > -------------------------------- > > Key: JBTM-887 > URL: https://issues.jboss.org/browse/JBTM-887 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > > This quickstart shows what happens when a participant fails at various points in the protocol. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-887) Simple WS-AT recovery quickstart

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-887?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-887: ------------------------------- Comment: was deleted (was: Hi [~paul.robinson] please can you mark this as "stop progress" to move this back to open, unless you are working on it, in which case you need to assign it back to yourself, thanks) > Simple WS-AT recovery quickstart > -------------------------------- > > Key: JBTM-887 > URL: https://issues.jboss.org/browse/JBTM-887 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > > This quickstart shows what happens when a participant fails at various points in the protocol. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-887) Simple WS-AT recovery quickstart

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-887?page=com.atlassian.jira.plugin.s... ] Work on JBTM-887 stopped by Tom Jenkinson. > Simple WS-AT recovery quickstart > -------------------------------- > > Key: JBTM-887 > URL: https://issues.jboss.org/browse/JBTM-887 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Tom Jenkinson > > This quickstart shows what happens when a participant fails at various points in the protocol. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-887) Simple WS-AT recovery quickstart

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-887?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson reassigned JBTM-887: ---------------------------------- Assignee: Tom Jenkinson > Simple WS-AT recovery quickstart > -------------------------------- > > Key: JBTM-887 > URL: https://issues.jboss.org/browse/JBTM-887 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Tom Jenkinson > > This quickstart shows what happens when a participant fails at various points in the protocol. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1266) Upload 2012 version of training material

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1266?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1266: -------------------------------- Affects Version/s: 4.16.4 > Upload 2012 version of training material > ---------------------------------------- > > Key: JBTM-1266 > URL: https://issues.jboss.org/browse/JBTM-1266 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 4.16.4 > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Attachments: txCompletion > > -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1368) Allow multiple JDBC Object Store jobs to run concurrently by using a table prefix (perhaps the job name)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1368?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1368: -------------------------------- Fix Version/s: (was: 4.17.4) > Allow multiple JDBC Object Store jobs to run concurrently by using a table prefix (perhaps the job name) > -------------------------------------------------------------------------------------------------------- > > Key: JBTM-1368 > URL: https://issues.jboss.org/browse/JBTM-1368 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Tom Jenkinson > Assignee: Ondřej Chaloupka > Priority: Minor > Fix For: 5.0.0.Final > > -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1266) Upload 2012 version of training material

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1266?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1266: -------------------------------- Fix Version/s: (was: 4.16.7) > Upload 2012 version of training material > ---------------------------------------- > > Key: JBTM-1266 > URL: https://issues.jboss.org/browse/JBTM-1266 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Attachments: txCompletion > > -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1505) WS-BA transaction context not propagated if JTA transaction present.

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1505: ----------------------------------- Summary: WS-BA transaction context not propagated if JTA transaction present. Key: JBTM-1505 URL: https://issues.jboss.org/browse/JBTM-1505 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: TxBridge, XTS Reporter: Paul Robinson Assignee: Gytis Trikleris Fix For: 5.0.0.M3 With default-context-propagation enabled: What happens if the Client is running in a JTA transaction, then begins a WS-BA transaction before calling a WS-BA enabled service? I suspect, as it stands, we would start a WS-AT transaction as well. This will cause the JaxBaseHeaderContextProcessor to default to WS-AT as it appears first in the if-then-elseif block: {code} final CoordinationContextType coordinationContext ; if (atContext != null) { coordinationContext = atContext.getCoordinationContext() ; } else if (baContext != null) { coordinationContext = baContext.getCoordinationContext() ; } {code} I'm not yet sure how we handle this case. We certainly need a test for it though. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1447) Create WebserviceFeature for TXBridge

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1447?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1447: -------------------------------- Comment: was deleted (was: What happens if the Client is running in a JTA transaction, then begins a WS-BA transaction before calling a WS-BA enabled service? I suspect, as it stands, we would start a WS-AT transaction as well. This will cause the JaxBaseHeaderContextProcessor to default to WS-AT as it appears first in the if-then-elseif block: {code} final CoordinationContextType coordinationContext ; if (atContext != null) { coordinationContext = atContext.getCoordinationContext() ; } else if (baContext != null) { coordinationContext = baContext.getCoordinationContext() ; } {code} I'm not yet sure how we handle this case. We certainly need a test for it though. ) > Create WebserviceFeature for TXBridge > ------------------------------------- > > Key: JBTM-1447 > URL: https://issues.jboss.org/browse/JBTM-1447 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: TxBridge > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M2 > > Original Estimate: 1 day > Time Spent: 1 day > Remaining Estimate: 6 hours > > h2. Create: > * JTAOverWSATFeature > * Configuration option on the XTS Subsytem (defaultContextPropagation) > h2. Semantics: > h4. JTAOverWSATFeature absent, defaultContextPropagation disabled > This is the current OOTB experience for EAP 5&6. No handlers are activated automatically. The developer has to add them manually for all ports. When the developer does add the handlers, the MustUnderstand attribute of the WS-TX context is set to true. > h4. JTAOverWSATFeature absent, defaultContextPropagation enabled (Default OOTB) > All Web service requests that are made in the context of a JTA transaction will be bridged to WS-AT and the WS-AT context added to the request soap header. MustUnderstand is set to false. > h4. JTAOverWSATFeature enabled, defaultContextPropagation disabled > All Web service requests, for this port, that are made in the context of a JTA transaction will be bridged to WS-AT and the WS-AT context added to the request soap header. MustUnderstand is set to true. > h5. JTAOverWSATFeature disabled, defaultContextPropagation enabled > All Web service requests, for this port, don't bridge JTA. > h2. Implementation > The XTS Subsystem reads its config on boot. It carries out one of the following actions depending on what it finds: > # <defaultContextPropagation enabled=”true” /> (default OOTB config) > Add the Bridge handler initialized to be enabled by default then do [JBTM-986] after. Ensure that the Bridge handler is invoked before the WSTX handler. > # <defaultContextPropagation enabled=”false” /> > Add the Bridge handler initialized to be disabled by default then do [JBTM-986] after. Ensure that the Bridge handler is invoked before the WSTX handler. > # Config absent. > Error. Fail config parse. > h5. Bridge handler > Two handlers that delegate to the existing TXBridge handler: > # Disabled by default. Only invokes the TXBridge handler if the JTAOverWSATFeature is present and enabled. > # Enabled by default. Always invokes the TXBridge handler unless the JTAOverWSATFeature is present and disabled. > If the bridge detects the JTAOverWSATFeature, but no WSTXFeature, it adds the WSTXFeature to the invocation context (setting WSTXFeature.enabled = JTAOverWSATFeature.enabled). This is needed by the WSTX handler and prevents the developer from having to add both. > h5. Backwards compatibility > Existing applications (written before this feature was released) will be specifying Handler chains manually via the binding provider. Therefore we need to tolerate the situation where these handlers are added twice. Once for by this feature and again by the developer. > In particular the handlers added by this feature and [JBTM-986] should do nothing if the com.arjuna.mw.wst11.client.JaxWSHeaderContextProcessor handler is already in the handler chain. We could achieve this by adding this handler in the post handler chain. We could then look for an existing WSTX header and do nothing if we find it. This is just a suggestion, there may be a better way to achieve this behaviour. -- 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

11 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues March 2013