March 2008 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBTM-123) Integrate with AS 5.0

by Jonathan Halliday (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-123?page=all ] Jonathan Halliday updated JBTM-123: ----------------------------------- Component/s: WS-T Implementation > Integrate with AS 5.0 > --------------------- > > Key: JBTM-123 > URL: http://jira.jboss.com/jira/browse/JBTM-123 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTS Implementation, JTA Implementation, WS-T Implementation > Affects Versions: 4.2.1 > Reporter: Mark Little > Assigned To: Jonathan Halliday > Fix For: 4.4 > > Time Spent: 2 days > Remaining Estimate: 0 minutes > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBTM-16) JBossWS support

by Andrew Dinn (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-16?page=comments#action_12401995 ] Andrew Dinn commented on JBTM-16: --------------------------------- As of revision 18807 updated demo build instructions ot explain how to build JaxWS-based (default) or JaxRPC-based version of demo and also how to install it either into JBoss 4.2.2.GA and subsequent or into JBoss 5.0Beta4. > JBossWS support > --------------- > > Key: JBTM-16 > URL: http://jira.jboss.com/jira/browse/JBTM-16 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: WS-T Implementation > Reporter: Mark Little > Assigned To: Andrew Dinn > Priority: Blocker > Fix For: 4.4 > > > After the initial release of the newly integrated Arjuna Transaction Service, ensure support for JBossWS. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-342) atsintegration build should support AS 4.2 and 5.0

by Jonathan Halliday (JIRA)

atsintegration build should support AS 4.2 and 5.0 -------------------------------------------------- Key: JBTM-342 URL: http://jira.jboss.com/jira/browse/JBTM-342 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.3.0.BETA2 Reporter: Jonathan Halliday Assigned To: Jonathan Halliday Fix For: 4.3.0.BETA3 The JBossTS 4.3.GA release should support app server integration with AS 4.2 and 5.0. Hence it should likewise build against either. They have different lib structure, so that means tweaking the build.xml lib paths. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-341) Change enum to int for recovery state

by Mark Little (JIRA)

Change enum to int for recovery state ------------------------------------- Key: JBTM-341 URL: http://jira.jboss.com/jira/browse/JBTM-341 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Recovery Reporter: Mark Little Assigned To: Mark Little Fix For: 4.4 Because we're using JDK 1.4 as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-340) If RM is suspended then ignore explicit scan requests

by Mark Little (JIRA)

If RM is suspended then ignore explicit scan requests ----------------------------------------------------- Key: JBTM-340 URL: http://jira.jboss.com/jira/browse/JBTM-340 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Recovery Reporter: Mark Little Assigned To: Mark Little Fix For: 4.4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-288) Add suspend/resume to recovery manager

by Mark Little (JIRA)

Add suspend/resume to recovery manager -------------------------------------- Key: JBTM-288 URL: http://jira.jboss.com/jira/browse/JBTM-288 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.4 Start/Stop are really termination states. No way to restart a recovery manager once it is stopped. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-337) Missing timeout code

by Mark Little (JIRA)

Missing timeout code -------------------- Key: JBTM-337 URL: http://jira.jboss.com/jira/browse/JBTM-337 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTS Implementation Affects Versions: 4.2.3.SP6 Reporter: Mark Little Assigned To: Mark Little /* * Currently send over the original timeout, and not * what is remaining. Will make this configurable until * the specification is clarified. */ But not present in TransactionImple, even though the spec. is clear on this now. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBTM-291) Change default timeout mechanism from NORMAL to DYNAMIC.

by Mark Little (JIRA)

Change default timeout mechanism from NORMAL to DYNAMIC. -------------------------------------------------------- Key: JBTM-291 URL: http://jira.jboss.com/jira/browse/JBTM-291 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Andrew Dinn Fix For: 4.4 MR1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-307) Update xa_prepare handling for rm/err failures in light of modern RMs

by Mark Little (JIRA)

Update xa_prepare handling for rm/err failures in light of modern RMs --------------------------------------------------------------------- Key: JBTM-307 URL: http://jira.jboss.com/jira/browse/JBTM-307 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP6 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.4 Initial RM implementations of XAResources that threw RMERR/RMFAIL on prepare didn't honour the XA spec, so TS had to assume heuristic outcome. That's no longer the case (probably hasn't been for many years). We can/should remove that option in the codebase. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (JBTM-323) TransactionSynchronizationRegistry should not be in JTA 1.0

by Jonathan Halliday (JIRA)

TransactionSynchronizationRegistry should not be in JTA 1.0 ----------------------------------------------------------- Key: JBTM-323 URL: http://jira.jboss.com/jira/browse/JBTM-323 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP6 Reporter: Jonathan Halliday Assigned To: Jonathan Halliday Fix For: 4.2.3.SP8 TransactionSynchronizationRegistryImple is present in the 4.2.3 branch (i.e. JTA 1.0.1b impl) but is really a feature for the JTA 1.1 i.e. TS 4.3+. Its presence in the app server's JNDI is causing problems as the 4.2.3 branch has a non-serializable prototype which does not play nice with JNDI, unlike the finished version in trunk. However, it should not be in JNDI in the first place. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues March 2008