June 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1479) Create a quickstart to show how to use IronJacamar and JBTM inside tomcat

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1479?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1479: ---------------------------------- Status: Pull Request Sent (was: Coding In Progress) > Create a quickstart to show how to use IronJacamar and JBTM inside tomcat > ------------------------------------------------------------------------- > > Key: JBTM-1479 > URL: https://issues.jboss.org/browse/JBTM-1479 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > Attachments: test-ds.xml, transaction.xml > > Original Estimate: 3 days > Time Spent: 1 week, 2 days, 1 hour, 20 minutes > Remaining Estimate: 0 minutes > > See JBTM-809 for the algorithm > You might want to put the startup in the context listener: > public class MyServletContextListener implements ServletContextListener { > public void contextInitialized(ServletContextEvent sce) { > // Initialize RecoveryManager > // Initialize TransactionManager > // Initialize IronJacamar > } > > @Override > public void contextDestroyed(ServletContextEvent sce) { > // Clean IronJacamar > // Clean TransactionManager > // Clean RecoveryManager > } > } > Quickstart application should connect to the database (say PostgreSQL), dummy XA resource and coordinate the transaction. The PostgreSQL data source needs to be accessed via IronJacamar. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1663) JBossTS - EAP6 productization issue tracker

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1663?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1663: -------------------------------- Fix Version/s: (was: 4.17.5) (was: 5.0.0.M4) > JBossTS - EAP6 productization issue tracker > ------------------------------------------- > > Key: JBTM-1663 > URL: https://issues.jboss.org/browse/JBTM-1663 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.4 > Reporter: Weinan Li > Assignee: Weinan Li > > This is the tracker for all the issues I've found during EAP6 productization process. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1663) JBossTS - EAP6 productization issue tracker

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1663?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1663: ------------------------------------- Hi Weinan, I have assigned this to you as you will know when it is complete. Feel free to assign me any linked issues you would like to. Thanks, Tom > JBossTS - EAP6 productization issue tracker > ------------------------------------------- > > Key: JBTM-1663 > URL: https://issues.jboss.org/browse/JBTM-1663 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.4 > Reporter: Weinan Li > Assignee: Weinan Li > > This is the tracker for all the issues I've found during EAP6 productization process. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1664) Create a profile that contains the components needed by EAP6

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1664?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1664. --------------------------------- Resolution: Out of Date Resolved by JBTM-1669 and JBTM-1670 > Create a profile that contains the components needed by EAP6 > ------------------------------------------------------------ > > Key: JBTM-1664 > URL: https://issues.jboss.org/browse/JBTM-1664 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.4 > Reporter: Weinan Li > Assignee: Tom Jenkinson > Fix For: 4.17.5, 5.0.0.M4 > > > Currently EAP6 need these components: > {code} > jbossts-arjuna > jbossts-arjunacore-services > jbossts-arjunacore > jbossts-bridge > jbossts-common > jbossts-idlj-idl > jbossts-jacorb-idl > jbossts-jbossjts-idlj > jbossts-jbossjts-integration > jbossts-jbossjts-jacorb > jbossts-jbosstxbridge > jbossts-jbossxts > jbossts-jtax > jbossts-jts > jbossts-narayana-jta > jbossts-orbportability > jbossts-recovery > jbossts-restat-api > jbossts-restat-util > jbossts-restat-web > jbossts-txframework > jbossts-txoj > jbossts-ws-c11 > jbossts-ws-t11 > jbossts-wsas > jbossts-wscf11 > jbossts-wstx11 > {code} -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1663) JBossTS - EAP6 productization issue tracker

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1663?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1663: -------------------------------- Assignee: Weinan Li (was: Tom Jenkinson) > JBossTS - EAP6 productization issue tracker > ------------------------------------------- > > Key: JBTM-1663 > URL: https://issues.jboss.org/browse/JBTM-1663 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.4 > Reporter: Weinan Li > Assignee: Weinan Li > Fix For: 4.17.5, 5.0.0.M4 > > > This is the tracker for all the issues I've found during EAP6 productization process. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1664) Create a profile that contains the components needed by EAP6

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1664?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1664: ------------------------------------- To compile those modules: ./build.sh -Didlj-enabled=true (I have assumed jbossts-arjunacore-services was a typo as there is a separate Jira to disable tanuki stuff) > Create a profile that contains the components needed by EAP6 > ------------------------------------------------------------ > > Key: JBTM-1664 > URL: https://issues.jboss.org/browse/JBTM-1664 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.4 > Reporter: Weinan Li > Assignee: Tom Jenkinson > Fix For: 4.17.5, 5.0.0.M4 > > > Currently EAP6 need these components: > {code} > jbossts-arjuna > jbossts-arjunacore-services > jbossts-arjunacore > jbossts-bridge > jbossts-common > jbossts-idlj-idl > jbossts-jacorb-idl > jbossts-jbossjts-idlj > jbossts-jbossjts-integration > jbossts-jbossjts-jacorb > jbossts-jbosstxbridge > jbossts-jbossxts > jbossts-jtax > jbossts-jts > jbossts-narayana-jta > jbossts-orbportability > jbossts-recovery > jbossts-restat-api > jbossts-restat-util > jbossts-restat-web > jbossts-txframework > jbossts-txoj > jbossts-ws-c11 > jbossts-ws-t11 > jbossts-wsas > jbossts-wscf11 > jbossts-wstx11 > {code} -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1526) Add a EAP profile that contains the components required by EAP

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1526?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1526. --------------------------------- Fix Version/s: (was: 4.17.5) (was: 5.0.0.M4) Resolution: Duplicate Issue Duplicate of JBTM-1664 > Add a EAP profile that contains the components required by EAP > -------------------------------------------------------------- > > Key: JBTM-1526 > URL: https://issues.jboss.org/browse/JBTM-1526 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.3 > Reporter: Weinan Li > Assignee: Tom Jenkinson > > Currently narayana has too many dependencies that is disallowed in EAP repo. We could create a profile for EAP6 that just have the necessary modules. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1776) Merge the individual emma code coverage reports

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1776: ----------------------------------- Summary: Merge the individual emma code coverage reports Key: JBTM-1776 URL: https://issues.jboss.org/browse/JBTM-1776 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Build System, Testing Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.0.0.M4 Currently each module will generate its own code coverage report. It would be useful if we can try to work out how to get Emma to either merge the reports or potentially we can see if we can change the location of where emma generates its reports (currently the target folder of each module) to a common location and see if that will will merge the reports automatically. The benefit of this is that certain modules do not contain complete code coverage unit tests and so we appear to have low coverage in some areas but when taken in context with the rest of the project this coverage would be much higher. We should also attempt to get the qa/ runs to generate emma coverage data. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1775) org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote failure wiith JDK orb

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-1775: ------------------------------------- Summary: org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote failure wiith JDK orb Key: JBTM-1775 URL: https://issues.jboss.org/browse/JBTM-1775 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS, Testing Reporter: Gytis Trikleris Assignee: Michael Musgrove Priority: Minor Fix For: 5.0.0.M4 http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-EAP61-jdbcobjectst... -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1774) STM artifactId name potentially ambiguous?

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1774: ----------------------------------- Summary: STM artifactId name potentially ambiguous? Key: JBTM-1774 URL: https://issues.jboss.org/browse/JBTM-1774 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Build System, STM Reporter: Tom Jenkinson Assignee: Mark Little Priority: Optional Most modules that a user is expected to build and use (e.g. XTS, ArjunaCore, the JTA/JTS uber jars) use an aggregate nominative part of the group plus a module-centric name to differentiate them. The problem such that it is, can be seen cleanest in JBTM-1769 (https://github.com/jbosstm/narayana/commit/8ec2ab2375e3efb67489e7702f20c4...). Here the user is suggested to build :core to build STM which is ambiguous in context with the rest of the project in particular ArjunaCore. Can the artifactId be changed to stm-core? or just stm? -- 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, 5 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 June 2013