February 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1467) Create a set of Koans for using Compensations

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1467: ----------------------------------- Summary: Create a set of Koans for using Compensations Key: JBTM-1467 URL: https://issues.jboss.org/browse/JBTM-1467 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: TXFramework, XTS Reporter: Paul Robinson In the spirit of http://rubykoans.com/, but to learn how to use compensations. In the long term we should use a Java EE Koan 'runner'. In the short term, try using Arquillian with some broken tests. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-986) Automatically setup the client side handler chain

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-986?page=com.atlassian.jira.plugin.s... ] Work on JBTM-986 started by Gytis Trikleris. > Automatically setup the client side handler chain > ------------------------------------------------- > > Key: JBTM-986 > URL: https://issues.jboss.org/browse/JBTM-986 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Labels: assign > Fix For: 5.0.0.M2 > > Original Estimate: 4 days > Time Spent: 1 week, 2 hours > Remaining Estimate: 2 hours > > When invoking a WS-AT or WS-BA Web service, the client side handler has to be added to the client stub to manage transaction context propagation. The code required to do this is as follows: > {code} > BindingProvider bindingProvider = (BindingProvider) client; > List<Handler> handlers = new ArrayList<Handler>(1); > handlers.add(new JaxWSHeaderContextProcessor()); > bindingProvider.getBinding().setHandlerChain(handlers); > {code} > This is not very user friendly. > This could be done using a JAX-WS feature passed to the Client-side port. > We also need to support client stubs created using @WebServiceRef. Here's some examples of its use: > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > The feature should be "enabled" by default providing the feature is enabled in the XTS server config. > The quickstarts also need updated to use this. -- 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, 3 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: -------------------------------- Priority: Minor (was: Major) > 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: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M2 > > Original Estimate: 1 day > Time Spent: 2 hours > Remaining Estimate: 1 day, 4 hours > > h2. Create: > * JTAtoWSTXFeature > * Configuration option on the XTS Subsytem. Lets call it "ByDefaultBridgeFromJTA" for now, subject to change. > h2. Semantics: > h4. JTAtoWSTXFeature absent, ByDefaultBridgeFromJTA absent (Default OOTB) > 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. > h4. JTAtoWSTXFeature absent, ByDefaultBridgeFromJTA present > 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. > h4. JTAtoWSTXFeature enabled, ByDefaultBridgeFromJTA absent > 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. > h5. JTAtoWSTXFeature disabled, ByDefaultBridgeFromJTA present > 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: > # <propagateByDefault/> or <propagateByDefault bridgeJTAByDefault='false'/> > Just do [JBTM-986]. > # <propagateByDefault bridgeJTAByDefault='true'/> > 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. > # No propagateByDefault Element > Config absent. 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. > 'bridgeJTAByDefault' is an attribute of 'propagateByDefault' as 'bridgeJTAByDefault' depends on 'propagateByDefault' being present. > h5. Bridge handler > Two handlers that delegate to the existing TXBridge handler: > # Disabled by default. Only invokes the TXBridge handler if the JTAtoWSTXFeature is present and enabled. > # Enabled by default. Always invokes the TXBridge handler unless the JTAtoWSTXFeature is present and disabled. > If the bridge detects the JTAtoWSTXFeature, but no WSTXFeature, it adds the WSTXFeature to the invocation context (setting WSTXFeature.enabled = JTAtoWSTXFeature.enabled). This is needed by the WSTX handler and prevents the developer from having to add both. > h5. Existing handler changes > We may need to change the TXBridge handler to tolerate the scenario where no JTA transaction is present. Fail silently if JTAtoWSTXFeature missing, but throw an Exception if JTAtoWSTXFeature is set. It is assumed that if the port has JTAtoWSTXFeature enabled, there should be a JTA transaction in place. This matches the the current semantics: if the developer adds the TXBridge handler, throw an Exception if no JTA present. This also allows the developer to add a sanity check (set the JTAtoWSTXFeature) to make sure that the call is only ever called in the context of a JTA transaction. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1227) StAX is not available on Android

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1227?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-1227: --------------------------------------- In order to make life easier for the users and not require them to modify android tools, ArjunaCore has to be modified. PropertiesFactory is the only class in ArjunaCore which uses StAX API, therefore not many changes are needed. Following commit solves the StAX problem in Android (and other devices which do not have this API and require to use ArjunaCore): https://github.com/Gytis/narayana/commit/368ec8dfe063e8dd1a2c44f3122ea5ff... > StAX is not available on Android > -------------------------------- > > Key: JBTM-1227 > URL: https://issues.jboss.org/browse/JBTM-1227 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Common > Affects Versions: 4.16.4, 5.0.0.M1 > Environment: Android 2.3.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.0.0.Final > > > StAX is not available. Since we use it for property configuration, the system fails to run unmodified. There is an equivalent implementation (XmlPullParser) but it is likely other JBoss projects will suffer from this issue. > See http://www.ibm.com/developerworks/library/x-android/ for more details. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1466) The REST-AT implementation needs its own abstract record type

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1466?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1466: ----------------------------------- Remember not to backport this change to the 4.x tree though. > The REST-AT implementation needs its own abstract record type > ------------------------------------------------------------- > > Key: JBTM-1466 > URL: https://issues.jboss.org/browse/JBTM-1466 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST > Affects Versions: 5.0.0.M2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.0.M2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The REST-AT implementation is using a user-defined record type RecordType.USER_DEF_FIRST0 but it should be using its own predefined type. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1466) The REST-AT implementation needs its own abstract record type

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1466: -------------------------------------- Summary: The REST-AT implementation needs its own abstract record type Key: JBTM-1466 URL: https://issues.jboss.org/browse/JBTM-1466 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: REST Affects Versions: 5.0.0.M2 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.0.0.M2 The REST-AT implementation is using a user-defined record type RecordType.USER_DEF_FIRST0 but it should be using its own predefined type. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1441) Create a version of the XTS demo using TXFramework

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1441?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1441: -------------------------------- Assignee: (was: Paul Robinson) > Create a version of the XTS demo using TXFramework > -------------------------------------------------- > > Key: JBTM-1441 > URL: https://issues.jboss.org/browse/JBTM-1441 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Paul Robinson > Fix For: 5.0.0.M2 > > Original Estimate: 1 week > Remaining Estimate: 1 week > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1441) Create a version of the XTS demo using TXFramework

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1441?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1441: -------------------------------- Fix Version/s: (was: 5.0.0.M2) > Create a version of the XTS demo using TXFramework > -------------------------------------------------- > > Key: JBTM-1441 > URL: https://issues.jboss.org/browse/JBTM-1441 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Paul Robinson > Original Estimate: 1 week > Remaining Estimate: 1 week > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1364) Migrate "REST-AT to JTA" bridge into TXBridge component

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1364?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1364: -------------------------------- Fix Version/s: (was: 5.0.0.M2) > Migrate "REST-AT to JTA" bridge into TXBridge component > ------------------------------------------------------- > > Key: JBTM-1364 > URL: https://issues.jboss.org/browse/JBTM-1364 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, REST, TxBridge > Reporter: Paul Robinson > Priority: Minor > Labels: assign > Original Estimate: 1 week > Remaining Estimate: 1 week > > The task is to the work Gytis did on his internship and migrate it into the TXBridge project. > Tasks: > 1. Review the current solution looking for: > 1.1 Major issues that prevent an initial release > 1.2 Test coverage > 2. Make any required changes > 3. Merge into the TXBridge project > 4. Migrate the quickstarts accross > 5. Create a blog post > 5.1 Consider what the end user will need to do to use this technology. We may want to wait until REST-AT and this Bridge are shipped with a Narayana build of AS7. Otherwise the steps to get this working could be rather lengthy. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1074) Deploy REST-AT artifacts to the jboss nexus

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1074?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1074: -------------------------------- Fix Version/s: (was: 5.0.0.M2) > Deploy REST-AT artifacts to the jboss nexus > ------------------------------------------- > > Key: JBTM-1074 > URL: https://issues.jboss.org/browse/JBTM-1074 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Affects Versions: 5.0.0.M1 > Reporter: Michael Musgrove > Priority: Minor > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > We have had a community member asking for the rest module artifacts to be available via the jboss repo -- 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, 3 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 February 2013