December 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1378) xts-demo-test cannot find artifact: org.jboss.as:jboss-as-arquillian-container-managed:jar:7.2.0.Alpha1-SNAPSHOT

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1378?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1378. --------------------------------- Resolution: Done > xts-demo-test cannot find artifact: org.jboss.as:jboss-as-arquillian-container-managed:jar:7.2.0.Alpha1-SNAPSHOT > ---------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1378 > URL: https://issues.jboss.org/browse/JBTM-1378 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > > See: http://172.17.131.2/job/btny-EAP61-quickstarts/559 > [ERROR] Failed to execute goal on project xts-demo-test: Could not resolve dependencies for project org.jboss.jbossts.quickstarts.xts.demo:xts-demo-test:jar:4.17.4.Final-SNAPSHOT: Could not find artifact org.jboss.as:jboss-as-arquillian-container-managed:jar:7.2.0.Alpha1-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) -> [Help 1] -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1378) xts-demo-test cannot find artifact: org.jboss.as:jboss-as-arquillian-container-managed:jar:7.2.0.Alpha1-SNAPSHOT

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1378?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1378: ------------------------------------- Problem with Upstream, now resolved > xts-demo-test cannot find artifact: org.jboss.as:jboss-as-arquillian-container-managed:jar:7.2.0.Alpha1-SNAPSHOT > ---------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1378 > URL: https://issues.jboss.org/browse/JBTM-1378 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > > See: http://172.17.131.2/job/btny-EAP61-quickstarts/559 > [ERROR] Failed to execute goal on project xts-demo-test: Could not resolve dependencies for project org.jboss.jbossts.quickstarts.xts.demo:xts-demo-test:jar:4.17.4.Final-SNAPSHOT: Could not find artifact org.jboss.as:jboss-as-arquillian-container-managed:jar:7.2.0.Alpha1-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) -> [Help 1] -- 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, 9 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: -------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M2) > 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 > Assignee: Paul Robinson > Labels: assign > Fix For: 5.0.0.Final > > > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBoss 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: 5.0.0.Final (was: 5.0.0.M2) > Deploy REST-AT support as a JBoss 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 > Fix For: 5.0.0.Final > > > 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). -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBoss Module

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?page=com.atlassian.jira.plugin.... ] Paul Robinson reassigned JBTM-1365: ----------------------------------- Assignee: Paul Robinson (was: Michael Musgrove) > Deploy REST-AT support as a JBoss 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 > Fix For: 5.0.0.M2 > > > 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). -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1376) Update TXFramework Quickstarts to use @Inject for DataManagement and TXManagement

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1376?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1376: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update TXFramework Quickstarts to use @Inject for DataManagement and TXManagement > --------------------------------------------------------------------------------- > > Key: JBTM-1376 > URL: https://issues.jboss.org/browse/JBTM-1376 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Demonstrator, TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1388) Package org.jboss.narayana.txframework.api.annotation.management was not found by TXFramework REST-AT quickstarts

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1388?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1388: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Package org.jboss.narayana.txframework.api.annotation.management was not found by TXFramework REST-AT quickstarts > ----------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1388 > URL: https://issues.jboss.org/browse/JBTM-1388 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, TXFramework > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > > See: http://172.17.131.2/job/btny-narayana-quickstarts/153 > {noformat} > [ERROR] \hudson\workspace\btny-narayana-quickstarts\TXFramework\restat-simple\src\main\java\org\jboss\narayana\quickstarts\restat\restaurant\RestaurantServiceATImpl.java:[34,63] package org.jboss.narayana.txframework.api.annotation.management does not exist > [ERROR] > [ERROR] \hudson\workspace\btny-narayana-quickstarts\TXFramework\restat-simple\src\main\java\org\jboss\narayana\quickstarts\restat\taxi\TaxiServiceATImpl.java:[34,63] package org.jboss.narayana.txframework.api.annotation.management does not exist > [ERROR] > [ERROR] \hudson\workspace\btny-narayana-quickstarts\TXFramework\restat-simple\src\main\java\org\jboss\narayana\quickstarts\restat\restaurant\RestaurantServiceATImpl.java:[53,5] cannot find symbol > [ERROR] symbol : class DataManagement > [ERROR] location: class org.jboss.narayana.quickstarts.restat.restaurant.RestaurantServiceATImpl > [ERROR] > [ERROR] \hudson\workspace\btny-narayana-quickstarts\TXFramework\restat-simple\src\main\java\org\jboss\narayana\quickstarts\restat\taxi\TaxiServiceATImpl.java:[53,5] cannot find symbol > [ERROR] symbol : class DataManagement > [ERROR] location: class org.jboss.narayana.quickstarts.restat.taxi.TaxiServiceATImpl > {noformat} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1289) XTS participant completion tests should use a rendezvous to delay close until participant has completed

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1289?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1289: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > XTS participant completion tests should use a rendezvous to delay close until participant has completed > ------------------------------------------------------------------------------------------------------- > > Key: JBTM-1289 > URL: https://issues.jboss.org/browse/JBTM-1289 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 4.16.7, 4.17.4, 5.0.0.M2 > > > The problem is that the participant's notification of completion (sent to the coord) is asynchronous. This can be overtaken by the client's "close" message, resulting in the coordinator cancelling the activity, due to not all participants being completed. > The hack is to add a delay before the client calls 'close'. We have that on the tests in TS, as a stop gap. I am reluctant to apply this hack to the AS test suite as it's embarrassing and likely to be rejected ;-) > This issue is to resolve the problem properly. Maybe by using a Byteman Rendezvous. Alternatively there may be some XTS feature that we can use to poll the coordinator. Or maybe we can add it, as the client API is not standardized. > This issue is not urgent for the TS tests as the hack seems to be holding out at present. However, we do occasionally see this issue on the XTS AS integration testsuite, which increases the priority. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1355) Merge XTS JUnit and Arquillian tests

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1355?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1355: ------------------------------------- I think we should also consider placing all the unit tests (WS-C, WSAS, WS-T, WSCF, WSTX) under a sinbgle project, separated by package. This should reduce the number of poms, arquillian.xmls etc we need to maintain. > Merge XTS JUnit and Arquillian tests > ------------------------------------ > > Key: JBTM-1355 > URL: https://issues.jboss.org/browse/JBTM-1355 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Labels: assign > Fix For: 4.17.4, 5.0.0.M2 > > > When migrating the XTS tests to Arquillian, we wanted to make sure that the old tests where still functional whilst the Arquillian counterparts stabilized. As a result we now have two classes for each test. The Arquillian test delegates each @Test method to the corresponding @Test in the old suite. > For example: > We have the actual test in: > ./XTS/localjunit/WSTX/src/main/java/com/arjuna/wst11/tests/arq/ba/MultiClose.java > And then a Arquillian JUnit test which just calls the test methods above is here: > ./XTS/localjunit/WSTX/src/test/java/com/arjuna/wst11/tests/arq/ba/MultiCloseTest.java > To resolve this issue, we should remove the tests under './XTS/localjunit/WSTX/src/main/java' and merge the test methods into Arquillian test. At the end of this process "./XTS/localjunit/WSTX/src/main" should be empty (and thus removed). > This applies to most, if not all suites under "./XTS/localjunit/". -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1357) Add coloured output to build.sh

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1357?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1357: ------------------------------------- I've been using it for a wile on my machine and I think it's currently too colourful to be adopted across the board. I think we just want to colour: 1. Test failures red 2. overall build success as green 3. overall build failure as red 4. ERROR as red 5. WARN as orange The output should then be mostly default colour with the important stuff highlighted. > Add coloured output to build.sh > ------------------------------- > > Key: JBTM-1357 > URL: https://issues.jboss.org/browse/JBTM-1357 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.Final > > > The following script: https://github.com/builddoctor/maven-antsy-color will colour-code maven output. In particular failed tests come out in red and passes in green. I'm using it on my machine for regular maven builds and I find it makes it a lot easier to spot errors. -- 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, 9 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 December 2012