February 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-312) Add clustering support

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-312?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-312: ------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.M3) > Add clustering support > ---------------------- > > Key: JBTM-312 > URL: https://issues.jboss.org/browse/JBTM-312 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA, JTS, Recovery, Transaction Core, XTS > Affects Versions: 4.3.0.BETA2 > Reporter: Mark Little > Assignee: Tom Jenkinson > Fix For: 6.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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-979) Support REST-JDI protocol in the TXFramework

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-979?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-979: ------------------------------- Fix Version/s: 6.0.0.Final > Support REST-JDI protocol in the TXFramework > --------------------------------------------- > > Key: JBTM-979 > URL: https://issues.jboss.org/browse/JBTM-979 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Labels: TXFramework > Fix For: 6.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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-410) implement mixed outcome support for XTS

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-410?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-410: ------------------------------- Fix Version/s: 6.0.0.Final > implement mixed outcome support for XTS > --------------------------------------- > > Key: JBTM-410 > URL: https://issues.jboss.org/browse/JBTM-410 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XTS > Affects Versions: 4.4.0.GA > Reporter: Jonathan Halliday > Fix For: 6.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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1496) Transaction Monitoring and Analysis

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1496?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1496: -------------------------------- Fix Version/s: 6.0.0.Final > Transaction Monitoring and Analysis > ----------------------------------- > > Key: JBTM-1496 > URL: https://issues.jboss.org/browse/JBTM-1496 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tooling > Reporter: Paul Robinson > Fix For: 6.0.0.Final > > > Details here: > https://community.jboss.org/wiki/TransactionMonitoringAndVisualization > First step is to create a simple prototype to demonstrate the potential. This will help justify resource to do it properly. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1449) Transactions in the browser

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1449?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1449: -------------------------------- Fix Version/s: 6.0.0.Final > Transactions in the browser > --------------------------- > > Key: JBTM-1449 > URL: https://issues.jboss.org/browse/JBTM-1449 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: jhalli > Labels: student > Fix For: 6.0.0.Final > > > Student project that we are not currently offering: > {quote} > Recent developments in web standards (HTML5, specifically Web Storage a.k.a. DOM Storage) indicates a move towards widespread availability of client (i.e. web browser) side persistent storage accessible by web applications. Initially useful for making content and applications available offline, this also open up the possibility of object replication between client and server. In this project you will explore the applicability of transaction concepts to applications built on this model. In particular, you will focus on identifying and exploiting new opportunities made available by the existence of persistent storage on the browser, a vital pre-requisite for recoverable transactions. > To undertake this project you should have a strong interest in web based applications, some javascript programming experience and a basic understanding of transactions concepts. Previous experience of at least one javascript framework would be an advantage. The work will be open source. > {quote} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1450) Transaction processing in javascript

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1450?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1450: -------------------------------- Fix Version/s: 6.0.0.Final > Transaction processing in javascript > ------------------------------------ > > Key: JBTM-1450 > URL: https://issues.jboss.org/browse/JBTM-1450 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: jhalli > Labels: student > Fix For: 6.0.0.Final > > > Student project that we are not currently offering: > {quote} > Increasingly sophisticated applications are being implemented using the javascript language. Initially popular for browser based environments, the language is also gaining traction on the server side (NodeJS, etc). A single threaded model promotes use of callbacks and asynchronous I/O operations. Ongoing standardization work is starting to provide APIs for enterprise functionality (commonJS, IndexedDB, etc). The Rhino javascript engine allows javascript to run on any JVM. These factors lead to situations where distributed business applications may be written wholly or partially in javascript and may need to interact with existing business logic or services implemented in Java. In this project you will consider how to provide transaction management capabilities to such applications. > This project will require a good knowledge of javascript programming, ideally encompassing a server side javascript environment. Candidates should also possess some knowledge of Java and transaction concepts. The work will be open source. > {quote} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-223) Check WL-to-JBossTS interoperability (via JTS).

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-223?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-223: ------------------------------- Fix Version/s: 6.0.0.Final > Check WL-to-JBossTS interoperability (via JTS). > ----------------------------------------------- > > Key: JBTM-223 > URL: https://issues.jboss.org/browse/JBTM-223 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTS > Reporter: Mark Little > Assignee: Mark Little > Fix For: 6.0.0.Final > > > Extensible header structure corba call > key value slot ids > slot for transaction context is not in the well known slot > tx context was not defined so we used the market leader at the time -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-622) Support for crash recovery of tx-inflow with multiple resource managers

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-622?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-622: ------------------------------- Fix Version/s: 6.0.0.Final > Support for crash recovery of tx-inflow with multiple resource managers > ----------------------------------------------------------------------- > > Key: JBTM-622 > URL: https://issues.jboss.org/browse/JBTM-622 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA, Recovery, Transaction Core > Affects Versions: 4.2.3.CP06 > Reporter: Toshiya Kobayashi > Priority: Minor > Fix For: 6.0.0.Final > > > JCA tx-inflow spec allows the external EIS to provide the Xid for the inflowed transaction. The TM handling the inflowed (i.e. subordinate) transaction uses this Xid verbatim when talking to RMs. > In current implementation, each RM enlisted in the subordinate tx will see the same Xid as originally provided by the EIS. This screws recovery where multiple resources are involved, since a given Xid no longer belongs to exactly one RM, but may be shared by several. We can no longer return a single XAResource to drive the recovery for a given Xid. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1495) Merge in BlackTie

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1495?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1495: -------------------------------- Issue Type: Feature Request (was: Enhancement) > Merge in BlackTie > ----------------- > > Key: JBTM-1495 > URL: https://issues.jboss.org/browse/JBTM-1495 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.Final > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Docs, code, forums, chat room (motd), Jira, web pages -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1496) Transaction Monitoring and Analysis

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1496?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1496: -------------------------------- Assignee: (was: Michael Musgrove) > Transaction Monitoring and Analysis > ----------------------------------- > > Key: JBTM-1496 > URL: https://issues.jboss.org/browse/JBTM-1496 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tooling > Reporter: Paul Robinson > > Details here: > https://community.jboss.org/wiki/TransactionMonitoringAndVisualization > First step is to create a simple prototype to demonstrate the potential. This will help justify resource to do it properly. -- 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, 10 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