February 2013 - jbossts-issues - Jboss List Archives

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

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1447?focusedWorklogId=12428725&page=... ] Gytis Trikleris logged work on JBTM-1447: ----------------------------------------- Author: Gytis Trikleris Created on: 26/Feb/13 2:32 PM Start Date: 26/Feb/13 9:00 AM Worklog Time Spent: 6 hours Issue Time Tracking ------------------- Remaining Estimate: 6 hours (was: 1 day, 4 hours) Time Spent: 1 day (was: 2 hours) Worklog Id: (was: 12428725) > 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

12 years, 10 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?focusedWorklogId=12428726&page=c... ] Gytis Trikleris logged work on JBTM-986: ---------------------------------------- Author: Gytis Trikleris Created on: 26/Feb/13 2:32 PM Start Date: 25/Feb/13 5:00 AM Worklog Time Spent: 1 day Issue Time Tracking ------------------- Remaining Estimate: 4 hours (was: 1 day, 7 hours, 30 minutes) Time Spent: 1 week, 4 days, 1 hour, 30 minutes (was: 1 week, 3 days, 1 hour, 30 minutes) Worklog Id: (was: 12428726) > 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, 4 days, 1 hour, 30 minutes > Remaining Estimate: 4 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1391) Prepare a blog post to introduce API changes for *-AT and Compensations

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1391?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1391: -------------------------------- Summary: Prepare a blog post to introduce API changes for *-AT and Compensations (was: Prepare a blog post to introduce the TXFramework) > Prepare a blog post to introduce API changes for *-AT and Compensations > ----------------------------------------------------------------------- > > Key: JBTM-1391 > URL: https://issues.jboss.org/browse/JBTM-1391 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > Original Estimate: 2 days > Time Spent: 1 day, 2 hours, 40 minutes > Remaining Estimate: 3 hours > -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1366) Create an XTS plugin for the Arquillian Transaction Extension

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1366?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1366: ------------------------------------- Just wondering if this should be in the Arquillian Transaction Extension Jira instance rather than here? > Create an XTS plugin for the Arquillian Transaction Extension > ------------------------------------------------------------- > > Key: JBTM-1366 > URL: https://issues.jboss.org/browse/JBTM-1366 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1492) Create a blog post on Compensations

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1492: ----------------------------------- Summary: Create a blog post on Compensations Key: JBTM-1492 URL: https://issues.jboss.org/browse/JBTM-1492 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, XTS Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M3 Covering: What are compensations When to use them What support we have in TS What plans we have in the future -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1480) On using hornetq object store native libraries are loaded automatically - it should be configurable

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1480?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1480: -------------------------------- Issue Type: Enhancement (was: Feature Request) > On using hornetq object store native libraries are loaded automatically - it should be configurable > --------------------------------------------------------------------------------------------------- > > Key: JBTM-1480 > URL: https://issues.jboss.org/browse/JBTM-1480 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Configuration > Affects Versions: 4.17.3 > Reporter: Ondřej Chaloupka > Assignee: Tom Jenkinson > > Currently when HornetQ implementation of object store is used and native libraries (AIO) are available the native are used without user's explicit request. > It was decided that user should have possibility to define whether the native libraries will be used or not. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1009) Ensure that the Object Store header for action records is the first item to be packed

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1009?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1009: -------------------------------- Issue Type: Enhancement (was: Feature Request) > Ensure that the Object Store header for action records is the first item to be packed > ------------------------------------------------------------------------------------- > > Key: JBTM-1009 > URL: https://issues.jboss.org/browse/JBTM-1009 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 4.16.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.Final > > > Clone of https://issues.jboss.org/browse/JBTM-1008 but targeted at trunk: > Some action classes call super.save_state after save their own state which results in the record header being packed at arbitrary locations within the record. Ideally the tooling (ObjStoreBrowser) would like to read the header without having to know the specific class responsible for the record. > The equivalent fix for 4.16.0.Final was a quick fix to force offending classes to save/restore the parent classes state before the specific state. A more versatile solution is desirable for trunk, for example change the extension point (for saving state) from say save_state to save_state_impl and provide a final implementation of save_state in StateManager that calls out the classes implementation of save_state_impl after packing the header. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-809) Replace transactional driver with ironjacamar

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-809?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-809: ------------------------------- Issue Type: Feature Request (was: Enhancement) > Replace transactional driver with ironjacamar > --------------------------------------------- > > Key: JBTM-809 > URL: https://issues.jboss.org/browse/JBTM-809 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Resource Manager > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.Final > > > The general approach would be along the lines of: > Startup > ====== > Embedded embedded = EmbeddedFactory.create(); > embedded.startup(); > embedded.deploy(new File("my-rar.rar").toURI().toURL()); > embedded.deploy(new File("my-ds.xml").toURI().toURL()); > In use > ===== > InitialContext initialContext = new InitialContext(); > UserTransaction ut = (UserTransaction)initialContext.lookup("UserTransaction"); > DataSource dataSource = (DataSource)initialContext.lookup("java:/"+"TestDS"); > Shutdown > ======= > embedded.undeploy(new File("my-ds.xml").toURI().toURL()); > embedded.undeploy(new File("my-rar.rar").toURI().toURL()); > embedded.shutdown(); // does not work - some threads don't stop > Problems? > ========= > JCA transitive dependencies? > Accessing ds files from war? > Accessing rar from war? > May have to provide these both upfront. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1491) Remove RTS deps from XTS subsystem

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1491: ----------------------------------- Summary: Remove RTS deps from XTS subsystem Key: JBTM-1491 URL: https://issues.jboss.org/browse/JBTM-1491 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Application Server Integration, XTS Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-845) Infinispan ObjectStore

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-845?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-845: ------------------------------- Issue Type: Feature Request (was: Enhancement) > Infinispan ObjectStore > ---------------------- > > Key: JBTM-845 > URL: https://issues.jboss.org/browse/JBTM-845 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.Final > > > Create an objectstore that uses inifinispan for replication of volatile data -- 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

12 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues February 2013