Consider allowing JDBCImple to manage connection lifecycles
-----------------------------------------------------------
Key: JBTM-465
URL: https://jira.jboss.org/jira/browse/JBTM-465
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.5
Reporter: Mark Little
Fix For: future
JDBCImple assumes that the JDBCAccess class manages the lifecycle of connections it returns.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Document static initializers
----------------------------
Key: JBTM-589
URL: https://jira.jboss.org/jira/browse/JBTM-589
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JTA, JTS, Recovery, Transaction Core, XTS
Affects Versions: 4.7.0
Reporter: Mark Little
Assignee: Mark Little
Fix For: future
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Add clustering support
----------------------
Key: JBTM-312
URL: http://jira.jboss.com/jira/browse/JBTM-312
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JTA Implementation, JTS Implementation, Recovery, Transaction Core, WS-T Implementation
Affects Versions: 4.3.0.BETA2
Reporter: Mark Little
Assigned To: Mark Little
--
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
Implement REST-tx specifications
--------------------------------
Key: JBTM-747
URL: https://jira.jboss.org/browse/JBTM-747
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: REST, TxBridge
Reporter: Mark Little
Assignee: Michael Musgrove
Fix For: 5.0.0
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Remove static initializers
--------------------------
Key: JBTM-846
URL: https://issues.jboss.org/browse/JBTM-846
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: Tom Jenkinson
Assignee: Tom Jenkinson
Fix For: 5.0.0.M1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Infinispan ObjectStore
----------------------
Key: JBTM-845
URL: https://issues.jboss.org/browse/JBTM-845
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: Tom Jenkinson
Create an objectstore that uses inifinispan for replication of volatile data
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Remove log4j.properties from jbossjts.jar
-----------------------------------------
Key: JBTM-738
URL: https://jira.jboss.org/jira/browse/JBTM-738
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Configuration
Affects Versions: 4.9.0
Reporter: Jesper Pedersen
Priority: Minor
The archive jbossjts.jar contains a log4j.properties file, which creates a transaction.log file.
It can be disabled by specifying -Dlog4j.defaultInitOverride=true, but that is not always possible for some Ant tasks, like checkstyle. Hence an empty file is created.
It would nice to have the logging configuration outside of the archive.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Generic compensation annotations
--------------------------------
Key: JBTM-248
URL: http://jira.jboss.com/jira/browse/JBTM-248
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JTA Implementation
Affects Versions: 4.2.3.SP5
Reporter: Mark Little
Assigned To: Mark Little
We're working on WS-BA based compensation annotations. That's great, but can we refactor so that we can support compensations outside of WS-BA? ArjunaCore can support compensations without Web Services. Maybe the WS-BA annotations vanish entirely, or collapse down to a subset of what currently exists to support what is truly unique about WS-BA?
--
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
get.drivers task in qa/build.xml is failing due to "java.net.UnknownHostException: reports.qa.atl.jboss.com
-----------------------------------------------------------------------------------------------------------
Key: JBTM-838
URL: https://issues.jboss.org/browse/JBTM-838
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Testing
Affects Versions: 4.6.1.CP11, 4.15.0
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Fix For: 4.6.1.CP12, 4.15.1
There has been a change in a lot of domain names recently and all the atl.jboss.com domains have been decommissioned.
Hence, the get.drivers target in qa/build.xml needs to be updated with a new domain name.
The domain name corresponding to the reports.qa.atl.jboss.com is now www.qa.jboss.com.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Mavenize JBoss Transactional File IO project
--------------------------------------------
Key: JBTM-651
URL: https://jira.jboss.org/jira/browse/JBTM-651
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: jaikiran pai
JBoss Transactional File IO project http://www.jboss.org/jbosstm/fileio/ currently is not available in the Maven repo. Making it available in the Maven repo would help other (Maven based) projects to easily consume it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira