February 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1351) Narayana Quickstarts: consider putting dependencies in BOM as JDF quickstarts do

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1351?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1351: -------------------------------- Assignee: (was: Paul Robinson) > Narayana Quickstarts: consider putting dependencies in BOM as JDF quickstarts do > -------------------------------------------------------------------------------- > > Key: JBTM-1351 > URL: https://issues.jboss.org/browse/JBTM-1351 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 5.0.0.M2 > Reporter: Ondřej Chaloupka > Priority: Minor > Fix For: 4.17.4, 5.0.0.M2 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Currently the quickstarts for Narayana project does not solve dependency management in some global way. > Each directory contains one quickstart and it manages dependencies on its own what leads to situation that during compilation quickstarts as a whole project common libraries are downloaded several times (e.g. arquillian). > There is idea of using JDF quickstart style of managing dependencies. They use BOMs where all dependencies are defined. Versions are defined in parent pom.xml. > As inspiration could be used BOM from JDF: > https://github.com/jboss-jdf/jboss-bom/blob/master/jboss-javaee-6.0-with-... > It could be used this bom directly or just import it or do it in other way. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1351) Narayana Quickstarts: consider putting dependencies in BOM as JDF quickstarts do

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1351?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1351: -------------------------------- Fix Version/s: (was: 5.0.0.M2) (was: 4.17.4) > Narayana Quickstarts: consider putting dependencies in BOM as JDF quickstarts do > -------------------------------------------------------------------------------- > > Key: JBTM-1351 > URL: https://issues.jboss.org/browse/JBTM-1351 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 5.0.0.M2 > Reporter: Ondřej Chaloupka > Priority: Minor > Original Estimate: 1 day > Remaining Estimate: 1 day > > Currently the quickstarts for Narayana project does not solve dependency management in some global way. > Each directory contains one quickstart and it manages dependencies on its own what leads to situation that during compilation quickstarts as a whole project common libraries are downloaded several times (e.g. arquillian). > There is idea of using JDF quickstart style of managing dependencies. They use BOMs where all dependencies are defined. Versions are defined in parent pom.xml. > As inspiration could be used BOM from JDF: > https://github.com/jboss-jdf/jboss-bom/blob/master/jboss-javaee-6.0-with-... > It could be used this bom directly or just import it or do it in other way. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1074) Deploy REST-AT artifacts to the jboss nexus

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1074?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1074: -------------------------------- Assignee: (was: Paul Robinson) > Deploy REST-AT artifacts to the jboss nexus > ------------------------------------------- > > Key: JBTM-1074 > URL: https://issues.jboss.org/browse/JBTM-1074 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Affects Versions: 5.0.0.M1 > Reporter: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M2 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > We have had a community member asking for the rest module artifacts to be available via the jboss repo -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBossAS subsystem and module

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1365: -------------------------------- Assignee: Michael Musgrove (was: Paul Robinson) > Deploy REST-AT support as a JBossAS subsystem and module > -------------------------------------------------------- > > Key: JBTM-1365 > URL: https://issues.jboss.org/browse/JBTM-1365 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Paul Robinson > Assignee: Michael Musgrove > Priority: Minor > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. > I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). > The subsystem would need to: > * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. > * Deploy the coordinator endpoint. > The module would need to contain the REST-AT coordinator code and the client libraries. > h3. Open Issues > Need to check with the AS team to see if we add a new Subsystem or make do with an existing one. We can't start this work until this is resolved. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBossAS subsystem and module

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1365: -------------------------------- Fix Version/s: (was: 5.0.0.M2) > Deploy REST-AT support as a JBossAS subsystem and module > -------------------------------------------------------- > > Key: JBTM-1365 > URL: https://issues.jboss.org/browse/JBTM-1365 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. > I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). > The subsystem would need to: > * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. > * Deploy the coordinator endpoint. > The module would need to contain the REST-AT coordinator code and the client libraries. > h3. Open Issues > Need to check with the AS team to see if we add a new Subsystem or make do with an existing one. We can't start this work until this is resolved. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBossAS subsystem and module

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1365: -------------------------------- Assignee: (was: Michael Musgrove) > Deploy REST-AT support as a JBossAS subsystem and module > -------------------------------------------------------- > > Key: JBTM-1365 > URL: https://issues.jboss.org/browse/JBTM-1365 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Paul Robinson > Priority: Minor > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. > I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). > The subsystem would need to: > * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. > * Deploy the coordinator endpoint. > The module would need to contain the REST-AT coordinator code and the client libraries. > h3. Open Issues > Need to check with the AS team to see if we add a new Subsystem or make do with an existing one. We can't start this work until this is resolved. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1364) Migrate "REST-AT to JTA" bridge into TXBridge component

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1364?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1364: -------------------------------- Assignee: (was: Paul Robinson) > Migrate "REST-AT to JTA" bridge into TXBridge component > ------------------------------------------------------- > > Key: JBTM-1364 > URL: https://issues.jboss.org/browse/JBTM-1364 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, REST, TxBridge > Reporter: Paul Robinson > Priority: Minor > Labels: assign > Fix For: 5.0.0.M2 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The task is to the work Gytis did on his internship and migrate it into the TXBridge project. > Tasks: > 1. Review the current solution looking for: > 1.1 Major issues that prevent an initial release > 1.2 Test coverage > 2. Make any required changes > 3. Merge into the TXBridge project > 4. Migrate the quickstarts accross > 5. Create a blog post > 5.1 Consider what the end user will need to do to use this technology. We may want to wait until REST-AT and this Bridge are shipped with a Narayana build of AS7. Otherwise the steps to get this working could be rather lengthy. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1454) Compare performance of REST-AT with JTS

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1454?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1454: ----------------------------------- Why? Also, will you be testing HTTP versus IIOP initially to get a base? > Compare performance of REST-AT with JTS > --------------------------------------- > > Key: JBTM-1454 > URL: https://issues.jboss.org/browse/JBTM-1454 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M2 > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-860) use XAResourceWrapper metadata for assume complete

by Jonathan Halliday (JIRA)

[ https://issues.jboss.org/browse/JBTM-860?page=com.atlassian.jira.plugin.s... ] Jonathan Halliday updated JBTM-860: ----------------------------------- Forum Reference: https://community.jboss.org/message/613737 > use XAResourceWrapper metadata for assume complete > -------------------------------------------------- > > Key: JBTM-860 > URL: https://issues.jboss.org/browse/JBTM-860 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Resource Manager > Affects Versions: 4.15.0 > Reporter: Jonathan Halliday > Assignee: Tom Jenkinson > Fix For: 5.0.0.Final > > > In the XA protocol a time window exists wherein the RM has committed and thus forgotten a tx branch but the TM has not yet deleted its log. A crash during this window currently results in an unrecoverable situation, as the TM assumes the branch belongs to an RM that is uncontactable and will retry recovery indefinitely. This stems from an inability to relate the Xid to a specific RM. It can be overridden globally with JTAEnvironmentBean.xaAssumeRecoveryComplete, but we would prefer more fine-grained control. With the availability of RM id information from XAResourceWrapper this becomes feasible. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1026) Fail XTS crash-recovery test if there are any records present in the tx-object-store after test completes

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1026?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1026: -------------------------------- Issue Type: Bug (was: Enhancement) > Fail XTS crash-recovery test if there are any records present in the tx-object-store after test completes > ---------------------------------------------------------------------------------------------------------- > > Key: JBTM-1026 > URL: https://issues.jboss.org/browse/JBTM-1026 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Affects Versions: 5.0.0.M1 > Reporter: Paul Robinson > Assignee: Amos Feng > Fix For: 4.17.0 > > > We should assert in the @After method of BaseCrashTest that there are no records remaining under: > $JBOSS_HOME/standalone/data/tx-object-store/ShadowNoFileLockStore/defaultStore/XTS/ > If any records are found, the test should be failed. -- 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, 3 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 February 2013