May 2013 - jbossts-issues - Jboss List Archives

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

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?focusedWorklogId=12429197&page=... ] Gytis Trikleris logged work on JBTM-1365: ----------------------------------------- Author: Gytis Trikleris Created on: 21/May/13 5:27 AM Start Date: 21/May/13 5:27 AM Worklog Time Spent: 2 days, 4 hours Issue Time Tracking ------------------- Remaining Estimate: 1 week, 4 hours, 50 minutes (was: 1 week, 3 days, 50 minutes) Time Spent: 1 week, 4 days, 3 hours, 10 minutes (was: 1 week, 1 day, 7 hours, 10 minutes) Worklog Id: (was: 12429197) > 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: Gytis Trikleris > Fix For: 5.0.0.M3 > > Original Estimate: 3 weeks > Time Spent: 1 week, 4 days, 3 hours, 10 minutes > Remaining Estimate: 1 week, 4 hours, 50 minutes > > 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1693) Arquillian DeploymentException: Cannot deploy: test.war

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1693?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1693: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Arquillian DeploymentException: Cannot deploy: test.war > ------------------------------------------------------- > > Key: JBTM-1693 > URL: https://issues.jboss.org/browse/JBTM-1693 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, TXFramework > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > See: > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/48/TESTS=XTS,jdk=... > Looks like a general issue with our usage of Arquillian. It seems to be happening consistently, so should be easy to reproduce. It's just started happening and I don't think we have made any changes that could of caused it, therefore I suspect it's due to some change in WildFly. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1701) Upgrade to wildfly 8.0.0.Alpha2-SNAPSHOT

by Amos Feng (JIRA)

Amos Feng created JBTM-1701: ------------------------------- Summary: Upgrade to wildfly 8.0.0.Alpha2-SNAPSHOT Key: JBTM-1701 URL: https://issues.jboss.org/browse/JBTM-1701 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: BlackTie, Testing Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.0.0.M3 -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1692) Tx tests failed with restat errors

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1692?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-1692: --------------------------------- It looks like out-of-date as blacktie-linux64-el6 and blacktie-linux32-el5 and blacktie-linux32-el6 work fine. > Tx tests failed with restat errors > ---------------------------------- > > Key: JBTM-1692 > URL: https://issues.jboss.org/browse/JBTM-1692 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0.M3 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/294/ > http://172.17.131.2/job/blacktie-linux32-el5/961/ > http://172.17.131.2/job/blacktie-linux64-el5/1526/ > {noformat} > 00:44:57,846 WARN [org.jboss.resteasy.plugins.providers.RegisterBuiltin] (default task-36) NoClassDefFoundError: Unable to load builtin provider: org.jboss.resteasy.plugins.validation.hibernate.HibernateValidatorContextResolver > 00:44:57,854 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (default task-36) Deploying javax.ws.rs.core.Application: class org.jboss.jbossts.star.service.TMApplication > 00:44:57,856 ERROR [io.undertow.request] (default task-36) Servlet request failed io.undertow.server.HttpServerExchange@13c6c59: java.lang.LinkageError: org/jboss/resteasy/spi/validation/GeneralValidator > [exec] 2013-05-16 00:44:48,645 [0x00001c10] INFO (TxHttpTxManager :116 ) - Unable to start a new txn on URI > {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

1
0
0 / 0

[JBoss JIRA] (JBTM-1692) Tx tests failed with restat errors

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1692?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1692: ---------------------------- Priority: Minor (was: Critical) > Tx tests failed with restat errors > ---------------------------------- > > Key: JBTM-1692 > URL: https://issues.jboss.org/browse/JBTM-1692 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0.M3 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/294/ > http://172.17.131.2/job/blacktie-linux32-el5/961/ > http://172.17.131.2/job/blacktie-linux64-el5/1526/ > {noformat} > 00:44:57,846 WARN [org.jboss.resteasy.plugins.providers.RegisterBuiltin] (default task-36) NoClassDefFoundError: Unable to load builtin provider: org.jboss.resteasy.plugins.validation.hibernate.HibernateValidatorContextResolver > 00:44:57,854 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (default task-36) Deploying javax.ws.rs.core.Application: class org.jboss.jbossts.star.service.TMApplication > 00:44:57,856 ERROR [io.undertow.request] (default task-36) Servlet request failed io.undertow.server.HttpServerExchange@13c6c59: java.lang.LinkageError: org/jboss/resteasy/spi/validation/GeneralValidator > [exec] 2013-05-16 00:44:48,645 [0x00001c10] INFO (TxHttpTxManager :116 ) - Unable to start a new txn on URI > {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

1
0
0 / 0

[JBoss JIRA] (JBTM-1692) Tx tests failed with restat errors

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1692?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-1692: --------------------------------- http://172.17.131.2/job/blacktie-linux64-el5/1540/ > Tx tests failed with restat errors > ---------------------------------- > > Key: JBTM-1692 > URL: https://issues.jboss.org/browse/JBTM-1692 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/294/ > http://172.17.131.2/job/blacktie-linux32-el5/961/ > http://172.17.131.2/job/blacktie-linux64-el5/1526/ > {noformat} > 00:44:57,846 WARN [org.jboss.resteasy.plugins.providers.RegisterBuiltin] (default task-36) NoClassDefFoundError: Unable to load builtin provider: org.jboss.resteasy.plugins.validation.hibernate.HibernateValidatorContextResolver > 00:44:57,854 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (default task-36) Deploying javax.ws.rs.core.Application: class org.jboss.jbossts.star.service.TMApplication > 00:44:57,856 ERROR [io.undertow.request] (default task-36) Servlet request failed io.undertow.server.HttpServerExchange@13c6c59: java.lang.LinkageError: org/jboss/resteasy/spi/validation/GeneralValidator > [exec] 2013-05-16 00:44:48,645 [0x00001c10] INFO (TxHttpTxManager :116 ) - Unable to start a new txn on URI > {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

1
0
0 / 0

[JBoss JIRA] (JBTM-1693) Arquillian DeploymentException: Cannot deploy: test.war

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1693?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-1693: --------------------------------- np > Arquillian DeploymentException: Cannot deploy: test.war > ------------------------------------------------------- > > Key: JBTM-1693 > URL: https://issues.jboss.org/browse/JBTM-1693 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, TXFramework > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > See: > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/48/TESTS=XTS,jdk=... > Looks like a general issue with our usage of Arquillian. It seems to be happening consistently, so should be easy to reproduce. It's just started happening and I don't think we have made any changes that could of caused it, therefore I suspect it's due to some change in WildFly. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1693) Arquillian DeploymentException: Cannot deploy: test.war

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1693?page=com.atlassian.jira.plugin.... ] Amos Feng reopened JBTM-1693: ----------------------------- > Arquillian DeploymentException: Cannot deploy: test.war > ------------------------------------------------------- > > Key: JBTM-1693 > URL: https://issues.jboss.org/browse/JBTM-1693 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, TXFramework > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > See: > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/48/TESTS=XTS,jdk=... > Looks like a general issue with our usage of Arquillian. It seems to be happening consistently, so should be easy to reproduce. It's just started happening and I don't think we have made any changes that could of caused it, therefore I suspect it's due to some change in WildFly. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1693) Arquillian DeploymentException: Cannot deploy: test.war

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1693?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1693: ---------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/jbosstm/narayana/pull/295, https://github.com/jbosstm/quickstart/pull/75 (was: https://github.com/jbosstm/narayana/pull/295) > Arquillian DeploymentException: Cannot deploy: test.war > ------------------------------------------------------- > > Key: JBTM-1693 > URL: https://issues.jboss.org/browse/JBTM-1693 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, TXFramework > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > See: > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/48/TESTS=XTS,jdk=... > Looks like a general issue with our usage of Arquillian. It seems to be happening consistently, so should be easy to reproduce. It's just started happening and I don't think we have made any changes that could of caused it, therefore I suspect it's due to some change in WildFly. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1693) Arquillian DeploymentException: Cannot deploy: test.war

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1693?page=com.atlassian.jira.plugin.... ] Amos Feng resolved JBTM-1693. ----------------------------- Resolution: Done > Arquillian DeploymentException: Cannot deploy: test.war > ------------------------------------------------------- > > Key: JBTM-1693 > URL: https://issues.jboss.org/browse/JBTM-1693 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, TXFramework > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > See: > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/48/TESTS=XTS,jdk=... > Looks like a general issue with our usage of Arquillian. It seems to be happening consistently, so should be easy to reproduce. It's just started happening and I don't think we have made any changes that could of caused it, therefore I suspect it's due to some change in WildFly. -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues May 2013