May 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1770) Root.war deployed to Wildfly gives wrong @ArquillianResource URL

by Cesar Ricardez (JIRA)

[ https://issues.jboss.org/browse/ARQ-1770?page=com.atlassian.jira.plugin.s... ] Cesar Ricardez updated ARQ-1770: -------------------------------- Attachment: arquillian_test_should_fail.zip The file to reproduce error > Root.war deployed to Wildfly gives wrong @ArquillianResource URL > ---------------------------------------------------------------- > > Key: ARQ-1770 > URL: https://issues.jboss.org/browse/ARQ-1770 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Matej Briskar > Attachments: arquillian_test_should_fail.zip > > > This bug is a small one and had easy workaround, but it happens. > When I deploy a ROOT.war to the Wildfly embedded container, the returned @ArquillianResource Url url gives localhost:8080/ROOT instead of the correct localhost:8080/. Tested with wildfly 8.1.0.CR1 dependency version. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1770) Root.war deployed to Wildfly gives wrong @ArquillianResource URL

by Cesar Ricardez (JIRA)

[ https://issues.jboss.org/browse/ARQ-1770?page=com.atlassian.jira.plugin.s... ] Cesar Ricardez commented on ARQ-1770: ------------------------------------- Also, this bus is affecting when using managed: Caused by: java.lang.IllegalStateException: Error launching request at http://127.0.0.1:8080/ROOT/ArquillianServletRunner?outputMode=serializedO.... No result returned at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.executeWithRetry(ServletMethodExecutor.java:139) at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.invoke(ServletMethodExecutor.java:99) at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > Root.war deployed to Wildfly gives wrong @ArquillianResource URL > ---------------------------------------------------------------- > > Key: ARQ-1770 > URL: https://issues.jboss.org/browse/ARQ-1770 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Matej Briskar > Attachments: arquillian_test_should_fail.zip > > > This bug is a small one and had easy workaround, but it happens. > When I deploy a ROOT.war to the Wildfly embedded container, the returned @ArquillianResource Url url gives localhost:8080/ROOT instead of the correct localhost:8080/. Tested with wildfly 8.1.0.CR1 dependency version. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1773) JUnittests pass when exception is thrown from @Before-annotated method

by Cesar Ricardez (JIRA)

[ https://issues.jboss.org/browse/ARQ-1773?page=com.atlassian.jira.plugin.s... ] Cesar Ricardez commented on ARQ-1773: ------------------------------------- I think this is related to ARQ-1758 > JUnittests pass when exception is thrown from @Before-annotated method > ---------------------------------------------------------------------- > > Key: ARQ-1773 > URL: https://issues.jboss.org/browse/ARQ-1773 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Mattias Persson > Attachments: arquillian_test_should_fail.zip > > > When an exception is thrown from a method with @Before, tests that should fail actually pass when using Arquillian 1.1.4.Final. When stepping down to 1.1.3.Final, the tests fail as expected. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1750) Support javaVmArguments configuration option to control forked vm

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-1750?page=com.atlassian.jira.plugin.s... ] Gerhard Poul updated ARQ-1750: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: was_1.0.0.next Resolution: Done merged into master > Support javaVmArguments configuration option to control forked vm > ----------------------------------------------------------------- > > Key: ARQ-1750 > URL: https://issues.jboss.org/browse/ARQ-1750 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Assignee: Gerhard Poul > Fix For: was_1.0.0.next > > > Support configuration option javaVmArguments to add extra information to the launched WLP vm. > * memory settings > * debug options > java [javaVmArguments] -javaagent:lib/bootstrap-agent.jar -jar lib/ws-launch.jar -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1780) Fix parsing of import-export packages in class AbstractOSGiApplicationArchiveProcessor

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/ARQ-1780?page=com.atlassian.jira.plugin.s... ] Martin Basovnik updated ARQ-1780: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-osgi/pull/17 > Fix parsing of import-export packages in class AbstractOSGiApplicationArchiveProcessor > -------------------------------------------------------------------------------------- > > Key: ARQ-1780 > URL: https://issues.jboss.org/browse/ARQ-1780 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Method {{enhanceApplicationArchive()}} in specified class cannot parse import packages from file {{MANIFEST.MF}} correctly. Input string must be split only by those commas that are not surrounded by double-quotes. > Example: > {{org.jboss.arquillian.junit;version="[X.0.0,Y.0.0)";extra="A,B",org.junit"}} > must be split as follows: > {{org.jboss.arquillian.junit;version="[X.0.0,Y.0.0)";extra="A,B"}} and {{org.junit}} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1780) Fix parsing of import-export packages in class AbstractOSGiApplicationArchiveProcessor

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/ARQ-1780?page=com.atlassian.jira.plugin.s... ] Martin Basovnik updated ARQ-1780: --------------------------------- Summary: Fix parsing of import-export packages in class AbstractOSGiApplicationArchiveProcessor (was: Class AbstractOSGiApplicationArchiveProcessor cannot parse import packages correctly) > Fix parsing of import-export packages in class AbstractOSGiApplicationArchiveProcessor > -------------------------------------------------------------------------------------- > > Key: ARQ-1780 > URL: https://issues.jboss.org/browse/ARQ-1780 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Method {{enhanceApplicationArchive()}} in specified class cannot parse import packages from file {{MANIFEST.MF}} correctly. Input string must be split only by those commas that are not surrounded by double-quotes. > Example: > {{org.jboss.arquillian.junit;version="[X.0.0,Y.0.0)";extra="A,B",org.junit"}} > must be split as follows: > {{org.jboss.arquillian.junit;version="[X.0.0,Y.0.0)";extra="A,B"}} and {{org.junit}} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1780) Class AbstractOSGiApplicationArchiveProcessor cannot parse import packages correctly

by Martin Basovnik (JIRA)

Martin Basovnik created ARQ-1780: ------------------------------------ Summary: Class AbstractOSGiApplicationArchiveProcessor cannot parse import packages correctly Key: ARQ-1780 URL: https://issues.jboss.org/browse/ARQ-1780 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Martin Basovnik Assignee: Thomas Diesler Method {{enhanceApplicationArchive()}} in specified class cannot parse import packages from file {{MANIFEST.MF}} correctly. Input string must be split only by those commas that are not surrounded by double-quotes. Example: {{org.jboss.arquillian.junit;version="[X.0.0,Y.0.0)";extra="A,B",org.junit"}} must be split as follows: {{org.jboss.arquillian.junit;version="[X.0.0,Y.0.0)";extra="A,B"}} and {{org.junit}} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1779) Tests are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter

by Thomas Küstermann (JIRA)

[ https://issues.jboss.org/browse/ARQ-1779?page=com.atlassian.jira.plugin.s... ] Thomas Küstermann commented on ARQ-1779: ---------------------------------------- I activated {{arquillian.debug}} and observed a bunch of {{(E) ScriptExecutionException}} entries. And indeed, there were errors in the scripts to execute (missed to set {{sqlDialect}} to oracle). So the problem is not that the tests aren't executed. The issue is that the exceptions don't fail the tests. The exceptions are not reported, neither in Eclipse nor on the command line (using maven). > Tests are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter > ----------------------------------------------------------------------------------- > > Key: ARQ-1779 > URL: https://issues.jboss.org/browse/ARQ-1779 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Thomas Küstermann > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > Forum reference: https://community.jboss.org/message/874117 > The following test case succeeds (green bar) although it should fail: > {code:java} > @RunWith(Arquillian.class) > @DataSource("java:oracleDS") > @Cleanup(phase=TestExecutionPhase.NONE) > @ApplyScriptBefore("deploy-db-functionality.sql") > @ApplyScriptAfter("undeploy-db-functionality.sql") > public class PersistenceIT { > // @Deployment ... > > @Test > @ApplyScriptBefore("trigger-db-functionality.sql") > public void shouldFail() { > Assert.fail("should fail, but doesn't"); > } > } > {code} > Removing class level annotations does not work either: > {code:java} > @Test > @ApplyScriptBefore({ "deploy-db-functionality.sql", "trigger-db-functionality.sql" }) > @ApplyScriptAfter("undeploy-db-functionality.sql") > public void shouldFail() { ... } > {code} > What actually works is to use only one ApplyScriptBefore / ApplyScriptAfter annotation per test, each with only one script to execute. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1779) Tests are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1779?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-1779: -------------------------------- Fix Version/s: persistence_1.0.0.next > Tests are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter > ----------------------------------------------------------------------------------- > > Key: ARQ-1779 > URL: https://issues.jboss.org/browse/ARQ-1779 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Thomas Küstermann > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > Forum reference: https://community.jboss.org/message/874117 > The following test case succeeds (green bar) although it should fail: > {code:java} > @RunWith(Arquillian.class) > @DataSource("java:oracleDS") > @Cleanup(phase=TestExecutionPhase.NONE) > @ApplyScriptBefore("deploy-db-functionality.sql") > @ApplyScriptAfter("undeploy-db-functionality.sql") > public class PersistenceIT { > // @Deployment ... > > @Test > @ApplyScriptBefore("trigger-db-functionality.sql") > public void shouldFail() { > Assert.fail("should fail, but doesn't"); > } > } > {code} > Removing class level annotations does not work either: > {code:java} > @Test > @ApplyScriptBefore({ "deploy-db-functionality.sql", "trigger-db-functionality.sql" }) > @ApplyScriptAfter("undeploy-db-functionality.sql") > public void shouldFail() { ... } > {code} > What actually works is to use only one ApplyScriptBefore / ApplyScriptAfter annotation per test, each with only one script to execute. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1779) Tests are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter

by Thomas Küstermann (JIRA)

[ https://issues.jboss.org/browse/ARQ-1779?page=com.atlassian.jira.plugin.s... ] Thomas Küstermann updated ARQ-1779: ----------------------------------- Summary: Tests are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter (was: Test are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter) > Tests are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter > ----------------------------------------------------------------------------------- > > Key: ARQ-1779 > URL: https://issues.jboss.org/browse/ARQ-1779 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Thomas Küstermann > Assignee: Bartosz Majsak > > Forum reference: https://community.jboss.org/message/874117 > The following test case succeeds (green bar) although it should fail: > {code:java} > @RunWith(Arquillian.class) > @DataSource("java:oracleDS") > @Cleanup(phase=TestExecutionPhase.NONE) > @ApplyScriptBefore("deploy-db-functionality.sql") > @ApplyScriptAfter("undeploy-db-functionality.sql") > public class PersistenceIT { > // @Deployment ... > > @Test > @ApplyScriptBefore("trigger-db-functionality.sql") > public void shouldFail() { > Assert.fail("should fail, but doesn't"); > } > } > {code} > Removing class level annotations does not work either: > {code:java} > @Test > @ApplyScriptBefore({ "deploy-db-functionality.sql", "trigger-db-functionality.sql" }) > @ApplyScriptAfter("undeploy-db-functionality.sql") > public void shouldFail() { ... } > {code} > What actually works is to use only one ApplyScriptBefore / ApplyScriptAfter annotation per test, each with only one script to execute. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues May 2014