February 2010 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-465) Consider allowing JDBCImple to manage connection lifecycles

by Mark Little (JIRA)

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

11 years, 12 months

3
13
0 / 0

[JBoss JIRA] Created: (JBTM-589) Document static initializers

by Mark Little (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

11 years, 12 months

2
13
0 / 0

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

by Mark Little (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

11 years, 12 months

5
10
0 / 0

[JBoss JIRA] Created: (JBTM-248) Generic compensation annotations

by Mark Little (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

12 years, 1 month

4
6
0 / 0

[JBoss JIRA] Created: (JBTM-651) Mavenize JBoss Transactional File IO project

by jaikiran pai (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

12 years, 1 month

5
16
0 / 0

[JBoss JIRA] Created: (JBTM-247) Update (if necessary) the new integration layer SPIs

by Mark Little (JIRA)

Update (if necessary) the new integration layer SPIs ---------------------------------------------------- Key: JBTM-247 URL: http://jira.jboss.com/jira/browse/JBTM-247 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation Reporter: Mark Little Assigned To: Jonathan Halliday http://anonsvn.jboss.org/repos/jbossas/projects/integration/ -- 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

12 years, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (JBTM-520) Include distribution information in MANIFEST.MF

by Jesper Pedersen (JIRA)

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.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

12 years, 1 month

4
14
0 / 0

[JBoss JIRA] Created: (JBTM-314) JDBCStore.getJDBCClass does not work for some JDBC drivers

by Jeremy Stone (JIRA)

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(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

12 years, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (JBTM-527) Adding PMD to build system

by Romain PELISSE (JIRA)

Adding PMD to build system --------------------------- Key: JBTM-527 URL: https://jira.jboss.org/jira/browse/JBTM-527 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System Affects Versions: future Reporter: Romain PELISSE Priority: Trivial Attachments: adding-pmd-as-qa-tools.patch I have a small patch that offers an integration of PMD (http://pmd.sourceforge.net/) into the current build system of JBoss Transaction. Obviously, this is not an highly important feature request, having PMD checking java code is just nice to have. Anyway, as your project is not likely to integrate this patch quickly, I also published the result of a PMD run on the current source code: http://belaran.eu/jbosstm-pmd.html (this way you can already check what PMD find out without setting up the tool itself) I integrated PMD into the qa/ directory which seems the most appropriate directory at first glance... An other strategy would have been to define a "pmd" task inside some common build file ( maybe common/build.xml but it does not look like it), and then have each module call for this anttask with the appropriate java source folder... If you fell this approach is better, please let me know, i'll adapt my patch. All "violation" detected by PMD are not relevant, a pmd report is just a set of hints of something that may be a bad idea or could be improved. PMD rulesets (what kind of violation is looking for) are defined in the qa/pmd.xml. In this file you can easily include/exclude rules, and you can use it to configure the PMD Eclipse Plugin. -- 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

12 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBTM-682) add emma code coverage to build

by Jonathan Halliday (JIRA)

add emma code coverage to build ------------------------------- Key: JBTM-682 URL: https://jira.jboss.org/jira/browse/JBTM-682 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System, Tooling Affects Versions: 4.9.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.10.0 Wire emma to the build system so we can start tracking unit test coverage. http://emma.sourceforge.net/ -- 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

12 years, 1 month

7
25
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues February 2010