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 …
[View More]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
[View Less]
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 …
[View More]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
[View Less]
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 …
[View More]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
[View Less]
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.…
[View More]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
[View Less]
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'…
[View More]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
[View Less]
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 …
[View More]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
[View Less]
Include distribution information in MANIFEST.MF
-----------------------------------------------
Key: JBTM-520
URL: https://jira.jboss.org/jira/browse/JBTM-520
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.6.0
Reporter: Jesper Pedersen
Priority: Minor
It would be nice if the jar files contain information inside the MANIFEST.…
[View More]MF files - like
Implementation-Title
Implementation-Vendor
Implementation-Vendor-Id
Implementation-Version
--
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
[View Less]
JDBCStore.getJDBCClass does not work for some JDBC drivers
----------------------------------------------------------
Key: JBTM-314
URL: http://jira.jboss.com/jira/browse/JBTM-314
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transaction Core
Reporter: Jeremy Stone
Implementation of com.arjuna.ats.internal.arjuna.objectstore.JDBCStore getJDBCClass(…
[View More]Connection) breaks if JDBC driver DatabaseMetaData getDriverName() is not consistent between driver releases or driver implementations (e.g. SQLServer), and tries to load illegally named classes if first word of reported driver name contains illegal characters (e.g. MySql).
Maybe a pluggable strategy for determination of the class should be used instead.
--
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
[View Less]