June 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1610) Typo in method names of SerializableXAResourceDeserializer interface

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1610?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1610. --------------------------------- Resolution: Deferred > Typo in method names of SerializableXAResourceDeserializer interface > -------------------------------------------------------------------- > > Key: JBTM-1610 > URL: https://issues.jboss.org/browse/JBTM-1610 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.3, 5.0.0.M2 > Reporter: jaikiran pai > Assignee: Tom Jenkinson > Priority: Optional > > The 2 methods in SerializableXAResourceDeserializer are named these: > {code} > ... > public boolean canDeserialze(String className); > ... > public XAResource deserialze(ObjectInputStream ois) throws IOException, ClassNotFoundException; > {code} > Notice the typo - a missing "i" in deserialize. > I guess it's too late or a bit too much to change those methods now since that interface might already be in use, in different projects. Hence, marking this JIRA as "Optional" -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1610) Typo in method names of SerializableXAResourceDeserializer interface

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1610?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1610: ------------------------------------- As the meaning is still quite clear, I think it might be easier to just leave these as is, but thanks for the report. I will defer it for now, if this really grates we can reschedule. > Typo in method names of SerializableXAResourceDeserializer interface > -------------------------------------------------------------------- > > Key: JBTM-1610 > URL: https://issues.jboss.org/browse/JBTM-1610 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.3, 5.0.0.M2 > Reporter: jaikiran pai > Assignee: Tom Jenkinson > Priority: Optional > > The 2 methods in SerializableXAResourceDeserializer are named these: > {code} > ... > public boolean canDeserialze(String className); > ... > public XAResource deserialze(ObjectInputStream ois) throws IOException, ClassNotFoundException; > {code} > Notice the typo - a missing "i" in deserialize. > I guess it's too late or a bit too much to change those methods now since that interface might already be in use, in different projects. Hence, marking this JIRA as "Optional" -- 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

10 years, 11 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: ------------------------------------- Hi Weinan, I was under the impression that [~pgier] did not want specific EAP profiles creating? I am happy to create a profile that triggers these modules but as I say, I just want to check it is of use first. Thanks, Tom > 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 > > 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1635) Enhance TRACE for delistResource

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1635?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1635: -------------------------------- Fix Version/s: 5.0.0.M4 > Enhance TRACE for delistResource > -------------------------------- > > Key: JBTM-1635 > URL: https://issues.jboss.org/browse/JBTM-1635 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.17.3 > Reporter: Jesper Pedersen > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.M4 > > > The following > {noformat} > TRACE [com.arjuna.ats.jta] (MSC service thread 1-14) TransactionImple.delistResource > {noformat} > statement would benefit for logging the actual TM flag sent -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1635) Enhance TRACE for delistResource

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1635?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1635: ------------------------------------- Hi Jesper, Do you want me to pretty-print the flag or is the int enough? I don't think you can OR the flags on delist so the int should be enough? Tom > Enhance TRACE for delistResource > -------------------------------- > > Key: JBTM-1635 > URL: https://issues.jboss.org/browse/JBTM-1635 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.17.3 > Reporter: Jesper Pedersen > Assignee: Tom Jenkinson > Priority: Minor > > The following > {noformat} > TRACE [com.arjuna.ats.jta] (MSC service thread 1-14) TransactionImple.delistResource > {noformat} > statement would benefit for logging the actual TM flag sent -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1636) Enhance TRACE for getStatus

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1636?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1636: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/318 Thanks for the FR, Jesper > Enhance TRACE for getStatus > --------------------------- > > Key: JBTM-1636 > URL: https://issues.jboss.org/browse/JBTM-1636 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.17.3 > Reporter: Jesper Pedersen > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.M4 > > > The following > {noformat} > TRACE [com.arjuna.ats.jta] (MSC service thread 1-14) TransactionImple.getStatus > {noformat} > statement would benefit from logging the actual return value sent to the caller -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1636) Enhance TRACE for getStatus

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1636?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1636: -------------------------------- Fix Version/s: 5.0.0.M4 > Enhance TRACE for getStatus > --------------------------- > > Key: JBTM-1636 > URL: https://issues.jboss.org/browse/JBTM-1636 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.17.3 > Reporter: Jesper Pedersen > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.M4 > > > The following > {noformat} > TRACE [com.arjuna.ats.jta] (MSC service thread 1-14) TransactionImple.getStatus > {noformat} > statement would benefit from logging the actual return value sent to the caller -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1551) Empty '.m2/repository/org/jboss/narayana' prior to running CI

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1551?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1551. --------------------------------- Fix Version/s: 5.0.0.M4 (was: 5.0.0.Final) Resolution: Done > Empty '.m2/repository/org/jboss/narayana' prior to running CI > ------------------------------------------------------------- > > Key: JBTM-1551 > URL: https://issues.jboss.org/browse/JBTM-1551 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.M4 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > This ensures that no old artefacts are picked up. > Need to wait for BT to be merged into Narayana as it relies on Narayana artefacts being present in .m2. A failed Narayana build will result in these artefacts being missing. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1551) Empty '.m2/repository/org/jboss/narayana' prior to running CI

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1551?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1551: ------------------------------------- As narayana is much more stable now, I have changed the flow to assume that there will always be a succesfull build of the latest narayana available. Unfortunately we don't deploy the snapshots (at the moment) so it is possible that blacktie will build on a node where narayana has not successfully built or an older version is resident. This should be covered in JBTM-1495 > Empty '.m2/repository/org/jboss/narayana' prior to running CI > ------------------------------------------------------------- > > Key: JBTM-1551 > URL: https://issues.jboss.org/browse/JBTM-1551 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.Final > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > This ensures that no old artefacts are picked up. > Need to wait for BT to be merged into Narayana as it relies on Narayana artefacts being present in .m2. A failed Narayana build will result in these artefacts being missing. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1670) Add a community profile to enable none-EAP features: was Remove jfreechart dependency from EAP6 profile

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1670?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1670: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/317 > Add a community profile to enable none-EAP features: was Remove jfreechart dependency from EAP6 profile > ------------------------------------------------------------------------------------------------------- > > Key: JBTM-1670 > URL: https://issues.jboss.org/browse/JBTM-1670 > 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 > > Currently in EAP6 there is no jfreechart library so we need to remove the relative components from JBossTS: > {code} > ArjunaCore/arjuna/pom.xml > pom.xml > {code} > And we need to remove these two classes which depend on jfreechart: > {code} > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/tools/stats/TxPerfPlugin.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/tools/stats/TxPerfGraph.java > {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

10 years, 11 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