August 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2731) Fix update_jira.py script

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2731?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2731: -------------------------------- Fix Version/s: 5.3.4.Final (was: 5.next) > Fix update_jira.py script > ------------------------- > > Key: JBTM-2731 > URL: https://issues.jboss.org/browse/JBTM-2731 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.3.4.Final > > > WFLY project used to have an issue type with the typo ("Component Upgrade" with double space). It seems to have been fixed, so typo should be removed from the script too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2731) Fix update_jira.py script

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2731?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Tom Jenkinson created pull request #1052 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Fix update_jira.py script > ------------------------- > > Key: JBTM-2731 > URL: https://issues.jboss.org/browse/JBTM-2731 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.3.4.Final > > > WFLY project used to have an issue type with the typo ("Component Upgrade" with double space). It seems to have been fixed, so typo should be removed from the script too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2731) Fix update_jira.py script

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2731?page=com.atlassian.jira.plugin.... ] Gytis Trikleris reassigned JBTM-2731: ------------------------------------- Assignee: Tom Jenkinson (was: Gytis Trikleris) > Fix update_jira.py script > ------------------------- > > Key: JBTM-2731 > URL: https://issues.jboss.org/browse/JBTM-2731 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.next > > > WFLY project used to have an issue type with the typo ("Component Upgrade" with double space). It seems to have been fixed, so typo should be removed from the script too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2731) Fix update_jira.py script

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2731: ------------------------------------- Summary: Fix update_jira.py script Key: JBTM-2731 URL: https://issues.jboss.org/browse/JBTM-2731 Project: JBoss Transaction Manager Issue Type: Task Components: Build System Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next WFLY project used to have an issue type with the typo ("Component Upgrade" with double space). It seems to have been fixed, so typo should be removed from the script too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-223) Check WL-to-JBossTS interoperability (via JTS).

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-223?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-223: ------------------------------- Fix Version/s: 5.next (was: 5.3.4.Final) > Check WL-to-JBossTS interoperability (via JTS). > ----------------------------------------------- > > Key: JBTM-223 > URL: https://issues.jboss.org/browse/JBTM-223 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Mark Little > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Extensible header structure corba call > key value slot ids > slot for transaction context is not in the well known slot > tx context was not defined so we used the market leader at the time -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2480) Provide documentation of how to integrate with Karaf

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2480?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2480: -------------------------------- Fix Version/s: 5.next (was: 5.3.4.Final) > Provide documentation of how to integrate with Karaf > ---------------------------------------------------- > > Key: JBTM-2480 > URL: https://issues.jboss.org/browse/JBTM-2480 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > This should include recovery information -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1107) Recovery Support in Compensation API

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1107?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1107: -------------------------------- Fix Version/s: 5.next (was: 5.3.4.Final) > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.jboss.org/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Compensations > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > *Background* > Currently Compensations API cannot handle system failures. Transaction state is not persisted in any stage. Thus no handlers will be invoked in case of the system crash. > *Requirements* > # Make handlers persistable (CompensationHandler, ConfirmationHandler, TransactionLoggedHandler). > ## Require Serializable interface. > ## Create PersistableHandler interface (similar to PersistableParticipant in RTS integration). > # Make participant persistable (ParticipantImpl, LocalParticipant, RemoteParticipant). > ## Make transaction identifier persistable (converting it to String should work). > ## Implement PersistableParticipant in ParticipantImpl. > ## Investigate if PARTICIPANT_COUNTERS in ParticipatnImpl have to be updated. > # Make compensation scoped beans persistable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2498) Incomplete BlackTie quickstart documentation

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2498?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2498: -------------------------------- Fix Version/s: 5.next (was: 5.3.4.Final) > Incomplete BlackTie quickstart documentation > -------------------------------------------- > > Key: JBTM-2498 > URL: https://issues.jboss.org/browse/JBTM-2498 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Demonstrator, Documentation > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The BlackTie README.md quickstart files are out of date with respect to running against the latest wildfly. > Ideally, the quickstarts should be standalone (and automatable - run.sh nearly works but not quite) so we need better instructions on how to configure, start and deploy to wildfly. > My ideal quickstart is one from which I can cut lines and paste into a terminal in order to get it working. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1804: -------------------------------- Fix Version/s: 5.next (was: 5.3.4.Final) > JTS remote tests not run and no code coverage > --------------------------------------------- > > Key: JBTM-1804 > URL: https://issues.jboss.org/browse/JBTM-1804 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS, Testing > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The tests in .remote. package for JTS are not run by default. We should consider adding a build option so that they are run (will require some mods to the tests since many of them are client/server based - see associated Readme.txt files); don't run them by default since they will add delay to a normal build. > It would then be beneficial to have them instrumented by emma to get code coverage. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2115) Not all classes are under code coverage

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2115?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2115: -------------------------------- Fix Version/s: 5.next (was: 5.3.4.Final) > Not all classes are under code coverage > --------------------------------------- > > Key: JBTM-2115 > URL: https://issues.jboss.org/browse/JBTM-2115 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.0.1 > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The following poms contain skipped classes for code coverage: > ArjunaCore/arjuna/pom.xml > ArjunaJTA/jdbc/pom.xml > ArjunaJTA/jta/pom.xml > ArjunaJTA/spi/pom.xml > XTS/localjunit/pom.xml > We should aim to test everything -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues August 2016