February 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1052) Support Web services with a webservices.xml present in TXFramework

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1052?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1052: -------------------------------- Issue Type: Enhancement (was: Feature Request) > Support Web services with a webservices.xml present in TXFramework > ------------------------------------------------------------------ > > Key: JBTM-1052 > URL: https://issues.jboss.org/browse/JBTM-1052 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: TXFramework > Affects Versions: 5.0.0.M1 > Reporter: Paul Robinson > Priority: Minor > > See: https://community.jboss.org/message/714478#714478 -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-765) Calling activate on XTS object store records cannot be invoked safely from the ObjectStore browser

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-765?page=com.atlassian.jira.plugin.s... ] Paul Robinson updated JBTM-765: ------------------------------- Issue Type: Bug (was: Feature Request) > Calling activate on XTS object store records cannot be invoked safely from the ObjectStore browser > -------------------------------------------------------------------------------------------------- > > Key: JBTM-765 > URL: https://issues.jboss.org/browse/JBTM-765 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tooling, XTS > Affects Versions: 4.11.0 > Reporter: Michael Musgrove > > To enable inspection of XTS records via the ObjectStore browser we need a safe way to activate records (the current implementation of activate causes XTS participants to become eligible for participation in recovery which is a job best left to the recovery manager). -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-981) Annotation support for transaction bridging

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-981?page=com.atlassian.jira.plugin.s... ] Paul Robinson resolved JBTM-981. -------------------------------- Assignee: Paul Robinson Fix Version/s: 5.0.0.M2 Resolution: Partially Completed This is partially complete (see sub-issues). Individual issues wil be created for individual bridging features. > Annotation support for transaction bridging > ------------------------------------------- > > Key: JBTM-981 > URL: https://issues.jboss.org/browse/JBTM-981 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Labels: TXFramework > Fix For: 5.0.0.M2 > > > h2.Vision > The grand plan for this feature is to support near transparent bridging, end-to-end irrespective of what transport and component technology is used. The only caveat being that the transport and component technologies support a compatible transaction model. The basic case would be to always bridge when possible and for this scenario the absolute bare-minimum number of annotations should be used. More specific bridging requirements should be specified through annotations. > h2.Example > This example shows what is considered the default scenario. It requires very few annotations. > # Some client code (A JSF managed bean, for example) has a client to Service1 injected. > # The managed bean begins a transaction somehow. > # Service1 uses WSPolicy to state that it requires a WSAT transaction to be in place. > # Somehow (maybe during injection or when CXF handles the PolicyAssertion) the injected client stub for Service1 has the TXBridge and XTS interceptors configured. > # The managed bean invokes a method on Service1. > # The JTA transaction is bridged to a WS-AT transaction and the Web service request is made. > # Service1 specified by an annotation that it requires a transaction (this was how the WS-Policy assertion was placed in the WSDL) and thus the XTS and TXBridge interceptors are inserted. > # The incoming WS-AT context is detected and bridged onto a JTA transaction. > # Service1 updates a DB and the associated XAResource is enlisted with the JTA transaction. > # Service1 then invokes the client of Service2. > # Service2 does not specify that it requires a WS-AT transaction, via a WS-Policy assertion. Therefore the client to Service2 must be annotated to specify that it requires WS-AT transaction out-flow. > # When invoking a method on the Service2 client it is detected that a WS-AT transaction is already in-place and this is used, rather than bridging again from JTA back to WS-AT. > Similar behaviour should occur for REST and JTS transactions also. > h2.Advanced features > This section describes some of the more advanced features that could be supported. As these features deviate from the default scenario, they are all specified via annotations. > h1. Specific "bridged from" protocol > In the default scenario the transaction protocol bridged from is inferred by the transaction context present when the service is invoked. As a result any supported transaction will enact bridging. Some services may need to limit the types of transactions they bridge from. For example, only enable bridging if a WS-BA transaction is in place prior to service invocation. > h1. Specific "bridged to" protocol > The default is to always bridge to JTA for incoming bridging. However, this could be inefficient if a Web service always invokes another Web service, both requiring WS-AT. There may be other situations where bridging to JTA is not appropriate. > h1. Disable bridging > The service may wish to prevent bridging altogether. For example if no transactional work needs to be done within a different type of 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1415) TXFramework: Allow servlet-name to be anything in web.xml

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1415?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1415: -------------------------------- Issue Type: Enhancement (was: Feature Request) > TXFramework: Allow servlet-name to be anything in web.xml > --------------------------------------------------------- > > Key: JBTM-1415 > URL: https://issues.jboss.org/browse/JBTM-1415 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > > Removes a restriction imposed by JBTM-1408. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1452) Distribution name of 4.17.x is narayana* rather than jbossts*

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1452?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1452: -------------------------------- Assignee: Gytis Trikleris (was: Tom Jenkinson) > Distribution name of 4.17.x is narayana* rather than jbossts* > ------------------------------------------------------------- > > Key: JBTM-1452 > URL: https://issues.jboss.org/browse/JBTM-1452 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.3 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 4.17.4 > > > See https://www.jboss.org/jbosstm/downloads/4_17_3_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

12 years, 1 month

1
0
0 / 0

[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 commented on JBTM-1398: ------------------------------------- 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 > 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 > 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

12 years, 1 month

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 commented on JBTM-887: ------------------------------------ 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

12 years, 1 month

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: -------------------------------- Priority: Minor (was: Major) > 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: 4.17.4, 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1479) Create a quickstart to show how to use IronJacamar and JBTM inside tomcat

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1479?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1479: -------------------------------- Component/s: Demonstrator > Create a quickstart to show how to use IronJacamar and JBTM inside tomcat > ------------------------------------------------------------------------- > > Key: JBTM-1479 > URL: https://issues.jboss.org/browse/JBTM-1479 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M2 > > Attachments: test-ds.xml, transaction.xml > > Original Estimate: 3 days > Time Spent: 6 hours > Remaining Estimate: 2 days, 2 hours > > See JBTM-809 for the algorithm > You might want to put the startup in the context listener: > public class MyServletContextListener implements ServletContextListener { > public void contextInitialized(ServletContextEvent sce) { > // Initialize RecoveryManager > // Initialize TransactionManager > // Initialize IronJacamar > } > > @Override > public void contextDestroyed(ServletContextEvent sce) { > // Clean IronJacamar > // Clean TransactionManager > // Clean RecoveryManager > } > } > Quickstart application should connect to the database (say PostgreSQL), dummy XA resource and coordinate the transaction. The PostgreSQL data source needs to be accessed via IronJacamar. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-264) Improve tooling

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-264?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-264: ------------------------------- Priority: Major (was: Critical) > Improve tooling > --------------- > > Key: JBTM-264 > URL: https://issues.jboss.org/browse/JBTM-264 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 4.2.3.SP5 > Reporter: Mark Little > Assignee: Michael Musgrove > > We need better tools support. -- 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, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues February 2013