From issues at jboss.org Sun Apr 2 14:38:00 2017 From: issues at jboss.org (Vsevolod Golovanov (JIRA)) Date: Sun, 2 Apr 2017 14:38:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-484) Enriched element is not equal to the same element In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13387618#comment-13387618 ] Vsevolod Golovanov commented on ARQGRA-484: ------------------------------------------- I don't understand how to link the new PR: https://github.com/arquillian/arquillian-graphene/pull/164 > Enriched element is not equal to the same element > ------------------------------------------------- > > Key: ARQGRA-484 > URL: https://issues.jboss.org/browse/ARQGRA-484 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.1.0.Alpha3 > Reporter: Ji?? ?tefek > > After upgrading to 2.1.0.Alpha3 from Alpha2, the following (simplified) test won't pass: > {code} > @FindBy(id="id") > private WebElement e; > @Test > private void test(){ > e.equals(e) > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 4 04:38:00 2017 From: issues at jboss.org (nicolas duminil (JIRA)) Date: Tue, 4 Apr 2017 04:38:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2089) Can't use Arquillian with WebSphere 8.5.5 In-Reply-To: References: Message-ID: nicolas duminil created ARQ-2089: ------------------------------------ Summary: Can't use Arquillian with WebSphere 8.5.5 Key: ARQ-2089 URL: https://issues.jboss.org/browse/ARQ-2089 Project: Arquillian Issue Type: Feature Request Components: WebSphere Containers Environment: WebSphere Application Server Full Profile (WAS), on Windows 10. Java 6 (requirement for WebSphere 8.5.5) Reporter: nicolas duminil Assignee: Gerhard Poul I get the following exception while trying to run arquillian tests on WebSphere 8.5.5: Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.562 sec <<< FAILURE! be.alphacredit.tests.TestXSDValidationArquillian Time elapsed: 0 sec <<< ERROR! java.lang.RuntimeException: Could not create new instance of class org.jboss.arquillian.test.impl.EventTestRunnerAdaptor at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:165) at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:102) at org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder.build(TestRunnerAdaptorBuilder.java:52) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:113) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) 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:497) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:422) at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:161) ... 15 more Caused by: java.lang.NoClassDefFoundError: Lcom/ibm/websphere/management/AdminClient; at java.lang.Class.getDeclaredFields0(Native Method) at java.lang.Class.privateGetDeclaredFields(Class.java:2583) at java.lang.Class.getDeclaredFields(Class.java:1916) at org.jboss.arquillian.core.impl.Reflections.getFieldInjectionPoints(Reflections.java:74) at org.jboss.arquillian.core.impl.ExtensionImpl.of(ExtensionImpl.java:53) at org.jboss.arquillian.core.impl.ManagerImpl.inject(ManagerImpl.java:211) at org.jboss.arquillian.core.impl.InjectorImpl.inject(InjectorImpl.java:58) at org.jboss.arquillian.core.impl.loadable.ServiceRegistryLoader.createServiceInstance(ServiceRegistryLoader.java:108) at org.jboss.arquillian.core.impl.loadable.ServiceRegistryLoader.all(ServiceRegistryLoader.java:55) at org.jboss.arquillian.core.impl.loadable.ServiceRegistryLoader.onlyOne(ServiceRegistryLoader.java:67) at org.jboss.arquillian.container.impl.LocalContainerRegistry.create(LocalContainerRegistry.java:80) at org.jboss.arquillian.container.impl.client.container.ContainerRegistryCreator.createRegistry(ContainerRegistryCreator.java:78) 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:497) 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.ManagerImpl.bindAndFire(ManagerImpl.java:265) at org.jboss.arquillian.core.impl.InstanceImpl.set(InstanceImpl.java:74) at org.jboss.arquillian.config.impl.extension.ConfigurationRegistrar.loadConfiguration(ConfigurationRegistrar.java:73) 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:497) 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.ManagerImpl.start(ManagerImpl.java:290) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.(EventTestRunnerAdaptor.java:63) ... 20 more Caused by: java.lang.ClassNotFoundException: com.ibm.websphere.management.AdminClient at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 55 more Here is the relevant part of my POM: com.ibm.websphere.j2ee j2ee provided ............... org.jboss.shrinkwrap.resolver shrinkwrap-resolver-impl-maven test org.jboss.arquillian.junit arquillian-junit-container test org.jboss.arquillian.protocol arquillian-protocol-servlet test org.jboss.arquillian.container arquillian-was-remote-8.5 test Here is the arquillian.xml file: target/deployments/ localhost 8880 false nicolas And here is my unit test: @RunWith(Arquillian.class) public class TestXSDValidationArquillian { private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); @Deployment public static Archive createTestArchive() { slf4jLogger.info("Loading pom.xml"); PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); slf4jLogger.info("pom.xml loaded. Now importing dependencies"); File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); slf4jLogger.info("Dependencies loaded. Creating web archive"); WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); slf4jLogger.info("Web archive created. Now, adding files to the archive"); for (File file : libs) war.addAsLibrary(file); slf4jLogger.info("Web archive created"); return war; } @Test public void test1(){} } What might be the problem here ? Many thanks in advance. Kind regards, Nicolas -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 4 05:29:00 2017 From: issues at jboss.org (nicolas duminil (JIRA)) Date: Tue, 4 Apr 2017 05:29:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2089) Can't use Arquillian with WebSphere 8.5.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13388311#comment-13388311 ] nicolas duminil commented on ARQ-2089: -------------------------------------- My bad, I forgot to define the WAS85_HOME env variable and, hence, the build didn't find the was-public.jar refered through this variable. Defining this variable the exception is gone, however, the test (an empty test) takes more then 5 minutes. But I'll open another ticket for that. This one may be closed. Kind regards, Nicolas > Can't use Arquillian with WebSphere 8.5.5 > ----------------------------------------- > > Key: ARQ-2089 > URL: https://issues.jboss.org/browse/ARQ-2089 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Environment: WebSphere Application Server Full Profile (WAS), on Windows 10. Java 6 (requirement for WebSphere 8.5.5) > Reporter: nicolas duminil > Assignee: Gerhard Poul > > I get the following exception while trying to run arquillian tests on WebSphere 8.5.5: > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.562 sec <<< FAILURE! > be.alphacredit.tests.TestXSDValidationArquillian Time elapsed: 0 sec <<< ERROR! > java.lang.RuntimeException: Could not create new instance of class org.jboss.arquillian.test.impl.EventTestRunnerAdaptor > at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:165) > at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:102) > at org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder.build(TestRunnerAdaptorBuilder.java:52) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:113) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > 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:497) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:161) > ... 15 more > Caused by: java.lang.NoClassDefFoundError: Lcom/ibm/websphere/management/AdminClient; > at java.lang.Class.getDeclaredFields0(Native Method) > at java.lang.Class.privateGetDeclaredFields(Class.java:2583) > at java.lang.Class.getDeclaredFields(Class.java:1916) > at org.jboss.arquillian.core.impl.Reflections.getFieldInjectionPoints(Reflections.java:74) > at org.jboss.arquillian.core.impl.ExtensionImpl.of(ExtensionImpl.java:53) > at org.jboss.arquillian.core.impl.ManagerImpl.inject(ManagerImpl.java:211) > at org.jboss.arquillian.core.impl.InjectorImpl.inject(InjectorImpl.java:58) > at org.jboss.arquillian.core.impl.loadable.ServiceRegistryLoader.createServiceInstance(ServiceRegistryLoader.java:108) > at org.jboss.arquillian.core.impl.loadable.ServiceRegistryLoader.all(ServiceRegistryLoader.java:55) > at org.jboss.arquillian.core.impl.loadable.ServiceRegistryLoader.onlyOne(ServiceRegistryLoader.java:67) > at org.jboss.arquillian.container.impl.LocalContainerRegistry.create(LocalContainerRegistry.java:80) > at org.jboss.arquillian.container.impl.client.container.ContainerRegistryCreator.createRegistry(ContainerRegistryCreator.java:78) > 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:497) > 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.ManagerImpl.bindAndFire(ManagerImpl.java:265) > at org.jboss.arquillian.core.impl.InstanceImpl.set(InstanceImpl.java:74) > at org.jboss.arquillian.config.impl.extension.ConfigurationRegistrar.loadConfiguration(ConfigurationRegistrar.java:73) > 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:497) > 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.ManagerImpl.start(ManagerImpl.java:290) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.(EventTestRunnerAdaptor.java:63) > ... 20 more > Caused by: java.lang.ClassNotFoundException: com.ibm.websphere.management.AdminClient > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 55 more > Here is the relevant part of my POM: > > > com.ibm.websphere.j2ee > j2ee > provided > > ............... > > org.jboss.shrinkwrap.resolver > shrinkwrap-resolver-impl-maven > test > > > org.jboss.arquillian.junit > arquillian-junit-container > test > > > org.jboss.arquillian.protocol > arquillian-protocol-servlet > test > > > org.jboss.arquillian.container > arquillian-was-remote-8.5 > test > > Here is the arquillian.xml file: > > > > target/deployments/ > > > > localhost > 8880 > false > nicolas > > > > And here is my unit test: > @RunWith(Arquillian.class) > public class TestXSDValidationArquillian > { > private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); > > @Deployment > public static Archive createTestArchive() > { > slf4jLogger.info("Loading pom.xml"); > PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); > slf4jLogger.info("pom.xml loaded. Now importing dependencies"); > File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); > slf4jLogger.info("Dependencies loaded. Creating web archive"); > WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); > slf4jLogger.info("Web archive created. Now, adding files to the archive"); > for (File file : libs) > war.addAsLibrary(file); > slf4jLogger.info("Web archive created"); > return war; > } > > @Test > public void test1(){} > } > What might be the problem here ? Many thanks in advance. > Kind regards, > Nicolas -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 4 05:29:00 2017 From: issues at jboss.org (nicolas duminil (JIRA)) Date: Tue, 4 Apr 2017 05:29:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2089) Can't use Arquillian with WebSphere 8.5.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas duminil resolved ARQ-2089. ---------------------------------- Resolution: Done > Can't use Arquillian with WebSphere 8.5.5 > ----------------------------------------- > > Key: ARQ-2089 > URL: https://issues.jboss.org/browse/ARQ-2089 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Environment: WebSphere Application Server Full Profile (WAS), on Windows 10. Java 6 (requirement for WebSphere 8.5.5) > Reporter: nicolas duminil > Assignee: Gerhard Poul > > I get the following exception while trying to run arquillian tests on WebSphere 8.5.5: > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.562 sec <<< FAILURE! > be.alphacredit.tests.TestXSDValidationArquillian Time elapsed: 0 sec <<< ERROR! > java.lang.RuntimeException: Could not create new instance of class org.jboss.arquillian.test.impl.EventTestRunnerAdaptor > at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:165) > at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:102) > at org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder.build(TestRunnerAdaptorBuilder.java:52) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:113) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > 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:497) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:161) > ... 15 more > Caused by: java.lang.NoClassDefFoundError: Lcom/ibm/websphere/management/AdminClient; > at java.lang.Class.getDeclaredFields0(Native Method) > at java.lang.Class.privateGetDeclaredFields(Class.java:2583) > at java.lang.Class.getDeclaredFields(Class.java:1916) > at org.jboss.arquillian.core.impl.Reflections.getFieldInjectionPoints(Reflections.java:74) > at org.jboss.arquillian.core.impl.ExtensionImpl.of(ExtensionImpl.java:53) > at org.jboss.arquillian.core.impl.ManagerImpl.inject(ManagerImpl.java:211) > at org.jboss.arquillian.core.impl.InjectorImpl.inject(InjectorImpl.java:58) > at org.jboss.arquillian.core.impl.loadable.ServiceRegistryLoader.createServiceInstance(ServiceRegistryLoader.java:108) > at org.jboss.arquillian.core.impl.loadable.ServiceRegistryLoader.all(ServiceRegistryLoader.java:55) > at org.jboss.arquillian.core.impl.loadable.ServiceRegistryLoader.onlyOne(ServiceRegistryLoader.java:67) > at org.jboss.arquillian.container.impl.LocalContainerRegistry.create(LocalContainerRegistry.java:80) > at org.jboss.arquillian.container.impl.client.container.ContainerRegistryCreator.createRegistry(ContainerRegistryCreator.java:78) > 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:497) > 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.ManagerImpl.bindAndFire(ManagerImpl.java:265) > at org.jboss.arquillian.core.impl.InstanceImpl.set(InstanceImpl.java:74) > at org.jboss.arquillian.config.impl.extension.ConfigurationRegistrar.loadConfiguration(ConfigurationRegistrar.java:73) > 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:497) > 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.ManagerImpl.start(ManagerImpl.java:290) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.(EventTestRunnerAdaptor.java:63) > ... 20 more > Caused by: java.lang.ClassNotFoundException: com.ibm.websphere.management.AdminClient > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 55 more > Here is the relevant part of my POM: > > > com.ibm.websphere.j2ee > j2ee > provided > > ............... > > org.jboss.shrinkwrap.resolver > shrinkwrap-resolver-impl-maven > test > > > org.jboss.arquillian.junit > arquillian-junit-container > test > > > org.jboss.arquillian.protocol > arquillian-protocol-servlet > test > > > org.jboss.arquillian.container > arquillian-was-remote-8.5 > test > > Here is the arquillian.xml file: > > > > target/deployments/ > > > > localhost > 8880 > false > nicolas > > > > And here is my unit test: > @RunWith(Arquillian.class) > public class TestXSDValidationArquillian > { > private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); > > @Deployment > public static Archive createTestArchive() > { > slf4jLogger.info("Loading pom.xml"); > PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); > slf4jLogger.info("pom.xml loaded. Now importing dependencies"); > File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); > slf4jLogger.info("Dependencies loaded. Creating web archive"); > WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); > slf4jLogger.info("Web archive created. Now, adding files to the archive"); > for (File file : libs) > war.addAsLibrary(file); > slf4jLogger.info("Web archive created"); > return war; > } > > @Test > public void test1(){} > } > What might be the problem here ? Many thanks in advance. > Kind regards, > Nicolas -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 4 05:42:00 2017 From: issues at jboss.org (nicolas duminil (JIRA)) Date: Tue, 4 Apr 2017 05:42:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2090) Arquillian test takes more than 5 minutes In-Reply-To: References: Message-ID: nicolas duminil created ARQ-2090: ------------------------------------ Summary: Arquillian test takes more than 5 minutes Key: ARQ-2090 URL: https://issues.jboss.org/browse/ARQ-2090 Project: Arquillian Issue Type: Bug Components: WebSphere Containers Environment: arquillian-was-remote-8.5:1.0.0-Final, WebSphere 8.5.5 on Windows 10, Java: IBM J9 VM (build 2.6, JRE 1.6.0 Windows 8 amd64-64 Compressed References 20130301_140166 (JIT enabled, AOT enabled) Reporter: nicolas duminil Assignee: Gerhard Poul The execution of an Arquillian test (an empty test) takes more than 5 minutes. here is the test: @RunWith(Arquillian.class) public class TestXSDValidationArquillian { private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); @Deployment public static Archive createTestArchive() { //slf4jLogger.info("Loading pom.xml"); System.out.println("Loading pom.xml"); PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); //slf4jLogger.info("pom.xml loaded. Now importing dependencies"); System.out.println("pom.xml loaded. Now importing dependencies"); File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); //slf4jLogger.info("Dependencies loaded. Creating web archive"); System.out.println("Dependencies loaded. Creating web archive"); WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); //slf4jLogger.info("Web archive created. Now, adding files to the archive"); System.out.println("Web archive created. Now, adding files to the archive"); for (File file : libs) war.addAsLibrary(file); //slf4jLogger.info("Web archive created"); System.out.println("Web archive created"); return war; } @Test public void test1(){} An here is the console output: ------------------------------------------------------- T E S T S ------------------------------------------------------- Running be.alphacredit.tests.TestXSDValidationArquillian 04-Apr-2017 11:09:59 null null WARNING: ADMC0046W 04-Apr-2017 11:10:00 null null WARNING: Could not find tmx4jTransform.jar in null/etc/tmx4jTransform.jar - Interoperability to older versions of WebSphere is disabled 04-Apr-2017 11:10:00 null null INFO: ssl.disable.url.hostname.verification.CWPKI0027I Loading pom.xml pom.xml loaded. Now importing dependencies 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed WARNING: Failed downloading org/jboss/arquillian/container/arquillian-was-remote-8.5/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-was-remote-8.5:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed WARNING: Failed downloading org/jboss/arquillian/container/arquillian-parent-was/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-parent-was:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) Dependencies loaded. Creating web archive Web archive created. Now, adding files to the archive Web archive created 04-Apr-2017 11:11:00 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at -126388353 ( com.ibm.ws.amm.scan.util.info.impl.test.AnnotationTypeReaderAnno.nestedAnno ) ] Name [ null ] Description [ Lcom/ibm/ws/amm/scan/util/info/impl/test/AnnotationTypeReaderNestedAnno; ] Call in violation of protocol 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1495822839 ( javax.persistence.AssociationOverride.joinTable ) ] Name [ null ] Description [ Ljavax/persistence/JoinTable; ] Call in violation of protocol 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1522521260 ( javax.servlet.annotation.ServletSecurity.value ) ] Name [ null ] Description [ Ljavax/servlet/annotation/HttpConstraint; ] Call in violation of protocol 04-Apr-2017 11:11:31 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy INFO: Target server for deployment is WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 04-Apr-2017 11:14:39 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy INFO: Application was started on the following targets: WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.094 sec Results : Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 As one may see, test starts at 11:09:59 and finishes at 11:14:39 and takes 291.094 seconds. I have googled and found some posts concerning the metadata-complete="true" that I added to my web.xml, as follows: but it didn't help. It seems to be related to the IBM Java 6 but this is the JVM that one is supposed to use with IBM WebSphere. Any idea of what might be the problem here ? Kind regards, Nicolas DUMINIL -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 4 05:46:01 2017 From: issues at jboss.org (nicolas duminil (JIRA)) Date: Tue, 4 Apr 2017 05:46:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2090) Arquillian test takes more than 5 minutes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas duminil updated ARQ-2090: --------------------------------- Description: The execution of an Arquillian test (an empty test) takes more than 5 minutes. here is the test: {{@RunWith(Arquillian.class) public class TestXSDValidationArquillian { private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); @Deployment public static Archive createTestArchive() { slf4jLogger.info("Loading pom.xml"); PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); slf4jLogger.info("pom.xml loaded. Now importing dependencies"); File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); slf4jLogger.info("Dependencies loaded. Creating web archive"); WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); slf4jLogger.info("Web archive created. Now, adding files to the archive"); for (File file : libs) war.addAsLibrary(file); slf4jLogger.info("Web archive created"); return war; } @Test public void test1(){} }} An here is the console output: ------------------------------------------------------- T E S T S ------------------------------------------------------- Running be.alphacredit.tests.TestXSDValidationArquillian 04-Apr-2017 11:09:59 null null WARNING: ADMC0046W 04-Apr-2017 11:10:00 null null WARNING: Could not find tmx4jTransform.jar in null/etc/tmx4jTransform.jar - Interoperability to older versions of WebSphere is disabled 04-Apr-2017 11:10:00 null null INFO: ssl.disable.url.hostname.verification.CWPKI0027I Loading pom.xml pom.xml loaded. Now importing dependencies 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed WARNING: Failed downloading org/jboss/arquillian/container/arquillian-was-remote-8.5/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-was-remote-8.5:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed WARNING: Failed downloading org/jboss/arquillian/container/arquillian-parent-was/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-parent-was:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) Dependencies loaded. Creating web archive Web archive created. Now, adding files to the archive Web archive created 04-Apr-2017 11:11:00 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at -126388353 ( com.ibm.ws.amm.scan.util.info.impl.test.AnnotationTypeReaderAnno.nestedAnno ) ] Name [ null ] Description [ Lcom/ibm/ws/amm/scan/util/info/impl/test/AnnotationTypeReaderNestedAnno; ] Call in violation of protocol 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1495822839 ( javax.persistence.AssociationOverride.joinTable ) ] Name [ null ] Description [ Ljavax/persistence/JoinTable; ] Call in violation of protocol 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1522521260 ( javax.servlet.annotation.ServletSecurity.value ) ] Name [ null ] Description [ Ljavax/servlet/annotation/HttpConstraint; ] Call in violation of protocol 04-Apr-2017 11:11:31 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy INFO: Target server for deployment is WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 04-Apr-2017 11:14:39 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy INFO: Application was started on the following targets: WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.094 sec Results : Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 As one may see, test starts at 11:09:59 and finishes at 11:14:39 and takes 291.094 seconds. I have googled and found some posts concerning the metadata-complete="true" that I added to my web.xml, as follows: but it didn't help. It seems to be related to the IBM Java 6 but this is the JVM that one is supposed to use with IBM WebSphere. Any idea of what might be the problem here ? Kind regards, Nicolas DUMINIL was: The execution of an Arquillian test (an empty test) takes more than 5 minutes. here is the test: @RunWith(Arquillian.class) public class TestXSDValidationArquillian { private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); @Deployment public static Archive createTestArchive() { //slf4jLogger.info("Loading pom.xml"); System.out.println("Loading pom.xml"); PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); //slf4jLogger.info("pom.xml loaded. Now importing dependencies"); System.out.println("pom.xml loaded. Now importing dependencies"); File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); //slf4jLogger.info("Dependencies loaded. Creating web archive"); System.out.println("Dependencies loaded. Creating web archive"); WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); //slf4jLogger.info("Web archive created. Now, adding files to the archive"); System.out.println("Web archive created. Now, adding files to the archive"); for (File file : libs) war.addAsLibrary(file); //slf4jLogger.info("Web archive created"); System.out.println("Web archive created"); return war; } @Test public void test1(){} An here is the console output: ------------------------------------------------------- T E S T S ------------------------------------------------------- Running be.alphacredit.tests.TestXSDValidationArquillian 04-Apr-2017 11:09:59 null null WARNING: ADMC0046W 04-Apr-2017 11:10:00 null null WARNING: Could not find tmx4jTransform.jar in null/etc/tmx4jTransform.jar - Interoperability to older versions of WebSphere is disabled 04-Apr-2017 11:10:00 null null INFO: ssl.disable.url.hostname.verification.CWPKI0027I Loading pom.xml pom.xml loaded. Now importing dependencies 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed WARNING: Failed downloading org/jboss/arquillian/container/arquillian-was-remote-8.5/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-was-remote-8.5:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed WARNING: Failed downloading org/jboss/arquillian/container/arquillian-parent-was/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-parent-was:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) Dependencies loaded. Creating web archive Web archive created. Now, adding files to the archive Web archive created 04-Apr-2017 11:11:00 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at -126388353 ( com.ibm.ws.amm.scan.util.info.impl.test.AnnotationTypeReaderAnno.nestedAnno ) ] Name [ null ] Description [ Lcom/ibm/ws/amm/scan/util/info/impl/test/AnnotationTypeReaderNestedAnno; ] Call in violation of protocol 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1495822839 ( javax.persistence.AssociationOverride.joinTable ) ] Name [ null ] Description [ Ljavax/persistence/JoinTable; ] Call in violation of protocol 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1522521260 ( javax.servlet.annotation.ServletSecurity.value ) ] Name [ null ] Description [ Ljavax/servlet/annotation/HttpConstraint; ] Call in violation of protocol 04-Apr-2017 11:11:31 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy INFO: Target server for deployment is WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 04-Apr-2017 11:14:39 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy INFO: Application was started on the following targets: WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.094 sec Results : Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 As one may see, test starts at 11:09:59 and finishes at 11:14:39 and takes 291.094 seconds. I have googled and found some posts concerning the metadata-complete="true" that I added to my web.xml, as follows: but it didn't help. It seems to be related to the IBM Java 6 but this is the JVM that one is supposed to use with IBM WebSphere. Any idea of what might be the problem here ? Kind regards, Nicolas DUMINIL > Arquillian test takes more than 5 minutes > ----------------------------------------- > > Key: ARQ-2090 > URL: https://issues.jboss.org/browse/ARQ-2090 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: arquillian-was-remote-8.5:1.0.0-Final, WebSphere 8.5.5 on Windows 10, > Java: IBM J9 VM (build 2.6, JRE 1.6.0 Windows 8 amd64-64 Compressed References 20130301_140166 (JIT enabled, AOT enabled) > Reporter: nicolas duminil > Assignee: Gerhard Poul > > The execution of an Arquillian test (an empty test) takes more than 5 minutes. here is the test: > {{@RunWith(Arquillian.class) > public class TestXSDValidationArquillian > { > private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); > > @Deployment > public static Archive createTestArchive() > { > slf4jLogger.info("Loading pom.xml"); > PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); > slf4jLogger.info("pom.xml loaded. Now importing dependencies"); > File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); > slf4jLogger.info("Dependencies loaded. Creating web archive"); > WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); > slf4jLogger.info("Web archive created. Now, adding files to the archive"); > for (File file : libs) > war.addAsLibrary(file); > slf4jLogger.info("Web archive created"); > return war; > } > > @Test > public void test1(){} > }} > An here is the console output: > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running be.alphacredit.tests.TestXSDValidationArquillian > 04-Apr-2017 11:09:59 null null > WARNING: ADMC0046W > 04-Apr-2017 11:10:00 null null > WARNING: Could not find tmx4jTransform.jar in null/etc/tmx4jTransform.jar - Interoperability to older versions of WebSphere is disabled > 04-Apr-2017 11:10:00 null null > INFO: ssl.disable.url.hostname.verification.CWPKI0027I > Loading pom.xml > pom.xml loaded. Now importing dependencies > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-was-remote-8.5/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-was-remote-8.5:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-parent-was/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-parent-was:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > Dependencies loaded. Creating web archive > Web archive created. Now, adding files to the archive > Web archive created > 04-Apr-2017 11:11:00 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at -126388353 ( com.ibm.ws.amm.scan.util.info.impl.test.AnnotationTypeReaderAnno.nestedAnno ) ] Name [ null ] Description [ Lcom/ibm/ws/amm/scan/util/info/impl/test/AnnotationTypeReaderNestedAnno; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1495822839 ( javax.persistence.AssociationOverride.joinTable ) ] Name [ null ] Description [ Ljavax/persistence/JoinTable; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1522521260 ( javax.servlet.annotation.ServletSecurity.value ) ] Name [ null ] Description [ Ljavax/servlet/annotation/HttpConstraint; ] Call in violation of protocol > 04-Apr-2017 11:11:31 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Target server for deployment is WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > 04-Apr-2017 11:14:39 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Application was started on the following targets: WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.094 sec > Results : > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 > As one may see, test starts at 11:09:59 and finishes at 11:14:39 and takes 291.094 seconds. I have googled and found some posts concerning the metadata-complete="true" that I added to my web.xml, as follows: > > > but it didn't help. It seems to be related to the IBM Java 6 but this is the JVM that one is supposed to use with IBM WebSphere. Any idea of what might be the problem here ? > Kind regards, > Nicolas DUMINIL -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 4 05:48:00 2017 From: issues at jboss.org (nicolas duminil (JIRA)) Date: Tue, 4 Apr 2017 05:48:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2090) Arquillian test takes more than 5 minutes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas duminil updated ARQ-2090: --------------------------------- Description: The execution of an Arquillian test (an empty test) takes more than 5 minutes. here is the test: -{{@RunWith(Arquillian.class) public class TestXSDValidationArquillian { private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); @Deployment public static Archive createTestArchive() { slf4jLogger.info("Loading pom.xml"); PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); slf4jLogger.info("pom.xml loaded. Now importing dependencies"); File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); slf4jLogger.info("Dependencies loaded. Creating web archive"); WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); slf4jLogger.info("Web archive created. Now, adding files to the archive"); for (File file : libs) war.addAsLibrary(file); slf4jLogger.info("Web archive created"); return war; }- @Test public void test1(){} }} An here is the console output: ------------------------------------------------------- T E S T S ------------------------------------------------------- Running be.alphacredit.tests.TestXSDValidationArquillian 04-Apr-2017 11:09:59 null null WARNING: ADMC0046W 04-Apr-2017 11:10:00 null null WARNING: Could not find tmx4jTransform.jar in null/etc/tmx4jTransform.jar - Interoperability to older versions of WebSphere is disabled 04-Apr-2017 11:10:00 null null INFO: ssl.disable.url.hostname.verification.CWPKI0027I Loading pom.xml pom.xml loaded. Now importing dependencies 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed WARNING: Failed downloading org/jboss/arquillian/container/arquillian-was-remote-8.5/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-was-remote-8.5:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed WARNING: Failed downloading org/jboss/arquillian/container/arquillian-parent-was/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-parent-was:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) Dependencies loaded. Creating web archive Web archive created. Now, adding files to the archive Web archive created 04-Apr-2017 11:11:00 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at -126388353 ( com.ibm.ws.amm.scan.util.info.impl.test.AnnotationTypeReaderAnno.nestedAnno ) ] Name [ null ] Description [ Lcom/ibm/ws/amm/scan/util/info/impl/test/AnnotationTypeReaderNestedAnno; ] Call in violation of protocol 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1495822839 ( javax.persistence.AssociationOverride.joinTable ) ] Name [ null ] Description [ Ljavax/persistence/JoinTable; ] Call in violation of protocol 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1522521260 ( javax.servlet.annotation.ServletSecurity.value ) ] Name [ null ] Description [ Ljavax/servlet/annotation/HttpConstraint; ] Call in violation of protocol 04-Apr-2017 11:11:31 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy INFO: Target server for deployment is WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 04-Apr-2017 11:14:39 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy INFO: Application was started on the following targets: WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.094 sec Results : Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 As one may see, test starts at 11:09:59 and finishes at 11:14:39 and takes 291.094 seconds. I have googled and found some posts concerning the metadata-complete="true" that I added to my web.xml, as follows: but it didn't help. It seems to be related to the IBM Java 6 but this is the JVM that one is supposed to use with IBM WebSphere. Any idea of what might be the problem here ? Kind regards, Nicolas DUMINIL was: The execution of an Arquillian test (an empty test) takes more than 5 minutes. here is the test: {{@RunWith(Arquillian.class) public class TestXSDValidationArquillian { private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); @Deployment public static Archive createTestArchive() { slf4jLogger.info("Loading pom.xml"); PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); slf4jLogger.info("pom.xml loaded. Now importing dependencies"); File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); slf4jLogger.info("Dependencies loaded. Creating web archive"); WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); slf4jLogger.info("Web archive created. Now, adding files to the archive"); for (File file : libs) war.addAsLibrary(file); slf4jLogger.info("Web archive created"); return war; } @Test public void test1(){} }} An here is the console output: ------------------------------------------------------- T E S T S ------------------------------------------------------- Running be.alphacredit.tests.TestXSDValidationArquillian 04-Apr-2017 11:09:59 null null WARNING: ADMC0046W 04-Apr-2017 11:10:00 null null WARNING: Could not find tmx4jTransform.jar in null/etc/tmx4jTransform.jar - Interoperability to older versions of WebSphere is disabled 04-Apr-2017 11:10:00 null null INFO: ssl.disable.url.hostname.verification.CWPKI0027I Loading pom.xml pom.xml loaded. Now importing dependencies 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed WARNING: Failed downloading org/jboss/arquillian/container/arquillian-was-remote-8.5/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-was-remote-8.5:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed WARNING: Failed downloading org/jboss/arquillian/container/arquillian-parent-was/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-parent-was:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) Dependencies loaded. Creating web archive Web archive created. Now, adding files to the archive Web archive created 04-Apr-2017 11:11:00 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at -126388353 ( com.ibm.ws.amm.scan.util.info.impl.test.AnnotationTypeReaderAnno.nestedAnno ) ] Name [ null ] Description [ Lcom/ibm/ws/amm/scan/util/info/impl/test/AnnotationTypeReaderNestedAnno; ] Call in violation of protocol 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1495822839 ( javax.persistence.AssociationOverride.joinTable ) ] Name [ null ] Description [ Ljavax/persistence/JoinTable; ] Call in violation of protocol 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1522521260 ( javax.servlet.annotation.ServletSecurity.value ) ] Name [ null ] Description [ Ljavax/servlet/annotation/HttpConstraint; ] Call in violation of protocol 04-Apr-2017 11:11:31 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy INFO: Target server for deployment is WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 04-Apr-2017 11:14:39 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy INFO: Application was started on the following targets: WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.094 sec Results : Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 As one may see, test starts at 11:09:59 and finishes at 11:14:39 and takes 291.094 seconds. I have googled and found some posts concerning the metadata-complete="true" that I added to my web.xml, as follows: but it didn't help. It seems to be related to the IBM Java 6 but this is the JVM that one is supposed to use with IBM WebSphere. Any idea of what might be the problem here ? Kind regards, Nicolas DUMINIL > Arquillian test takes more than 5 minutes > ----------------------------------------- > > Key: ARQ-2090 > URL: https://issues.jboss.org/browse/ARQ-2090 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: arquillian-was-remote-8.5:1.0.0-Final, WebSphere 8.5.5 on Windows 10, > Java: IBM J9 VM (build 2.6, JRE 1.6.0 Windows 8 amd64-64 Compressed References 20130301_140166 (JIT enabled, AOT enabled) > Reporter: nicolas duminil > Assignee: Gerhard Poul > > The execution of an Arquillian test (an empty test) takes more than 5 minutes. here is the test: > -{{@RunWith(Arquillian.class) > public class TestXSDValidationArquillian > { > private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); > > @Deployment > public static Archive createTestArchive() > { > slf4jLogger.info("Loading pom.xml"); > PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); > slf4jLogger.info("pom.xml loaded. Now importing dependencies"); > File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); > slf4jLogger.info("Dependencies loaded. Creating web archive"); > WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); > slf4jLogger.info("Web archive created. Now, adding files to the archive"); > for (File file : libs) > war.addAsLibrary(file); > slf4jLogger.info("Web archive created"); > return war; > }- > > @Test > public void test1(){} > }} > An here is the console output: > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running be.alphacredit.tests.TestXSDValidationArquillian > 04-Apr-2017 11:09:59 null null > WARNING: ADMC0046W > 04-Apr-2017 11:10:00 null null > WARNING: Could not find tmx4jTransform.jar in null/etc/tmx4jTransform.jar - Interoperability to older versions of WebSphere is disabled > 04-Apr-2017 11:10:00 null null > INFO: ssl.disable.url.hostname.verification.CWPKI0027I > Loading pom.xml > pom.xml loaded. Now importing dependencies > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-was-remote-8.5/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-was-remote-8.5:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-parent-was/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-parent-was:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > Dependencies loaded. Creating web archive > Web archive created. Now, adding files to the archive > Web archive created > 04-Apr-2017 11:11:00 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at -126388353 ( com.ibm.ws.amm.scan.util.info.impl.test.AnnotationTypeReaderAnno.nestedAnno ) ] Name [ null ] Description [ Lcom/ibm/ws/amm/scan/util/info/impl/test/AnnotationTypeReaderNestedAnno; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1495822839 ( javax.persistence.AssociationOverride.joinTable ) ] Name [ null ] Description [ Ljavax/persistence/JoinTable; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1522521260 ( javax.servlet.annotation.ServletSecurity.value ) ] Name [ null ] Description [ Ljavax/servlet/annotation/HttpConstraint; ] Call in violation of protocol > 04-Apr-2017 11:11:31 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Target server for deployment is WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > 04-Apr-2017 11:14:39 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Application was started on the following targets: WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.094 sec > Results : > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 > As one may see, test starts at 11:09:59 and finishes at 11:14:39 and takes 291.094 seconds. I have googled and found some posts concerning the metadata-complete="true" that I added to my web.xml, as follows: > > > but it didn't help. It seems to be related to the IBM Java 6 but this is the JVM that one is supposed to use with IBM WebSphere. Any idea of what might be the problem here ? > Kind regards, > Nicolas DUMINIL -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 4 15:24:00 2017 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Tue, 4 Apr 2017 15:24:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2089) Can't use Arquillian with WebSphere 8.5.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Poul closed ARQ-2089. ----------------------------- > Can't use Arquillian with WebSphere 8.5.5 > ----------------------------------------- > > Key: ARQ-2089 > URL: https://issues.jboss.org/browse/ARQ-2089 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Environment: WebSphere Application Server Full Profile (WAS), on Windows 10. Java 6 (requirement for WebSphere 8.5.5) > Reporter: nicolas duminil > Assignee: Gerhard Poul > > I get the following exception while trying to run arquillian tests on WebSphere 8.5.5: > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.562 sec <<< FAILURE! > be.alphacredit.tests.TestXSDValidationArquillian Time elapsed: 0 sec <<< ERROR! > java.lang.RuntimeException: Could not create new instance of class org.jboss.arquillian.test.impl.EventTestRunnerAdaptor > at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:165) > at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:102) > at org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder.build(TestRunnerAdaptorBuilder.java:52) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:113) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > 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:497) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:161) > ... 15 more > Caused by: java.lang.NoClassDefFoundError: Lcom/ibm/websphere/management/AdminClient; > at java.lang.Class.getDeclaredFields0(Native Method) > at java.lang.Class.privateGetDeclaredFields(Class.java:2583) > at java.lang.Class.getDeclaredFields(Class.java:1916) > at org.jboss.arquillian.core.impl.Reflections.getFieldInjectionPoints(Reflections.java:74) > at org.jboss.arquillian.core.impl.ExtensionImpl.of(ExtensionImpl.java:53) > at org.jboss.arquillian.core.impl.ManagerImpl.inject(ManagerImpl.java:211) > at org.jboss.arquillian.core.impl.InjectorImpl.inject(InjectorImpl.java:58) > at org.jboss.arquillian.core.impl.loadable.ServiceRegistryLoader.createServiceInstance(ServiceRegistryLoader.java:108) > at org.jboss.arquillian.core.impl.loadable.ServiceRegistryLoader.all(ServiceRegistryLoader.java:55) > at org.jboss.arquillian.core.impl.loadable.ServiceRegistryLoader.onlyOne(ServiceRegistryLoader.java:67) > at org.jboss.arquillian.container.impl.LocalContainerRegistry.create(LocalContainerRegistry.java:80) > at org.jboss.arquillian.container.impl.client.container.ContainerRegistryCreator.createRegistry(ContainerRegistryCreator.java:78) > 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:497) > 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.ManagerImpl.bindAndFire(ManagerImpl.java:265) > at org.jboss.arquillian.core.impl.InstanceImpl.set(InstanceImpl.java:74) > at org.jboss.arquillian.config.impl.extension.ConfigurationRegistrar.loadConfiguration(ConfigurationRegistrar.java:73) > 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:497) > 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.ManagerImpl.start(ManagerImpl.java:290) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.(EventTestRunnerAdaptor.java:63) > ... 20 more > Caused by: java.lang.ClassNotFoundException: com.ibm.websphere.management.AdminClient > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 55 more > Here is the relevant part of my POM: > > > com.ibm.websphere.j2ee > j2ee > provided > > ............... > > org.jboss.shrinkwrap.resolver > shrinkwrap-resolver-impl-maven > test > > > org.jboss.arquillian.junit > arquillian-junit-container > test > > > org.jboss.arquillian.protocol > arquillian-protocol-servlet > test > > > org.jboss.arquillian.container > arquillian-was-remote-8.5 > test > > Here is the arquillian.xml file: > > > > target/deployments/ > > > > localhost > 8880 > false > nicolas > > > > And here is my unit test: > @RunWith(Arquillian.class) > public class TestXSDValidationArquillian > { > private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); > > @Deployment > public static Archive createTestArchive() > { > slf4jLogger.info("Loading pom.xml"); > PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); > slf4jLogger.info("pom.xml loaded. Now importing dependencies"); > File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); > slf4jLogger.info("Dependencies loaded. Creating web archive"); > WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); > slf4jLogger.info("Web archive created. Now, adding files to the archive"); > for (File file : libs) > war.addAsLibrary(file); > slf4jLogger.info("Web archive created"); > return war; > } > > @Test > public void test1(){} > } > What might be the problem here ? Many thanks in advance. > Kind regards, > Nicolas -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 4 15:31:00 2017 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Tue, 4 Apr 2017 15:31:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2090) Arquillian test takes more than 5 minutes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13388843#comment-13388843 ] Gerhard Poul commented on ARQ-2090: ----------------------------------- With Liberty Profile you should also be able to use Java 7, 7.1, and 8: http://www-01.ibm.com/support/docview.wss?uid=swg27005002 Not saying that this will fix it; I'd rather first ask you to check that we're not running into any issues with an anti-virus or similar as that is an issue I've seen rather frequently on that platform. If you can you might want to try how long the deployment of the application that is built takes on a liberty when not started through Arquillian to check whether it is faster then when you remove Arquillian from the equation for debugging purposes. > Arquillian test takes more than 5 minutes > ----------------------------------------- > > Key: ARQ-2090 > URL: https://issues.jboss.org/browse/ARQ-2090 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: arquillian-was-remote-8.5:1.0.0-Final, WebSphere 8.5.5 on Windows 10, > Java: IBM J9 VM (build 2.6, JRE 1.6.0 Windows 8 amd64-64 Compressed References 20130301_140166 (JIT enabled, AOT enabled) > Reporter: nicolas duminil > Assignee: Gerhard Poul > > The execution of an Arquillian test (an empty test) takes more than 5 minutes. here is the test: > -{{@RunWith(Arquillian.class) > public class TestXSDValidationArquillian > { > private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); > > @Deployment > public static Archive createTestArchive() > { > slf4jLogger.info("Loading pom.xml"); > PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); > slf4jLogger.info("pom.xml loaded. Now importing dependencies"); > File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); > slf4jLogger.info("Dependencies loaded. Creating web archive"); > WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); > slf4jLogger.info("Web archive created. Now, adding files to the archive"); > for (File file : libs) > war.addAsLibrary(file); > slf4jLogger.info("Web archive created"); > return war; > }- > > @Test > public void test1(){} > }} > An here is the console output: > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running be.alphacredit.tests.TestXSDValidationArquillian > 04-Apr-2017 11:09:59 null null > WARNING: ADMC0046W > 04-Apr-2017 11:10:00 null null > WARNING: Could not find tmx4jTransform.jar in null/etc/tmx4jTransform.jar - Interoperability to older versions of WebSphere is disabled > 04-Apr-2017 11:10:00 null null > INFO: ssl.disable.url.hostname.verification.CWPKI0027I > Loading pom.xml > pom.xml loaded. Now importing dependencies > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-was-remote-8.5/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-was-remote-8.5:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-parent-was/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-parent-was:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > Dependencies loaded. Creating web archive > Web archive created. Now, adding files to the archive > Web archive created > 04-Apr-2017 11:11:00 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at -126388353 ( com.ibm.ws.amm.scan.util.info.impl.test.AnnotationTypeReaderAnno.nestedAnno ) ] Name [ null ] Description [ Lcom/ibm/ws/amm/scan/util/info/impl/test/AnnotationTypeReaderNestedAnno; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1495822839 ( javax.persistence.AssociationOverride.joinTable ) ] Name [ null ] Description [ Ljavax/persistence/JoinTable; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1522521260 ( javax.servlet.annotation.ServletSecurity.value ) ] Name [ null ] Description [ Ljavax/servlet/annotation/HttpConstraint; ] Call in violation of protocol > 04-Apr-2017 11:11:31 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Target server for deployment is WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > 04-Apr-2017 11:14:39 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Application was started on the following targets: WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.094 sec > Results : > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 > As one may see, test starts at 11:09:59 and finishes at 11:14:39 and takes 291.094 seconds. I have googled and found some posts concerning the metadata-complete="true" that I added to my web.xml, as follows: > > > but it didn't help. It seems to be related to the IBM Java 6 but this is the JVM that one is supposed to use with IBM WebSphere. Any idea of what might be the problem here ? > Kind regards, > Nicolas DUMINIL -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Apr 5 04:31:00 2017 From: issues at jboss.org (nicolas duminil (JIRA)) Date: Wed, 5 Apr 2017 04:31:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2090) Arquillian test takes more than 5 minutes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13389100#comment-13389100 ] nicolas duminil commented on ARQ-2090: -------------------------------------- The post above doesn't concenrn WLP (WebSphere Liberty Profile) but WAS 8.5.5. WLP is not production ready and hence we don't use it. And running the same test with IBM Java 7 has exactly the same result. Without Arquillian test the build is instantly, as shown above in the console output. The part which takes the 5 minutes starts with the message "Running be.alphacredit.tests.TestXSDValidationArquillian" at11:09:59. It takes one minute to load the POM, import the dependencies, create the archive and add the dependedncies to the archive. At 11:11:00 the message "Web archive created" shows rhe return from the method createTestArchive(). Then during 31 seconds different warnings are displayed. At 11:11:31 the message "INFO: Target server for deployment is WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1" is displayed and then the deployment of the archive on the remote application server takes 3 minutes and 8 seconds until the message "INFO: Application was started on the following targets: WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1" is displayed. Further, when it comes to the real deployment, in the pre-integration-test phase of maven, the same archive (well almost the same) takes a couple of seconds. The remote server is local, it runs on the same machine. So the question is why the Arquillian deployment takes so long and one of the possible answers is that the server is scanning the archive for annotations. This is what meta-data=complete is supposed to avoid, but it doesn't. Hence my question: does anyone know why ? Kind regards, Nicolas DUMINIL > Arquillian test takes more than 5 minutes > ----------------------------------------- > > Key: ARQ-2090 > URL: https://issues.jboss.org/browse/ARQ-2090 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: arquillian-was-remote-8.5:1.0.0-Final, WebSphere 8.5.5 on Windows 10, > Java: IBM J9 VM (build 2.6, JRE 1.6.0 Windows 8 amd64-64 Compressed References 20130301_140166 (JIT enabled, AOT enabled) > Reporter: nicolas duminil > Assignee: Gerhard Poul > > The execution of an Arquillian test (an empty test) takes more than 5 minutes. here is the test: > -{{@RunWith(Arquillian.class) > public class TestXSDValidationArquillian > { > private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); > > @Deployment > public static Archive createTestArchive() > { > slf4jLogger.info("Loading pom.xml"); > PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); > slf4jLogger.info("pom.xml loaded. Now importing dependencies"); > File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); > slf4jLogger.info("Dependencies loaded. Creating web archive"); > WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); > slf4jLogger.info("Web archive created. Now, adding files to the archive"); > for (File file : libs) > war.addAsLibrary(file); > slf4jLogger.info("Web archive created"); > return war; > }- > > @Test > public void test1(){} > }} > An here is the console output: > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running be.alphacredit.tests.TestXSDValidationArquillian > 04-Apr-2017 11:09:59 null null > WARNING: ADMC0046W > 04-Apr-2017 11:10:00 null null > WARNING: Could not find tmx4jTransform.jar in null/etc/tmx4jTransform.jar - Interoperability to older versions of WebSphere is disabled > 04-Apr-2017 11:10:00 null null > INFO: ssl.disable.url.hostname.verification.CWPKI0027I > Loading pom.xml > pom.xml loaded. Now importing dependencies > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-was-remote-8.5/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-was-remote-8.5:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-parent-was/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-parent-was:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > Dependencies loaded. Creating web archive > Web archive created. Now, adding files to the archive > Web archive created > 04-Apr-2017 11:11:00 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at -126388353 ( com.ibm.ws.amm.scan.util.info.impl.test.AnnotationTypeReaderAnno.nestedAnno ) ] Name [ null ] Description [ Lcom/ibm/ws/amm/scan/util/info/impl/test/AnnotationTypeReaderNestedAnno; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1495822839 ( javax.persistence.AssociationOverride.joinTable ) ] Name [ null ] Description [ Ljavax/persistence/JoinTable; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1522521260 ( javax.servlet.annotation.ServletSecurity.value ) ] Name [ null ] Description [ Ljavax/servlet/annotation/HttpConstraint; ] Call in violation of protocol > 04-Apr-2017 11:11:31 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Target server for deployment is WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > 04-Apr-2017 11:14:39 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Application was started on the following targets: WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.094 sec > Results : > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 > As one may see, test starts at 11:09:59 and finishes at 11:14:39 and takes 291.094 seconds. I have googled and found some posts concerning the metadata-complete="true" that I added to my web.xml, as follows: > > > but it didn't help. It seems to be related to the IBM Java 6 but this is the JVM that one is supposed to use with IBM WebSphere. Any idea of what might be the problem here ? > Kind regards, > Nicolas DUMINIL -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Apr 5 11:43:00 2017 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Wed, 5 Apr 2017 11:43:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2090) Arquillian test takes more than 5 minutes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13389529#comment-13389529 ] Gerhard Poul commented on ARQ-2090: ----------------------------------- Ah sorry, yes; I somehow assumed it was WLP for some reason; can you please provide me with the SystemOut.log and versionInfo.sh -maintenancePackages? > Arquillian test takes more than 5 minutes > ----------------------------------------- > > Key: ARQ-2090 > URL: https://issues.jboss.org/browse/ARQ-2090 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: arquillian-was-remote-8.5:1.0.0-Final, WebSphere 8.5.5 on Windows 10, > Java: IBM J9 VM (build 2.6, JRE 1.6.0 Windows 8 amd64-64 Compressed References 20130301_140166 (JIT enabled, AOT enabled) > Reporter: nicolas duminil > Assignee: Gerhard Poul > > The execution of an Arquillian test (an empty test) takes more than 5 minutes. here is the test: > -{{@RunWith(Arquillian.class) > public class TestXSDValidationArquillian > { > private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); > > @Deployment > public static Archive createTestArchive() > { > slf4jLogger.info("Loading pom.xml"); > PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); > slf4jLogger.info("pom.xml loaded. Now importing dependencies"); > File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); > slf4jLogger.info("Dependencies loaded. Creating web archive"); > WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); > slf4jLogger.info("Web archive created. Now, adding files to the archive"); > for (File file : libs) > war.addAsLibrary(file); > slf4jLogger.info("Web archive created"); > return war; > }- > > @Test > public void test1(){} > }} > An here is the console output: > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running be.alphacredit.tests.TestXSDValidationArquillian > 04-Apr-2017 11:09:59 null null > WARNING: ADMC0046W > 04-Apr-2017 11:10:00 null null > WARNING: Could not find tmx4jTransform.jar in null/etc/tmx4jTransform.jar - Interoperability to older versions of WebSphere is disabled > 04-Apr-2017 11:10:00 null null > INFO: ssl.disable.url.hostname.verification.CWPKI0027I > Loading pom.xml > pom.xml loaded. Now importing dependencies > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-was-remote-8.5/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-was-remote-8.5:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-parent-was/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-parent-was:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > Dependencies loaded. Creating web archive > Web archive created. Now, adding files to the archive > Web archive created > 04-Apr-2017 11:11:00 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at -126388353 ( com.ibm.ws.amm.scan.util.info.impl.test.AnnotationTypeReaderAnno.nestedAnno ) ] Name [ null ] Description [ Lcom/ibm/ws/amm/scan/util/info/impl/test/AnnotationTypeReaderNestedAnno; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1495822839 ( javax.persistence.AssociationOverride.joinTable ) ] Name [ null ] Description [ Ljavax/persistence/JoinTable; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1522521260 ( javax.servlet.annotation.ServletSecurity.value ) ] Name [ null ] Description [ Ljavax/servlet/annotation/HttpConstraint; ] Call in violation of protocol > 04-Apr-2017 11:11:31 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Target server for deployment is WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > 04-Apr-2017 11:14:39 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Application was started on the following targets: WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.094 sec > Results : > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 > As one may see, test starts at 11:09:59 and finishes at 11:14:39 and takes 291.094 seconds. I have googled and found some posts concerning the metadata-complete="true" that I added to my web.xml, as follows: > > > but it didn't help. It seems to be related to the IBM Java 6 but this is the JVM that one is supposed to use with IBM WebSphere. Any idea of what might be the problem here ? > Kind regards, > Nicolas DUMINIL -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Apr 6 03:40:00 2017 From: issues at jboss.org (nicolas duminil (JIRA)) Date: Thu, 6 Apr 2017 03:40:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2090) Arquillian test takes more than 5 minutes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas duminil updated ARQ-2090: --------------------------------- Attachment: versioninfo.txt > Arquillian test takes more than 5 minutes > ----------------------------------------- > > Key: ARQ-2090 > URL: https://issues.jboss.org/browse/ARQ-2090 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: arquillian-was-remote-8.5:1.0.0-Final, WebSphere 8.5.5 on Windows 10, > Java: IBM J9 VM (build 2.6, JRE 1.6.0 Windows 8 amd64-64 Compressed References 20130301_140166 (JIT enabled, AOT enabled) > Reporter: nicolas duminil > Assignee: Gerhard Poul > Attachments: versioninfo.txt > > > The execution of an Arquillian test (an empty test) takes more than 5 minutes. here is the test: > -{{@RunWith(Arquillian.class) > public class TestXSDValidationArquillian > { > private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); > > @Deployment > public static Archive createTestArchive() > { > slf4jLogger.info("Loading pom.xml"); > PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); > slf4jLogger.info("pom.xml loaded. Now importing dependencies"); > File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); > slf4jLogger.info("Dependencies loaded. Creating web archive"); > WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); > slf4jLogger.info("Web archive created. Now, adding files to the archive"); > for (File file : libs) > war.addAsLibrary(file); > slf4jLogger.info("Web archive created"); > return war; > }- > > @Test > public void test1(){} > }} > An here is the console output: > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running be.alphacredit.tests.TestXSDValidationArquillian > 04-Apr-2017 11:09:59 null null > WARNING: ADMC0046W > 04-Apr-2017 11:10:00 null null > WARNING: Could not find tmx4jTransform.jar in null/etc/tmx4jTransform.jar - Interoperability to older versions of WebSphere is disabled > 04-Apr-2017 11:10:00 null null > INFO: ssl.disable.url.hostname.verification.CWPKI0027I > Loading pom.xml > pom.xml loaded. Now importing dependencies > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-was-remote-8.5/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-was-remote-8.5:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-parent-was/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-parent-was:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > Dependencies loaded. Creating web archive > Web archive created. Now, adding files to the archive > Web archive created > 04-Apr-2017 11:11:00 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at -126388353 ( com.ibm.ws.amm.scan.util.info.impl.test.AnnotationTypeReaderAnno.nestedAnno ) ] Name [ null ] Description [ Lcom/ibm/ws/amm/scan/util/info/impl/test/AnnotationTypeReaderNestedAnno; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1495822839 ( javax.persistence.AssociationOverride.joinTable ) ] Name [ null ] Description [ Ljavax/persistence/JoinTable; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1522521260 ( javax.servlet.annotation.ServletSecurity.value ) ] Name [ null ] Description [ Ljavax/servlet/annotation/HttpConstraint; ] Call in violation of protocol > 04-Apr-2017 11:11:31 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Target server for deployment is WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > 04-Apr-2017 11:14:39 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Application was started on the following targets: WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.094 sec > Results : > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 > As one may see, test starts at 11:09:59 and finishes at 11:14:39 and takes 291.094 seconds. I have googled and found some posts concerning the metadata-complete="true" that I added to my web.xml, as follows: > > > but it didn't help. It seems to be related to the IBM Java 6 but this is the JVM that one is supposed to use with IBM WebSphere. Any idea of what might be the problem here ? > Kind regards, > Nicolas DUMINIL -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Apr 6 05:19:00 2017 From: issues at jboss.org (nicolas duminil (JIRA)) Date: Thu, 6 Apr 2017 05:19:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2090) Arquillian test takes more than 5 minutes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas duminil updated ARQ-2090: --------------------------------- Attachment: SystemOut.log > Arquillian test takes more than 5 minutes > ----------------------------------------- > > Key: ARQ-2090 > URL: https://issues.jboss.org/browse/ARQ-2090 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: arquillian-was-remote-8.5:1.0.0-Final, WebSphere 8.5.5 on Windows 10, > Java: IBM J9 VM (build 2.6, JRE 1.6.0 Windows 8 amd64-64 Compressed References 20130301_140166 (JIT enabled, AOT enabled) > Reporter: nicolas duminil > Assignee: Gerhard Poul > Attachments: SystemOut.log, versioninfo.txt > > > The execution of an Arquillian test (an empty test) takes more than 5 minutes. here is the test: > -{{@RunWith(Arquillian.class) > public class TestXSDValidationArquillian > { > private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); > > @Deployment > public static Archive createTestArchive() > { > slf4jLogger.info("Loading pom.xml"); > PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); > slf4jLogger.info("pom.xml loaded. Now importing dependencies"); > File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); > slf4jLogger.info("Dependencies loaded. Creating web archive"); > WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); > slf4jLogger.info("Web archive created. Now, adding files to the archive"); > for (File file : libs) > war.addAsLibrary(file); > slf4jLogger.info("Web archive created"); > return war; > }- > > @Test > public void test1(){} > }} > An here is the console output: > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running be.alphacredit.tests.TestXSDValidationArquillian > 04-Apr-2017 11:09:59 null null > WARNING: ADMC0046W > 04-Apr-2017 11:10:00 null null > WARNING: Could not find tmx4jTransform.jar in null/etc/tmx4jTransform.jar - Interoperability to older versions of WebSphere is disabled > 04-Apr-2017 11:10:00 null null > INFO: ssl.disable.url.hostname.verification.CWPKI0027I > Loading pom.xml > pom.xml loaded. Now importing dependencies > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-was-remote-8.5/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-was-remote-8.5:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-parent-was/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-parent-was:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > Dependencies loaded. Creating web archive > Web archive created. Now, adding files to the archive > Web archive created > 04-Apr-2017 11:11:00 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at -126388353 ( com.ibm.ws.amm.scan.util.info.impl.test.AnnotationTypeReaderAnno.nestedAnno ) ] Name [ null ] Description [ Lcom/ibm/ws/amm/scan/util/info/impl/test/AnnotationTypeReaderNestedAnno; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1495822839 ( javax.persistence.AssociationOverride.joinTable ) ] Name [ null ] Description [ Ljavax/persistence/JoinTable; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1522521260 ( javax.servlet.annotation.ServletSecurity.value ) ] Name [ null ] Description [ Ljavax/servlet/annotation/HttpConstraint; ] Call in violation of protocol > 04-Apr-2017 11:11:31 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Target server for deployment is WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > 04-Apr-2017 11:14:39 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Application was started on the following targets: WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.094 sec > Results : > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 > As one may see, test starts at 11:09:59 and finishes at 11:14:39 and takes 291.094 seconds. I have googled and found some posts concerning the metadata-complete="true" that I added to my web.xml, as follows: > > > but it didn't help. It seems to be related to the IBM Java 6 but this is the JVM that one is supposed to use with IBM WebSphere. Any idea of what might be the problem here ? > Kind regards, > Nicolas DUMINIL -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Apr 6 05:20:00 2017 From: issues at jboss.org (nicolas duminil (JIRA)) Date: Thu, 6 Apr 2017 05:20:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2090) Arquillian test takes more than 5 minutes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas duminil updated ARQ-2090: --------------------------------- Attachment: server1_59bcd553_17.04.06_10.57.28.5878689953196173082500.txt > Arquillian test takes more than 5 minutes > ----------------------------------------- > > Key: ARQ-2090 > URL: https://issues.jboss.org/browse/ARQ-2090 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: arquillian-was-remote-8.5:1.0.0-Final, WebSphere 8.5.5 on Windows 10, > Java: IBM J9 VM (build 2.6, JRE 1.6.0 Windows 8 amd64-64 Compressed References 20130301_140166 (JIT enabled, AOT enabled) > Reporter: nicolas duminil > Assignee: Gerhard Poul > Attachments: SystemOut.log, server1_59bcd553_17.04.06_10.57.28.5878689953196173082500.txt, versioninfo.txt > > > The execution of an Arquillian test (an empty test) takes more than 5 minutes. here is the test: > -{{@RunWith(Arquillian.class) > public class TestXSDValidationArquillian > { > private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); > > @Deployment > public static Archive createTestArchive() > { > slf4jLogger.info("Loading pom.xml"); > PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); > slf4jLogger.info("pom.xml loaded. Now importing dependencies"); > File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); > slf4jLogger.info("Dependencies loaded. Creating web archive"); > WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); > slf4jLogger.info("Web archive created. Now, adding files to the archive"); > for (File file : libs) > war.addAsLibrary(file); > slf4jLogger.info("Web archive created"); > return war; > }- > > @Test > public void test1(){} > }} > An here is the console output: > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running be.alphacredit.tests.TestXSDValidationArquillian > 04-Apr-2017 11:09:59 null null > WARNING: ADMC0046W > 04-Apr-2017 11:10:00 null null > WARNING: Could not find tmx4jTransform.jar in null/etc/tmx4jTransform.jar - Interoperability to older versions of WebSphere is disabled > 04-Apr-2017 11:10:00 null null > INFO: ssl.disable.url.hostname.verification.CWPKI0027I > Loading pom.xml > pom.xml loaded. Now importing dependencies > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-was-remote-8.5/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-was-remote-8.5:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-parent-was/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-parent-was:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > Dependencies loaded. Creating web archive > Web archive created. Now, adding files to the archive > Web archive created > 04-Apr-2017 11:11:00 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at -126388353 ( com.ibm.ws.amm.scan.util.info.impl.test.AnnotationTypeReaderAnno.nestedAnno ) ] Name [ null ] Description [ Lcom/ibm/ws/amm/scan/util/info/impl/test/AnnotationTypeReaderNestedAnno; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1495822839 ( javax.persistence.AssociationOverride.joinTable ) ] Name [ null ] Description [ Ljavax/persistence/JoinTable; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1522521260 ( javax.servlet.annotation.ServletSecurity.value ) ] Name [ null ] Description [ Ljavax/servlet/annotation/HttpConstraint; ] Call in violation of protocol > 04-Apr-2017 11:11:31 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Target server for deployment is WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > 04-Apr-2017 11:14:39 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Application was started on the following targets: WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.094 sec > Results : > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 > As one may see, test starts at 11:09:59 and finishes at 11:14:39 and takes 291.094 seconds. I have googled and found some posts concerning the metadata-complete="true" that I added to my web.xml, as follows: > > > but it didn't help. It seems to be related to the IBM Java 6 but this is the JVM that one is supposed to use with IBM WebSphere. Any idea of what might be the problem here ? > Kind regards, > Nicolas DUMINIL -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Apr 6 05:20:00 2017 From: issues at jboss.org (nicolas duminil (JIRA)) Date: Thu, 6 Apr 2017 05:20:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2090) Arquillian test takes more than 5 minutes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13389936#comment-13389936 ] nicolas duminil commented on ARQ-2090: -------------------------------------- Hello, I'm attaching here the versioninfo output as well as the requested log file. The SystemOut.log file is a fresh one containing only one execution of the arquillian test. The execution takes more than 15 minutes. Exceptions are logged in the ffdc files which I'm attaching as well. Many thanks in advance for your help Kind regards, Nicolas DUMINIL [^SystemOut.log] [^server1_59bcd553_17.04.06_10.57.28.5878689953196173082500.txt] [^versioninfo.txt] > Arquillian test takes more than 5 minutes > ----------------------------------------- > > Key: ARQ-2090 > URL: https://issues.jboss.org/browse/ARQ-2090 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: arquillian-was-remote-8.5:1.0.0-Final, WebSphere 8.5.5 on Windows 10, > Java: IBM J9 VM (build 2.6, JRE 1.6.0 Windows 8 amd64-64 Compressed References 20130301_140166 (JIT enabled, AOT enabled) > Reporter: nicolas duminil > Assignee: Gerhard Poul > Attachments: SystemOut.log, server1_59bcd553_17.04.06_10.57.28.5878689953196173082500.txt, versioninfo.txt > > > The execution of an Arquillian test (an empty test) takes more than 5 minutes. here is the test: > -{{@RunWith(Arquillian.class) > public class TestXSDValidationArquillian > { > private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); > > @Deployment > public static Archive createTestArchive() > { > slf4jLogger.info("Loading pom.xml"); > PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); > slf4jLogger.info("pom.xml loaded. Now importing dependencies"); > File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); > slf4jLogger.info("Dependencies loaded. Creating web archive"); > WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); > slf4jLogger.info("Web archive created. Now, adding files to the archive"); > for (File file : libs) > war.addAsLibrary(file); > slf4jLogger.info("Web archive created"); > return war; > }- > > @Test > public void test1(){} > }} > An here is the console output: > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running be.alphacredit.tests.TestXSDValidationArquillian > 04-Apr-2017 11:09:59 null null > WARNING: ADMC0046W > 04-Apr-2017 11:10:00 null null > WARNING: Could not find tmx4jTransform.jar in null/etc/tmx4jTransform.jar - Interoperability to older versions of WebSphere is disabled > 04-Apr-2017 11:10:00 null null > INFO: ssl.disable.url.hostname.verification.CWPKI0027I > Loading pom.xml > pom.xml loaded. Now importing dependencies > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-was-remote-8.5/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-was-remote-8.5:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-parent-was/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-parent-was:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > Dependencies loaded. Creating web archive > Web archive created. Now, adding files to the archive > Web archive created > 04-Apr-2017 11:11:00 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at -126388353 ( com.ibm.ws.amm.scan.util.info.impl.test.AnnotationTypeReaderAnno.nestedAnno ) ] Name [ null ] Description [ Lcom/ibm/ws/amm/scan/util/info/impl/test/AnnotationTypeReaderNestedAnno; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1495822839 ( javax.persistence.AssociationOverride.joinTable ) ] Name [ null ] Description [ Ljavax/persistence/JoinTable; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1522521260 ( javax.servlet.annotation.ServletSecurity.value ) ] Name [ null ] Description [ Ljavax/servlet/annotation/HttpConstraint; ] Call in violation of protocol > 04-Apr-2017 11:11:31 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Target server for deployment is WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > 04-Apr-2017 11:14:39 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Application was started on the following targets: WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.094 sec > Results : > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 > As one may see, test starts at 11:09:59 and finishes at 11:14:39 and takes 291.094 seconds. I have googled and found some posts concerning the metadata-complete="true" that I added to my web.xml, as follows: > > > but it didn't help. It seems to be related to the IBM Java 6 but this is the JVM that one is supposed to use with IBM WebSphere. Any idea of what might be the problem here ? > Kind regards, > Nicolas DUMINIL -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Apr 6 05:59:00 2017 From: issues at jboss.org (Vsevolod Golovanov (JIRA)) Date: Thu, 6 Apr 2017 05:59:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-500) Navigation with URL parameters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13389980#comment-13389980 ] Vsevolod Golovanov commented on ARQGRA-500: ------------------------------------------- Dumping some additional concerns that bother me. -- Generalize to dynamic path manipulation (DPM)? "Parameters" only make sense for the HTTP scheme currently. The linked SO's OP also wanted more than that. But generalize too much and it looks like another LocationDecider. Might as well check if the test object implememts the LocationDecider interface. No, I think the generalized DPM should be an implementation helper for Deciders. E.g. the HTTP decider would use it to implement the parameter provider functionality and path substitution functionality ("http://static/\{dynamic\}") - 2 different interfaces. But how to expose this functionality in Graphene.goTo? Either be content with some generic DPM interface argument, or refactor goTo to return a specific builder somehow. Make goTo return a builder? Nasty breaking change - goTo now doesn't trigger navigation. Some new method (arguments like goTo) returns a builder, and an argumentless goTo triggers navigation? This could work. -- Need to descriminate the pages. Problem: LocationDecider only knows a String location. Needs to know pageClass too. --- Annotated parameters could accept it as {{\@LocationParameters(for = MyPage.class)}}. > Navigation with URL parameters > ------------------------------ > > Key: ARQGRA-500 > URL: https://issues.jboss.org/browse/ARQGRA-500 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Vsevolod Golovanov > > I need to add a dynamic URL parameter to a location of a page before navigating to it. > I don't want to use Selenium's navigation, because I would then need to reinvent/shoehorn Graphene's location deciding. > A special landing page would be a pretty ugly workaround. > I get that it's not possible with annotations. But at least support this with Graphene.goTo methods. > Actually it may be possible with annotations, if you could supply some provider class? E.g. {{\@Location(value = "MyView.xhtml", parameterProvider = MyParameterProvider.class)}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Apr 6 12:38:00 2017 From: issues at jboss.org (nicolas duminil (JIRA)) Date: Thu, 6 Apr 2017 12:38:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2090) Arquillian test takes more than 5 minutes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13390412#comment-13390412 ] nicolas duminil commented on ARQ-2090: -------------------------------------- I replaced the code in the createArchive() by the following: return (WebArchive) ShrinkWrap.create(ZipImporter.class, "arquillian-test.war").importFrom(new File("target/xsd-validation-war.war")).as(WebArchive.class); and I'm doing: mvn -DskipTests clean install mvn test this way I use the same WAR as the one created in the package phase. this works properly so I reckon that using Maven.resolver().loadPomFromFile() might be the problem as it could create to big archives. I need to dig deeper into that but anyways the issue doesn't seem to be related to Arquillian itself or to the container. I'm closing the ticket. many thanks for your help and support. Kind regards, Nicolas > Arquillian test takes more than 5 minutes > ----------------------------------------- > > Key: ARQ-2090 > URL: https://issues.jboss.org/browse/ARQ-2090 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: arquillian-was-remote-8.5:1.0.0-Final, WebSphere 8.5.5 on Windows 10, > Java: IBM J9 VM (build 2.6, JRE 1.6.0 Windows 8 amd64-64 Compressed References 20130301_140166 (JIT enabled, AOT enabled) > Reporter: nicolas duminil > Assignee: Gerhard Poul > Attachments: SystemOut.log, server1_59bcd553_17.04.06_10.57.28.5878689953196173082500.txt, versioninfo.txt > > > The execution of an Arquillian test (an empty test) takes more than 5 minutes. here is the test: > -{{@RunWith(Arquillian.class) > public class TestXSDValidationArquillian > { > private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); > > @Deployment > public static Archive createTestArchive() > { > slf4jLogger.info("Loading pom.xml"); > PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); > slf4jLogger.info("pom.xml loaded. Now importing dependencies"); > File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); > slf4jLogger.info("Dependencies loaded. Creating web archive"); > WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); > slf4jLogger.info("Web archive created. Now, adding files to the archive"); > for (File file : libs) > war.addAsLibrary(file); > slf4jLogger.info("Web archive created"); > return war; > }- > > @Test > public void test1(){} > }} > An here is the console output: > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running be.alphacredit.tests.TestXSDValidationArquillian > 04-Apr-2017 11:09:59 null null > WARNING: ADMC0046W > 04-Apr-2017 11:10:00 null null > WARNING: Could not find tmx4jTransform.jar in null/etc/tmx4jTransform.jar - Interoperability to older versions of WebSphere is disabled > 04-Apr-2017 11:10:00 null null > INFO: ssl.disable.url.hostname.verification.CWPKI0027I > Loading pom.xml > pom.xml loaded. Now importing dependencies > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-was-remote-8.5/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-was-remote-8.5:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-parent-was/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-parent-was:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > Dependencies loaded. Creating web archive > Web archive created. Now, adding files to the archive > Web archive created > 04-Apr-2017 11:11:00 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at -126388353 ( com.ibm.ws.amm.scan.util.info.impl.test.AnnotationTypeReaderAnno.nestedAnno ) ] Name [ null ] Description [ Lcom/ibm/ws/amm/scan/util/info/impl/test/AnnotationTypeReaderNestedAnno; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1495822839 ( javax.persistence.AssociationOverride.joinTable ) ] Name [ null ] Description [ Ljavax/persistence/JoinTable; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1522521260 ( javax.servlet.annotation.ServletSecurity.value ) ] Name [ null ] Description [ Ljavax/servlet/annotation/HttpConstraint; ] Call in violation of protocol > 04-Apr-2017 11:11:31 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Target server for deployment is WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > 04-Apr-2017 11:14:39 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Application was started on the following targets: WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.094 sec > Results : > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 > As one may see, test starts at 11:09:59 and finishes at 11:14:39 and takes 291.094 seconds. I have googled and found some posts concerning the metadata-complete="true" that I added to my web.xml, as follows: > > > but it didn't help. It seems to be related to the IBM Java 6 but this is the JVM that one is supposed to use with IBM WebSphere. Any idea of what might be the problem here ? > Kind regards, > Nicolas DUMINIL -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Apr 6 12:42:00 2017 From: issues at jboss.org (nicolas duminil (JIRA)) Date: Thu, 6 Apr 2017 12:42:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2090) Arquillian test takes more than 5 minutes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas duminil resolved ARQ-2090. ---------------------------------- Resolution: Done > Arquillian test takes more than 5 minutes > ----------------------------------------- > > Key: ARQ-2090 > URL: https://issues.jboss.org/browse/ARQ-2090 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: arquillian-was-remote-8.5:1.0.0-Final, WebSphere 8.5.5 on Windows 10, > Java: IBM J9 VM (build 2.6, JRE 1.6.0 Windows 8 amd64-64 Compressed References 20130301_140166 (JIT enabled, AOT enabled) > Reporter: nicolas duminil > Assignee: Gerhard Poul > Attachments: SystemOut.log, server1_59bcd553_17.04.06_10.57.28.5878689953196173082500.txt, versioninfo.txt > > > The execution of an Arquillian test (an empty test) takes more than 5 minutes. here is the test: > -{{@RunWith(Arquillian.class) > public class TestXSDValidationArquillian > { > private static final Logger slf4jLogger = LoggerFactory.getLogger(TestXSDValidationArquillian.class); > > @Deployment > public static Archive createTestArchive() > { > slf4jLogger.info("Loading pom.xml"); > PomEquippedResolveStage mavenResolver = Maven.resolver().loadPomFromFile("pom.xml"); > slf4jLogger.info("pom.xml loaded. Now importing dependencies"); > File[] libs = mavenResolver.importRuntimeAndTestDependencies().resolve().withTransitivity().asFile(); > slf4jLogger.info("Dependencies loaded. Creating web archive"); > WebArchive war = ShrinkWrap.create(WebArchive.class, "arquillian-test.war"); > slf4jLogger.info("Web archive created. Now, adding files to the archive"); > for (File file : libs) > war.addAsLibrary(file); > slf4jLogger.info("Web archive created"); > return war; > }- > > @Test > public void test1(){} > }} > An here is the console output: > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running be.alphacredit.tests.TestXSDValidationArquillian > 04-Apr-2017 11:09:59 null null > WARNING: ADMC0046W > 04-Apr-2017 11:10:00 null null > WARNING: Could not find tmx4jTransform.jar in null/etc/tmx4jTransform.jar - Interoperability to older versions of WebSphere is disabled > 04-Apr-2017 11:10:00 null null > INFO: ssl.disable.url.hostname.verification.CWPKI0027I > Loading pom.xml > pom.xml loaded. Now importing dependencies > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-was-remote-8.5/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-was-remote-8.5:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > 04-Apr-2017 11:10:02 org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/jboss/arquillian/container/arquillian-parent-was/1.0.0.Final-SNAPSHOT/maven-metadata.xml from http://repo1.maven.org/maven2/. Reason: > org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.jboss.arquillian.container:arquillian-parent-was:1.0.0.Final-SNAPSHOT/maven-metadata.xml in central (http://repo1.maven.org/maven2) > Dependencies loaded. Creating web archive > Web archive created. Now, adding files to the archive > Web archive created > 04-Apr-2017 11:11:00 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at -126388353 ( com.ibm.ws.amm.scan.util.info.impl.test.AnnotationTypeReaderAnno.nestedAnno ) ] Name [ null ] Description [ Lcom/ibm/ws/amm/scan/util/info/impl/test/AnnotationTypeReaderNestedAnno; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1495822839 ( javax.persistence.AssociationOverride.joinTable ) ] Name [ null ] Description [ Ljavax/persistence/JoinTable; ] Call in violation of protocol > 04-Apr-2017 11:11:03 com.ibm.ws.amm.scan.util.AnnotationInfoDefaultVisitor visitAnnotation > WARNING: [ com.ibm.ws.amm.scan.util.InfoVisitor at -323862990 ] for method [ com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1522521260 ( javax.servlet.annotation.ServletSecurity.value ) ] Name [ null ] Description [ Ljavax/servlet/annotation/HttpConstraint; ] Call in violation of protocol > 04-Apr-2017 11:11:31 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Target server for deployment is WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > 04-Apr-2017 11:14:39 org.jboss.arquillian.container.was.remote_8_5.WebSphereRemoteContainer deploy > INFO: Application was started on the following targets: WebSphere:cell=cac40Node01Cell,node=cac40Node01,server=server1 > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.094 sec > Results : > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 > As one may see, test starts at 11:09:59 and finishes at 11:14:39 and takes 291.094 seconds. I have googled and found some posts concerning the metadata-complete="true" that I added to my web.xml, as follows: > > > but it didn't help. It seems to be related to the IBM Java 6 but this is the JVM that one is supposed to use with IBM WebSphere. Any idea of what might be the problem here ? > Kind regards, > Nicolas DUMINIL -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Apr 10 10:29:00 2017 From: issues at jboss.org (Krassimir Valev (JIRA)) Date: Mon, 10 Apr 2017 10:29:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-501) Error when checking for the invisibility of elements In-Reply-To: References: Message-ID: Krassimir Valev created ARQGRA-501: -------------------------------------- Summary: Error when checking for the invisibility of elements Key: ARQGRA-501 URL: https://issues.jboss.org/browse/ARQGRA-501 Project: Arquillian Graphene Issue Type: Bug Affects Versions: 2.2.0 Reporter: Krassimir Valev I get the following error message, when waiting for an element to disappear: {code:java} java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:653) at java.util.ArrayList.get(ArrayList.java:429) at org.jboss.arquillian.graphene.enricher.WebElementUtils$3.getTarget(WebElementUtils.java:104) at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.getTarget(GrapheneProxyHandler.java:149) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.getTarget(GrapheneContextualHandler.java:189) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:162) at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:47) at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:43) at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:209) at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:96) at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:43) at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:212) at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:208) at com.sun.proxy.$Proxy316.isDisplayed(Unknown Source) at org.openqa.selenium.support.ui.ExpectedConditions$20.apply(ExpectedConditions.java:585) at org.openqa.selenium.support.ui.ExpectedConditions$20.apply(ExpectedConditions.java:581) at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:209) at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:96) {code} The wait condition looks like this: {code:java} return waitGui() .withTimeout(timeout, TimeUnit.SECONDS) .pollingEvery(100, TimeUnit.MILLISECONDS) .ignoring(NoSuchElementException.class, StaleElementReferenceException.class) .ignoring(InvocationTargetException.class) .until(ExpectedConditions.invisibilityOfElementLocated(locator)); {code} The very same condition used to work with graphene-webdriver 2.0.3.Final and selenium-bom 2.50.1, but it fails now after upgrading to graphene-webdriver 2.2.0 and selenium-bom 3.3.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 04:54:00 2017 From: issues at jboss.org (Krassimir Valev (JIRA)) Date: Tue, 11 Apr 2017 04:54:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-500) Navigation with URL parameters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13392046#comment-13392046 ] Krassimir Valev commented on ARQGRA-500: ---------------------------------------- [~vsevolodgolovanov] We implemented something similar for our project a while ago, which turned out to be very simple: - we introduced the convention for placeholders in the Location parameter, e.g. Location("url?param={VALUE}") - in case the placeholder had a sensible default value, which should only we overwritten in certain use cases, you can introduce a new custom annotation, e.g. DefaultLocationParam("VALUE", "1") - with yet another custom annotation you can set a static value per test case {code:java} public void test(@InitialPage @LocationParam(name = "VALUE", value = "2") final PageObject page) { } {code} - the actual replacement happens in a custom LocationEnricher (most likely it is not possible to share the code from a legal standpoint, but hopefully this is enough of a pointer for you) {code:java} public class MyLocationEnricher implements org.jboss.arquillian.test.spi.TestEnricher { @Override public Object[] resolve(final Method method) { // from the method you can get all sorts of information that you need - the PageObject class, annotations, the test class and so on // you can also take a look at the org.jboss.arquillian.graphene.location.LocationEnricher class so see the default behaviour } } {code} You can then override the default behaviour with your own: {code:java} public class MyGrapheneExtension implements org.jboss.arquillian.core.spi.LoadableExtension { @Override public void register(final ExtensionBuilder builder) { builder.override(TestEnricher.class, LocationEnricher.class, MyLocationEnricher.class); } } {code} and the last step is to register your extension with the Arquillian runtime, by creating the file 'org.jboss.arquillian.core.spi.LoadableExtension' in the folder 'META-INF/services'. The file should contain the fully qualified path to your extension, e.g. com.company.graphene.MyGrapheneExtension > Navigation with URL parameters > ------------------------------ > > Key: ARQGRA-500 > URL: https://issues.jboss.org/browse/ARQGRA-500 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Vsevolod Golovanov > > I need to add a dynamic URL parameter to a location of a page before navigating to it. > I don't want to use Selenium's navigation, because I would then need to reinvent/shoehorn Graphene's location deciding. > A special landing page would be a pretty ugly workaround. > I get that it's not possible with annotations. But at least support this with Graphene.goTo methods. > Actually it may be possible with annotations, if you could supply some provider class? E.g. {{\@Location(value = "MyView.xhtml", parameterProvider = MyParameterProvider.class)}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:02:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:02:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1129) Investigate poor performance of JGit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-1129. ------------------------------- Resolution: Done Decommissioned as new OpenShift v3 support is moved to Arquillian Cube > Investigate poor performance of JGit > ------------------------------------ > > Key: ARQ-1129 > URL: https://issues.jboss.org/browse/ARQ-1129 > Project: Arquillian > Issue Type: Task > Components: OpenShift Containers > Affects Versions: openshift_1.0.0.Beta1 > Reporter: Karel Piwko > Priority: Critical > Fix For: openshift_1.0.0.next > > > Git operations take too much time. Investigate why. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:03:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:03:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2036) Migrating to wildfly10, I get an error with the jboss logging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-2036. ------------------------------- Resolution: Won't Fix > Migrating to wildfly10, I get an error with the jboss logging > ------------------------------------------------------------- > > Key: ARQ-2036 > URL: https://issues.jboss.org/browse/ARQ-2036 > Project: Arquillian > Issue Type: Bug > Environment: WildFly10 mode managed in arquillian: > org.wildfly.arquillian:wildfly-arquillian-parent:2.0.0.Final > org.jboss.arquillian:arquillian-build:1.1.11.Final (modelversion: 4.0.0) > Reporter: lamiae obila > Priority: Blocker > > I was migrating my application from Jboss AS7 to Wildfly10 using arquillian for tests. > But, I get this error : > {code:java} > Exception in thread "Remoting "endpoint" task-4" java.lang.NoSuchMethodError: org.jboss.logging.Logger.tracef(Ljava/lang/String;I)V > at org.jboss.remotingjmx.VersionedConectionFactory$ClientVersionReceiver.handleMessage(VersionedConectionFactory.java:158) > at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:456) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {code} > I use the wildfly-arquillian-container-managed: version 2.0.0.Final for my test arquillian. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:03:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:03:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2036) Migrating to wildfly10, I get an error with the jboss logging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13392510#comment-13392510 ] Bartosz Majsak commented on ARQ-2036: ------------------------------------- I would also suggest switching from jmx-protocol to servlet. > Migrating to wildfly10, I get an error with the jboss logging > ------------------------------------------------------------- > > Key: ARQ-2036 > URL: https://issues.jboss.org/browse/ARQ-2036 > Project: Arquillian > Issue Type: Bug > Environment: WildFly10 mode managed in arquillian: > org.wildfly.arquillian:wildfly-arquillian-parent:2.0.0.Final > org.jboss.arquillian:arquillian-build:1.1.11.Final (modelversion: 4.0.0) > Reporter: lamiae obila > Priority: Blocker > > I was migrating my application from Jboss AS7 to Wildfly10 using arquillian for tests. > But, I get this error : > {code:java} > Exception in thread "Remoting "endpoint" task-4" java.lang.NoSuchMethodError: org.jboss.logging.Logger.tracef(Ljava/lang/String;I)V > at org.jboss.remotingjmx.VersionedConectionFactory$ClientVersionReceiver.handleMessage(VersionedConectionFactory.java:158) > at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:456) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {code} > I use the wildfly-arquillian-container-managed: version 2.0.0.Final for my test arquillian. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:04:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:04:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-467) Could not connect to container - Arquillian alpha 4 with Jboss 5.1 EAP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-467. ------------------------------ Resolution: Out of Date Labels: (was: new_and_noteworthy) > Could not connect to container - Arquillian alpha 4 with Jboss 5.1 EAP > ---------------------------------------------------------------------- > > Key: ARQ-467 > URL: https://issues.jboss.org/browse/ARQ-467 > Project: Arquillian > Issue Type: CTS Challenge > Components: JBoss AS Containers > Affects Versions: 1.0.0.Alpha4 > Environment: Windows XP , JBoss 5.1 EAP, IntelliJ 10.03 > Reporter: Niraj Adhikary > Priority: Blocker > > Hi All, > I am getting the issue when running the junit test case against JBoss 5.1 EAP using Arquillian alpha 4 in IntelliJ. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:08:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:08:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-911) Report better error if ssh key is not registered with OpenShift account In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-911. ------------------------------ Resolution: Out of Date Decommissioned as new OpenShift v3 support is moved to [Arquillian Cube|http://arquillian.org/arquillian-cube/#_kubernetes]. > Report better error if ssh key is not registered with OpenShift account > ----------------------------------------------------------------------- > > Key: ARQ-911 > URL: https://issues.jboss.org/browse/ARQ-911 > Project: Arquillian > Issue Type: Enhancement > Components: OpenShift Containers > Affects Versions: openshift_1.0.0.Beta1 > Reporter: Dan Allen > Priority: Critical > > The OpenShift container clones the remote git repository configured in arquillian.xml into a temporary directory to exchange files with the test application. The clone is performed over an SSH connection that's negotiated using a public/private RSA key pair. If the public key is not registered with the account, the test fails with the following exception: > {quote} > Exception caught during execution of fetch command > TransportException session is down > {quote} > This sends the developer on a wild goose chase because this error is reported for just about any kind of SSH connection failure. > The problem is revealed if you attempt to ssh into the account: > {quote} > Permission denied (publickey,gssapi-keyex,gssapi-with-mic). > {quote} > It would be nice if we could find a way to get this message to be passed through. However, it might be even more useful if we recognize that the connection failure is mostly likely the result of the key not being registered and we can advice the developer > a) how to register it (the client tool command) > b) how to check it > {code} > rhc sshkey add -k ~/.ssh/libra_id_rsa.pub -i libra > ssh -i ~/.ssh/libra_id_rsa 123456789123456789 at TEST_APP-USER_DOMAIN.rhcloud.com > {code} > The full stack trace of the exception is below: > {code} > org.eclipse.jgit.api.errors.JGitInternalException: Exception caught during execution of fetch command > at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:138) > at org.eclipse.jgit.api.CloneCommand.fetch(CloneCommand.java:175) > at org.eclipse.jgit.api.CloneCommand.call(CloneCommand.java:121) > at org.jboss.arquillian.container.openshift.express.OpenShiftRepository.initialize(OpenShiftRepository.java:235) > at org.jboss.arquillian.container.openshift.express.OpenShiftRepository.(OpenShiftRepository.java:75) > at org.jboss.arquillian.container.openshift.express.OpenShiftExpressContainer.start(OpenShiftExpressContainer.java:102) > at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:198) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > 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.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > 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:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:86) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > 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.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:68) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:97) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > Caused by: org.eclipse.jgit.errors.TransportException: ssh://123456789123456789 at TEST_APP-USER_DOMAIN.rhcloud.com/~/git/TEST_APP.git/: session is down > at org.eclipse.jgit.transport.JschSession$JschProcess.(JschSession.java:154) > at org.eclipse.jgit.transport.JschSession$JschProcess.(JschSession.java:118) > at org.eclipse.jgit.transport.JschSession.exec(JschSession.java:91) > at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.(TransportGitSsh.java:248) > at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:147) > at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:127) > at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:113) > at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1062) > at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:129) > ... 72 more > Caused by: com.jcraft.jsch.JSchException: session is down > at com.jcraft.jsch.Session.openChannel(Session.java:762) > at org.eclipse.jgit.transport.JschSession$JschProcess.(JschSession.java:147) > ... 80 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:09:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:09:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-922) Delete temporary git repository on exit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-922. ------------------------------ Resolution: Out of Date Decommissioned as new OpenShift v3 support is moved to [Arquillian Cube|http://arquillian.org/arquillian-cube/#_kubernetes]. > Delete temporary git repository on exit > --------------------------------------- > > Key: ARQ-922 > URL: https://issues.jboss.org/browse/ARQ-922 > Project: Arquillian > Issue Type: Bug > Components: OpenShift Containers > Affects Versions: openshift_1.0.0.Beta1 > Reporter: Dan Allen > Priority: Minor > > The temporary git repository is not being cleaned up properly on exit. The directory is marked to be deleted on exit of the VM, but for some reason it isn't working. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:09:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:09:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-875) Use AS7 Deploy Ping Servlet to extract ProtocolMetadata In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-875. ------------------------------ Resolution: Done Decommissioned as new OpenShift v3 support is moved to [Arquillian Cube|http://arquillian.org/arquillian-cube/#_kubernetes]. > Use AS7 Deploy Ping Servlet to extract ProtocolMetadata > ------------------------------------------------------- > > Key: ARQ-875 > URL: https://issues.jboss.org/browse/ARQ-875 > Project: Arquillian > Issue Type: Feature Request > Components: OpenShift Containers > Affects Versions: openshift_1.0.0.Beta1 > Reporter: Aslak Knutsen > > Instead of doing Archive scanning to figure out the ProtocolMetadata, we could reuse the Ping Servlet we use to check if the deployment is done to return the ProtocolMetadata from inside the server. > The Wait For: > https://github.com/arquillian/arquillian-container-openshift/blob/master/openshift-express/src/main/java/org/jboss/arquillian/container/openshift/express/OpenShiftExpressContainer.java#L230 > The Extractor: > https://github.com/arquillian/arquillian-container-openshift/blob/master/openshift-express/src/main/java/org/jboss/arquillian/container/openshift/express/ping/DeploymentServlet.java > Similar MGM API Calls from AS7: > https://github.com/jbossas/jboss-as/blob/master/arquillian/common/src/main/java/org/jboss/as/arquillian/container/ManagementClient.java#L116 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:11:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:11:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-623) openshift - provide better way of detecting deployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-623. ------------------------------ Resolution: Out of Date Decommissioned as new OpenShift v3 support is moved to [Arquillian Cube|http://arquillian.org/arquillian-cube/#_kubernetes]. > openshift - provide better way of detecting deployment > ------------------------------------------------------ > > Key: ARQ-623 > URL: https://issues.jboss.org/browse/ARQ-623 > Project: Arquillian > Issue Type: Feature Request > Components: OpenShift Containers > Affects Versions: openshift_1.0.0.Alpha1 > Reporter: Jozef Hartinger > Fix For: openshift_1.0.0.next > > > Currently, org.jboss.arquillian.container.openshift.express.ping.DeploymentServlet is used to detect whether an archive being tested has been deployed yet. The DeploymentServlet uses calls to the AS7 management API. However, the DeploymentServlet does not act gracefully in cases when the application has not been deployed yet. Instead the operation causes the following stacktrace in the server log. > Given the fact that arq is polling the server (stacktrace appears on every attempt), this can be very confusing to the end user. A stacktrace in the server log can easily lead her to the conclusion that the deployment was not successful even if it was. > {noformat} > 04:18:48,740 ERROR [org.jboss.as.controller] (http--127.1.30.1-8080-1) Operation ("read-resource") failed - address: ([("deployment" => "rest-tasks.war")]): java.util.NoSuchElementException: "deployment" => "rest-tasks.war" > at org.jboss.as.controller.registry.BasicResource.requireChild(BasicResource.java:95) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.as.controller.ModelControllerImpl$RootResource.requireChild(ModelControllerImpl.java:423) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.as.controller.OperationContextImpl.readResource(OperationContextImpl.java:759) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$ReadResourceHandler.doExecute(GlobalOperationHandlers.java:151) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:828) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.as.controller.OperationContextImpl.executeStep(OperationContextImpl.java:351) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.as.controller.OperationContextImpl.doCompleteStep(OperationContextImpl.java:298) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.as.controller.OperationContextImpl.completeStep(OperationContextImpl.java:223) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:350) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.as.controller.OperationContextImpl.executeStep(OperationContextImpl.java:351) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.as.controller.OperationContextImpl.doCompleteStep(OperationContextImpl.java:298) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.as.controller.OperationContextImpl.completeStep(OperationContextImpl.java:223) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:119) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.arquillian.container.openshift.express.ping.DeploymentServlet.deploymentExists(DeploymentServlet.java:51) [classes:] > at org.jboss.arquillian.container.openshift.express.ping.DeploymentServlet.doGet(DeploymentServlet.java:34) [classes:] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.1.Final.jar:7.0.1.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at java.lang.Thread.run(Thread.java:636) [:1.6.0_20] > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:21:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:21:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2091) Provider programmatic DSL to seed data In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2091: ----------------------------------- Summary: Provider programmatic DSL to seed data Key: ARQ-2091 URL: https://issues.jboss.org/browse/ARQ-2091 Project: Arquillian Issue Type: Epic Components: Extension - Persistence Affects Versions: persistence_1.0.0.next Reporter: Bartosz Majsak Assignee: Bartosz Majsak Next to annotation driven approach programmatic, DSL based solution would bring a lot of value. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:28:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:28:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2092) Provide standalone support for seeding datasources In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2092: ----------------------------------- Summary: Provide standalone support for seeding datasources Key: ARQ-2092 URL: https://issues.jboss.org/browse/ARQ-2092 Project: Arquillian Issue Type: Story Components: Extension - Persistence Affects Versions: persistence_1.0.0.next Reporter: Bartosz Majsak Assignee: Bartosz Majsak Providing standalone DSL for seeding data sources would let users write black-box tests with control over their data store of choice. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:29:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:29:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2093) Bring SQL DSL for in-container tests In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2093: ----------------------------------- Summary: Bring SQL DSL for in-container tests Key: ARQ-2093 URL: https://issues.jboss.org/browse/ARQ-2093 Project: Arquillian Issue Type: Story Components: Extension - Persistence Affects Versions: persistence_1.0.0.next Reporter: Bartosz Majsak Assignee: Bartosz Majsak As first step bringing DSL to SQL / JPA in-container functionality would be a valuable option for developers. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:32:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:32:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2094) Create DSL with SPI hooks In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2094: ----------------------------------- Summary: Create DSL with SPI hooks Key: ARQ-2094 URL: https://issues.jboss.org/browse/ARQ-2094 Project: Arquillian Issue Type: Sub-task Components: Extension - Persistence Affects Versions: persistence_1.0.0.next Reporter: Bartosz Majsak Assignee: Alex Soto Fix For: persistence_1.0.0.next Design API and SPI for "populator" / standalone DSL for seeding datasources. This will enable us to provide programmatic control over datasources and also easily plug-in other than SQL data storage engines. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:33:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:33:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2095) Support for MongoDB in standalone DSL In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2095: ----------------------------------- Summary: Support for MongoDB in standalone DSL Key: ARQ-2095 URL: https://issues.jboss.org/browse/ARQ-2095 Project: Arquillian Issue Type: Sub-task Components: Extension - Persistence Affects Versions: persistence_1.0.0.next Reporter: Bartosz Majsak Assignee: Alex Soto Fix For: persistence_1.0.0.next -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:34:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:34:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2097) Support for Couchbase in standalone DSL In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2097: ----------------------------------- Summary: Support for Couchbase in standalone DSL Key: ARQ-2097 URL: https://issues.jboss.org/browse/ARQ-2097 Project: Arquillian Issue Type: Sub-task Components: Extension - Persistence Affects Versions: persistence_1.0.0.next Reporter: Bartosz Majsak Assignee: Alex Soto Fix For: persistence_1.0.0.next -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:34:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:34:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2096) Support for Redis in standalone DSL In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2096: ----------------------------------- Summary: Support for Redis in standalone DSL Key: ARQ-2096 URL: https://issues.jboss.org/browse/ARQ-2096 Project: Arquillian Issue Type: Sub-task Components: Extension - Persistence Affects Versions: persistence_1.0.0.next Reporter: Bartosz Majsak Assignee: Alex Soto Fix For: persistence_1.0.0.next -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:35:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:35:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2099) Support for Flyway/SQL seeding in standalone DSL In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2099: ----------------------------------- Summary: Support for Flyway/SQL seeding in standalone DSL Key: ARQ-2099 URL: https://issues.jboss.org/browse/ARQ-2099 Project: Arquillian Issue Type: Sub-task Components: Extension - Persistence Affects Versions: persistence_1.0.0.next Reporter: Bartosz Majsak Assignee: Alex Soto Fix For: persistence_1.0.0.next -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:35:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:35:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2098) Support for DBUnit/SQL seeding in standalone DSL In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2098: ----------------------------------- Summary: Support for DBUnit/SQL seeding in standalone DSL Key: ARQ-2098 URL: https://issues.jboss.org/browse/ARQ-2098 Project: Arquillian Issue Type: Sub-task Components: Extension - Persistence Affects Versions: persistence_1.0.0.next Reporter: Bartosz Majsak Assignee: Alex Soto Fix For: persistence_1.0.0.next -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:36:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:36:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2094) Create DSL with SPI hooks In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2094: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-persistence/pull/59 > Create DSL with SPI hooks > ------------------------- > > Key: ARQ-2094 > URL: https://issues.jboss.org/browse/ARQ-2094 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.next > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > > Design API and SPI for "populator" / standalone DSL for seeding datasources. > This will enable us to provide programmatic control over datasources and also easily plug-in other than SQL data storage engines. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:36:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:36:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2094) Create DSL with SPI hooks In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2094: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Create DSL with SPI hooks > ------------------------- > > Key: ARQ-2094 > URL: https://issues.jboss.org/browse/ARQ-2094 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.next > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > > Design API and SPI for "populator" / standalone DSL for seeding datasources. > This will enable us to provide programmatic control over datasources and also easily plug-in other than SQL data storage engines. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:36:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:36:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2095) Support for MongoDB in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2095: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-persistence/pull/59 > Support for MongoDB in standalone DSL > ------------------------------------- > > Key: ARQ-2095 > URL: https://issues.jboss.org/browse/ARQ-2095 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.next > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:37:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:37:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2097) Support for Couchbase in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2097: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-persistence/pull/61 > Support for Couchbase in standalone DSL > --------------------------------------- > > Key: ARQ-2097 > URL: https://issues.jboss.org/browse/ARQ-2097 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.next > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:37:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:37:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2097) Support for Couchbase in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2097: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Support for Couchbase in standalone DSL > --------------------------------------- > > Key: ARQ-2097 > URL: https://issues.jboss.org/browse/ARQ-2097 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.next > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:37:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:37:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2095) Support for MongoDB in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2095: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Support for MongoDB in standalone DSL > ------------------------------------- > > Key: ARQ-2095 > URL: https://issues.jboss.org/browse/ARQ-2095 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.next > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:37:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:37:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2096) Support for Redis in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2096: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Support for Redis in standalone DSL > ----------------------------------- > > Key: ARQ-2096 > URL: https://issues.jboss.org/browse/ARQ-2096 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.next > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:37:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:37:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2096) Support for Redis in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2096: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-persistence/pull/59 > Support for Redis in standalone DSL > ----------------------------------- > > Key: ARQ-2096 > URL: https://issues.jboss.org/browse/ARQ-2096 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.next > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:38:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:38:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2098) Support for DBUnit/SQL seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2098: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-persistence/pull/63 > Support for DBUnit/SQL seeding in standalone DSL > ------------------------------------------------ > > Key: ARQ-2098 > URL: https://issues.jboss.org/browse/ARQ-2098 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.next > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:38:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:38:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2098) Support for DBUnit/SQL seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2098: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Support for DBUnit/SQL seeding in standalone DSL > ------------------------------------------------ > > Key: ARQ-2098 > URL: https://issues.jboss.org/browse/ARQ-2098 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.next > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:43:02 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:43:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2099) Support for Flyway/SQL seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2099: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-persistence/pull/72 > Support for Flyway/SQL seeding in standalone DSL > ------------------------------------------------ > > Key: ARQ-2099 > URL: https://issues.jboss.org/browse/ARQ-2099 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.next > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:43:02 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:43:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2099) Support for Flyway/SQL seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2099: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Support for Flyway/SQL seeding in standalone DSL > ------------------------------------------------ > > Key: ARQ-2099 > URL: https://issues.jboss.org/browse/ARQ-2099 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.next > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:43:02 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:43:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2092) Provide standalone support for seeding datasources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak reassigned ARQ-2092: ----------------------------------- Assignee: Alex Soto (was: Bartosz Majsak) > Provide standalone support for seeding datasources > -------------------------------------------------- > > Key: ARQ-2092 > URL: https://issues.jboss.org/browse/ARQ-2092 > Project: Arquillian > Issue Type: Story > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.next > Reporter: Bartosz Majsak > Assignee: Alex Soto > > Providing standalone DSL for seeding data sources would let users write black-box tests with control over their data store of choice. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:45:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:45:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2100) Support for Vault seeding in standalone DSL In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2100: ----------------------------------- Summary: Support for Vault seeding in standalone DSL Key: ARQ-2100 URL: https://issues.jboss.org/browse/ARQ-2100 Project: Arquillian Issue Type: Sub-task Components: Extension - Persistence Affects Versions: persistence_1.0.0.next Reporter: Bartosz Majsak Assignee: Alex Soto -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:45:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:45:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2100) Support for Vault seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2100: -------------------------------- Affects Version/s: (was: persistence_1.0.0.next) > Support for Vault seeding in standalone DSL > ------------------------------------------- > > Key: ARQ-2100 > URL: https://issues.jboss.org/browse/ARQ-2100 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:45:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:45:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2100) Support for Vault seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2100: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Support for Vault seeding in standalone DSL > ------------------------------------------- > > Key: ARQ-2100 > URL: https://issues.jboss.org/browse/ARQ-2100 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:45:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:45:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2100) Support for Vault seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2100: -------------------------------- Fix Version/s: persistence_1.0.0.next > Support for Vault seeding in standalone DSL > ------------------------------------------- > > Key: ARQ-2100 > URL: https://issues.jboss.org/browse/ARQ-2100 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:45:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:45:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2091) Provider programmatic DSL to seed data In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2091: -------------------------------- Description: Next to annotation driven approach, programmatic, DSL based solution would bring a lot of value. (was: Next to annotation driven approach programmatic, DSL based solution would bring a lot of value.) > Provider programmatic DSL to seed data > -------------------------------------- > > Key: ARQ-2091 > URL: https://issues.jboss.org/browse/ARQ-2091 > Project: Arquillian > Issue Type: Epic > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.next > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > > Next to annotation driven approach, programmatic, DSL based solution would bring a lot of value. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:45:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:45:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2100) Support for Vault seeding in standalone DSL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2100: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-persistence/pull/73 > Support for Vault seeding in standalone DSL > ------------------------------------------- > > Key: ARQ-2100 > URL: https://issues.jboss.org/browse/ARQ-2100 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 14:46:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 14:46:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2091) Provider programmatic DSL to seed data In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2091: -------------------------------- Description: Next to annotation-driven approach, programmatic, DSL-based solution would bring a lot of value. (was: Next to annotation driven approach, programmatic, DSL based solution would bring a lot of value.) > Provider programmatic DSL to seed data > -------------------------------------- > > Key: ARQ-2091 > URL: https://issues.jboss.org/browse/ARQ-2091 > Project: Arquillian > Issue Type: Epic > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.next > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > > Next to annotation-driven approach, programmatic, DSL-based solution would bring a lot of value. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 15:00:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 15:00:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2101) Improves connection handling In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2101: ----------------------------------- Summary: Improves connection handling Key: ARQ-2101 URL: https://issues.jboss.org/browse/ARQ-2101 Project: Arquillian Issue Type: Sub-task Components: Extension - Persistence Reporter: Bartosz Majsak Assignee: Alex Soto Fix For: persistence_1.0.0.next Improves when connect and disconnect are called, currently connect and disconnect happens once per test method. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 15:01:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 15:01:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2102) Add an option to set schema to use In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2102: ----------------------------------- Summary: Add an option to set schema to use Key: ARQ-2102 URL: https://issues.jboss.org/browse/ARQ-2102 Project: Arquillian Issue Type: Sub-task Components: Extension - Persistence Reporter: Bartosz Majsak Assignee: Alex Soto Fix For: persistence_1.0.0.next For DBUnit add schema handling -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 15:01:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 15:01:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2102) Add an option to set schema to use In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2102: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-persistence/pull/71 > Add an option to set schema to use > ---------------------------------- > > Key: ARQ-2102 > URL: https://issues.jboss.org/browse/ARQ-2102 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > > For DBUnit add schema handling -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 15:02:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 15:02:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2103) Provides APE DSL in-container In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2103: ----------------------------------- Summary: Provides APE DSL in-container Key: ARQ-2103 URL: https://issues.jboss.org/browse/ARQ-2103 Project: Arquillian Issue Type: Sub-task Components: Extension - Persistence Reporter: Bartosz Majsak Assignee: Bartosz Majsak Fix For: persistence_1.0.0.next -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 11 15:02:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 11 Apr 2017 15:02:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2103) Provides APE DSL in-container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2103: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-persistence/pull/70 > Provides APE DSL in-container > ----------------------------- > > Key: ARQ-2103 > URL: https://issues.jboss.org/browse/ARQ-2103 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Apr 12 03:27:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Wed, 12 Apr 2017 03:27:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2104) Make configuration objects injectable to tests In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2104: ----------------------------------- Summary: Make configuration objects injectable to tests Key: ARQ-2104 URL: https://issues.jboss.org/browse/ARQ-2104 Project: Arquillian Issue Type: Enhancement Components: Extension - Persistence Reporter: Bartosz Majsak Assignee: Bartosz Majsak Fix For: persistence_1.0.0.next When writing tests having access to configuration objects such as: * PersistenceConfiguration * DBUnitConfiguration * ScriptingConfiguration might help developers writing simpler tests - e.g. refer to default datasource when using DSL to seed the data. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Apr 12 09:43:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Wed, 12 Apr 2017 09:43:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2103) Provides APE DSL in-container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2103: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Upstream [a738ba6](https://github.com/arquillian/arquillian-extension-persistence/commit/a738ba6ed936fb6ab667a16ca0d5d717a0035ec4) > Provides APE DSL in-container > ----------------------------- > > Key: ARQ-2103 > URL: https://issues.jboss.org/browse/ARQ-2103 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Apr 12 09:44:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Wed, 12 Apr 2017 09:44:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2103) Provides APE DSL in-container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13393025#comment-13393025 ] Bartosz Majsak edited comment on ARQ-2103 at 4/12/17 9:43 AM: -------------------------------------------------------------- Upstream [@a738ba6|https://github.com/arquillian/arquillian-extension-persistence/commit/a738ba6ed936fb6ab667a16ca0d5d717a0035ec4]. was (Author: bmajsak): Upstream [a738ba6](https://github.com/arquillian/arquillian-extension-persistence/commit/a738ba6ed936fb6ab667a16ca0d5d717a0035ec4) > Provides APE DSL in-container > ----------------------------- > > Key: ARQ-2103 > URL: https://issues.jboss.org/browse/ARQ-2103 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Apr 12 13:16:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Wed, 12 Apr 2017 13:16:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2102) Add an option to set schema to use In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto updated ARQ-2102: --------------------------- Git Pull Request: https://github.com/arquillian/arquillian-extension-persistence/pull/76 (was: https://github.com/arquillian/arquillian-extension-persistence/pull/71) > Add an option to set schema to use > ---------------------------------- > > Key: ARQ-2102 > URL: https://issues.jboss.org/browse/ARQ-2102 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > > For DBUnit add schema handling -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Apr 12 13:17:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Wed, 12 Apr 2017 13:17:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2102) Add an option to set schema to use In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto updated ARQ-2102: --------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add an option to set schema to use > ---------------------------------- > > Key: ARQ-2102 > URL: https://issues.jboss.org/browse/ARQ-2102 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Alex Soto > Fix For: persistence_1.0.0.next > > > For DBUnit add schema handling -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Apr 12 13:23:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Wed, 12 Apr 2017 13:23:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2105) Add JUnit Rule support in client populators In-Reply-To: References: Message-ID: Alex Soto created ARQ-2105: ------------------------------ Summary: Add JUnit Rule support in client populators Key: ARQ-2105 URL: https://issues.jboss.org/browse/ARQ-2105 Project: Arquillian Issue Type: Sub-task Reporter: Alex Soto -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Apr 12 13:23:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Wed, 12 Apr 2017 13:23:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2105) Add JUnit Rule support in client populators In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto reassigned ARQ-2105: ------------------------------ Assignee: Alex Soto > Add JUnit Rule support in client populators > ------------------------------------------- > > Key: ARQ-2105 > URL: https://issues.jboss.org/browse/ARQ-2105 > Project: Arquillian > Issue Type: Sub-task > Reporter: Alex Soto > Assignee: Alex Soto > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Apr 13 03:39:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 13 Apr 2017 03:39:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2104) Make configuration objects injectable to tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARQ-2104 started by Bartosz Majsak. ------------------------------------------- > Make configuration objects injectable to tests > ---------------------------------------------- > > Key: ARQ-2104 > URL: https://issues.jboss.org/browse/ARQ-2104 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > When writing tests having access to configuration objects such as: > * PersistenceConfiguration > * DBUnitConfiguration > * ScriptingConfiguration > might help developers writing simpler tests - e.g. refer to default datasource when using DSL to seed the data. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Apr 13 06:16:00 2017 From: issues at jboss.org (Dipak Pawar (JIRA)) Date: Thu, 13 Apr 2017 06:16:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1836) Support HtmlUnitDriver client options In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dipak Pawar reassigned ARQ-1836: -------------------------------- Assignee: Dipak Pawar > Support HtmlUnitDriver client options > ------------------------------------- > > Key: ARQ-1836 > URL: https://issues.jboss.org/browse/ARQ-1836 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Dipak Pawar > Fix For: drone_2.1.0.Final > > > There are options that could be set for HtmlUnitDriver but are not available in Drone configuration. > Drone would need to proxy HtmlUnitDriver and override protected {{modifyWebClient}} method because this is not exposed in Selenium. > https://code.google.com/p/selenium/source/browse/java/client/src/org/openqa/selenium/htmlunit/HtmlUnitDriver.java?r=1615e198f0e0b9d7a0cc60bedf475fe23b9c7e1e#266 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Apr 13 06:17:00 2017 From: issues at jboss.org (Dipak Pawar (JIRA)) Date: Thu, 13 Apr 2017 06:17:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1836) Support HtmlUnitDriver client options In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13393454#comment-13393454 ] Dipak Pawar commented on ARQ-1836: ---------------------------------- Implemented this functionality in https://github.com/arquillian/arquillian-extension-drone/pull/85 > Support HtmlUnitDriver client options > ------------------------------------- > > Key: ARQ-1836 > URL: https://issues.jboss.org/browse/ARQ-1836 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Dipak Pawar > Fix For: drone_2.1.0.Final > > > There are options that could be set for HtmlUnitDriver but are not available in Drone configuration. > Drone would need to proxy HtmlUnitDriver and override protected {{modifyWebClient}} method because this is not exposed in Selenium. > https://code.google.com/p/selenium/source/browse/java/client/src/org/openqa/selenium/htmlunit/HtmlUnitDriver.java?r=1615e198f0e0b9d7a0cc60bedf475fe23b9c7e1e#266 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Apr 13 06:22:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 13 Apr 2017 06:22:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2104) Make configuration objects injectable to tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak resolved ARQ-2104. --------------------------------- Resolution: Done Upstream [@997b0ae|997b0ae66a00d0388fc36cec81ddd75d5a1c737d] > Make configuration objects injectable to tests > ---------------------------------------------- > > Key: ARQ-2104 > URL: https://issues.jboss.org/browse/ARQ-2104 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > When writing tests having access to configuration objects such as: > * PersistenceConfiguration > * DBUnitConfiguration > * ScriptingConfiguration > might help developers writing simpler tests - e.g. refer to default datasource when using DSL to seed the data. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 18 07:18:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 18 Apr 2017 07:18:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2106) Browser configuration shouldn't be case sensitive In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2106: ----------------------------------- Summary: Browser configuration shouldn't be case sensitive Key: ARQ-2106 URL: https://issues.jboss.org/browse/ARQ-2106 Project: Arquillian Issue Type: Feature Request Components: Extension - Drone Affects Versions: drone_2.1.0.Beta1 Reporter: Matous Jobanek Assignee: Dipak Pawar Don't differentiate htmlunit / htmlUnit and internetExplorer / internetexplorer -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 18 07:18:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 18 Apr 2017 07:18:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2106) Browser configuration shouldn't be case sensitive In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2106: -------------------------------- Fix Version/s: drone_2.1.0 > Browser configuration shouldn't be case sensitive > ------------------------------------------------- > > Key: ARQ-2106 > URL: https://issues.jboss.org/browse/ARQ-2106 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.1.0.Beta1 > Reporter: Matous Jobanek > Assignee: Dipak Pawar > Fix For: drone_2.1.0 > > > Don't differentiate htmlunit / htmlUnit and internetExplorer / internetexplorer -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 18 07:19:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 18 Apr 2017 07:19:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2106) Browser configuration shouldn't be case sensitive In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2106: -------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-extension-drone/pull/84 > Browser configuration shouldn't be case sensitive > ------------------------------------------------- > > Key: ARQ-2106 > URL: https://issues.jboss.org/browse/ARQ-2106 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.1.0.Beta1 > Reporter: Matous Jobanek > Assignee: Dipak Pawar > Fix For: drone_2.1.0 > > > Don't differentiate htmlunit / htmlUnit and internetExplorer / internetexplorer -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 18 07:20:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 18 Apr 2017 07:20:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2106) Browser configuration shouldn't be case sensitive In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2106. ------------------------------- Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/87a1d762f887b3f53003d8fe6f38fcd3facb3cee > Browser configuration shouldn't be case sensitive > ------------------------------------------------- > > Key: ARQ-2106 > URL: https://issues.jboss.org/browse/ARQ-2106 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.1.0.Beta1 > Reporter: Matous Jobanek > Assignee: Dipak Pawar > Fix For: drone_2.1.0 > > > Don't differentiate htmlunit / htmlUnit and internetExplorer / internetexplorer -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 18 10:00:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 18 Apr 2017 10:00:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2105) Add JUnit Rule support in client populators In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2105: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-persistence/pull/77 > Add JUnit Rule support in client populators > ------------------------------------------- > > Key: ARQ-2105 > URL: https://issues.jboss.org/browse/ARQ-2105 > Project: Arquillian > Issue Type: Sub-task > Reporter: Alex Soto > Assignee: Alex Soto > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 18 10:01:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 18 Apr 2017 10:01:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2105) Add JUnit Rule support in client populators In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2105: -------------------------------- Component/s: Extension - Persistence > Add JUnit Rule support in client populators > ------------------------------------------- > > Key: ARQ-2105 > URL: https://issues.jboss.org/browse/ARQ-2105 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Alex Soto > Assignee: Alex Soto > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 18 10:02:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 18 Apr 2017 10:02:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2105) Add JUnit Rule support in client populators In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2105: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Upstream https://github.com/arquillian/arquillian-extension-persistence/commit/624740788d8d7ffac5fa9b08af6807b01931ce49 > Add JUnit Rule support in client populators > ------------------------------------------- > > Key: ARQ-2105 > URL: https://issues.jboss.org/browse/ARQ-2105 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Persistence > Reporter: Alex Soto > Assignee: Alex Soto > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 18 12:06:00 2017 From: issues at jboss.org (Josef Hasenberger (JIRA)) Date: Tue, 18 Apr 2017 12:06:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1282) TestNG @DataProvider is fully invoked for each record In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13394649#comment-13394649 ] Josef Hasenberger commented on ARQ-1282: ---------------------------------------- Would be nice to have this fixed. Running into this issue as well. > TestNG @DataProvider is fully invoked for each record > ----------------------------------------------------- > > Key: ARQ-1282 > URL: https://issues.jboss.org/browse/ARQ-1282 > Project: Arquillian > Issue Type: Bug > Components: JBoss AS Containers > Affects Versions: 1.0.3.Final > Reporter: Karel Cemus > Assignee: Bartosz Majsak > Attachments: ArquillianDataProvider.java, FlightServiceTest.java > > > h2. Expected behavior > TestNG defines @DataProvider annotation to allow single method to perform multiple test cases. Provider method annotated with @DataProvider returns an array of arrays, each containing one test case. These parameters are given to the target method as input parameters. By the definition, the total count of performed test by single method is equal to number of test cases in related data provider. > h2. Actual behavior > Using TestNG under Arquillian framework makes this functionality buggy. Although the client (maven, IDE, etc.) thinks, that the total number of invoked test is correct, it is not. When we take a look into server's log, we can see that for each single test case it invoked full set of all test cases. It means, that in the end the amount of performed tests is equal to expected count squared. Such behaviour is not only slow but also in some cases it doesn't work and it makes tests to fail. > h2. Example > {code:java} > @DataProvider > public Object[][] sumProvider() { > return new Object[][]{ > new Object[]{ 0, 0, 0 }, > new Object[]{ 1, 1, 2 }, > new Object[]{ 1, 5, 6 }, > new Object[]{ 5, 1, 6 } > }; > } > {code} > h3. Expected output in server log > {quote} > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > {quote} > h3. Actual output > {quote} > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Apr 18 16:07:00 2017 From: issues at jboss.org (Josef Hasenberger (JIRA)) Date: Tue, 18 Apr 2017 16:07:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2086) Test failures not reported with recent versions of TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13394751#comment-13394751 ] Josef Hasenberger commented on ARQ-2086: ---------------------------------------- Please fix, encountered this as well. > Test failures not reported with recent versions of TestNG > --------------------------------------------------------- > > Key: ARQ-2086 > URL: https://issues.jboss.org/browse/ARQ-2086 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.12.Final > Reporter: Gunnar Morling > Assignee: Bartosz Majsak > Priority: Blocker > > When using recent TestNG versions (> 6.8.21) with Arquillian, failing tests are accidentally reported as passing. > A reproducer can be found at https://github.com/gunnarmorling/arquillian-testng-bug. > There is a single test which is expected to fail, but it actually is reported as successful with TestNG 6.11. It is reported as failed as expected with 6.8.21. Run {{mvn clean install}} for reproducing. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 02:39:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 02:39:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1836) Support HtmlUnitDriver client options In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1836: -------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-extension-drone/pull/85 > Support HtmlUnitDriver client options > ------------------------------------- > > Key: ARQ-1836 > URL: https://issues.jboss.org/browse/ARQ-1836 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Dipak Pawar > Fix For: drone_2.1.0.Final > > > There are options that could be set for HtmlUnitDriver but are not available in Drone configuration. > Drone would need to proxy HtmlUnitDriver and override protected {{modifyWebClient}} method because this is not exposed in Selenium. > https://code.google.com/p/selenium/source/browse/java/client/src/org/openqa/selenium/htmlunit/HtmlUnitDriver.java?r=1615e198f0e0b9d7a0cc60bedf475fe23b9c7e1e#266 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 02:40:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 02:40:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1836) Support HtmlUnitDriver client options In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-1836. ------------------------------- Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/5fd928e4d830fbcc4e877b7af654f121498bb6b6 > Support HtmlUnitDriver client options > ------------------------------------- > > Key: ARQ-1836 > URL: https://issues.jboss.org/browse/ARQ-1836 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Dipak Pawar > Fix For: drone_2.1.0.Final > > > There are options that could be set for HtmlUnitDriver but are not available in Drone configuration. > Drone would need to proxy HtmlUnitDriver and override protected {{modifyWebClient}} method because this is not exposed in Selenium. > https://code.google.com/p/selenium/source/browse/java/client/src/org/openqa/selenium/htmlunit/HtmlUnitDriver.java?r=1615e198f0e0b9d7a0cc60bedf475fe23b9c7e1e#266 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 02:41:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 02:41:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1836) Support HtmlUnitDriver client options In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reopened ARQ-1836: --------------------------------- > Support HtmlUnitDriver client options > ------------------------------------- > > Key: ARQ-1836 > URL: https://issues.jboss.org/browse/ARQ-1836 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Dipak Pawar > Fix For: drone_2.1.0.Final > > > There are options that could be set for HtmlUnitDriver but are not available in Drone configuration. > Drone would need to proxy HtmlUnitDriver and override protected {{modifyWebClient}} method because this is not exposed in Selenium. > https://code.google.com/p/selenium/source/browse/java/client/src/org/openqa/selenium/htmlunit/HtmlUnitDriver.java?r=1615e198f0e0b9d7a0cc60bedf475fe23b9c7e1e#266 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 02:42:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 02:42:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1836) Support HtmlUnitDriver client options In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1836: -------------------------------- Fix Version/s: drone_2.1.0 (was: drone_2.1.0.Final) > Support HtmlUnitDriver client options > ------------------------------------- > > Key: ARQ-1836 > URL: https://issues.jboss.org/browse/ARQ-1836 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Dipak Pawar > Fix For: drone_2.1.0 > > > There are options that could be set for HtmlUnitDriver but are not available in Drone configuration. > Drone would need to proxy HtmlUnitDriver and override protected {{modifyWebClient}} method because this is not exposed in Selenium. > https://code.google.com/p/selenium/source/browse/java/client/src/org/openqa/selenium/htmlunit/HtmlUnitDriver.java?r=1615e198f0e0b9d7a0cc60bedf475fe23b9c7e1e#266 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 02:42:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 02:42:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1836) Support HtmlUnitDriver client options In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-1836. ------------------------------- Resolution: Done > Support HtmlUnitDriver client options > ------------------------------------- > > Key: ARQ-1836 > URL: https://issues.jboss.org/browse/ARQ-1836 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Dipak Pawar > Fix For: drone_2.1.0 > > > There are options that could be set for HtmlUnitDriver but are not available in Drone configuration. > Drone would need to proxy HtmlUnitDriver and override protected {{modifyWebClient}} method because this is not exposed in Selenium. > https://code.google.com/p/selenium/source/browse/java/client/src/org/openqa/selenium/htmlunit/HtmlUnitDriver.java?r=1615e198f0e0b9d7a0cc60bedf475fe23b9c7e1e#266 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 02:43:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 02:43:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1699) PhantomJS resolution by Spacelift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-1699. ------------------------------- Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/5f4f64146dfbb42b641464dfb89aaa811b008a31 > PhantomJS resolution by Spacelift > --------------------------------- > > Key: ARQ-1699 > URL: https://issues.jboss.org/browse/ARQ-1699 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Reporter: Karel Piwko > Assignee: Matous Jobanek > Fix For: drone_2.1.0.Beta1 > > > PhantomJS resolution should be done via Spacelift. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 02:47:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 02:47:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1891) Update selenium version in branch 1.3.x to 2.43.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-1891. ------------------------------- Assignee: Matous Jobanek Resolution: Won't Fix The 1.3.x branch is not maintained any more. > Update selenium version in branch 1.3.x to 2.43.1 > ------------------------------------------------- > > Key: ARQ-1891 > URL: https://issues.jboss.org/browse/ARQ-1891 > Project: Arquillian > Issue Type: Sub-task > Components: Extension - Drone > Reporter: Sona Jamborova > Assignee: Matous Jobanek > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 02:49:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 02:49:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1890) Support implementation of Microsoft WebDriver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reopened ARQ-1890: --------------------------------- > Support implementation of Microsoft WebDriver > --------------------------------------------- > > Key: ARQ-1890 > URL: https://issues.jboss.org/browse/ARQ-1890 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_1.3.1.Final > Reporter: Sona Jamborova > Assignee: Tomas David > Fix For: drone_2.1.0.Alpha2 > > > Selenium team adds support of Microsoft WebDriver in 2.43.0. Drone should use this vendor as well as selenium. > My Idea is: > 1) An user is responsible to install MS WebDriver > 2) Arquillian.xml presents new property (for example: IEDriverEngine). The values are LEGACY, VENDOR, AUTODETECT. The default value is LEGACY or AUTODETECT. I prefer AUTODETECT. > Unfortunately, this feature is not fully supported by Selenium for Java platforms (see comments). > Solution for branch drone 1.3.x: > * for enabling property in arquillian.xml: > ** add new field (attribute) in class WebDriverConfiguration > ** add setter and getter for this field > ** Note: properties in arquillian.xml are automaticaly mapped to fields in this class > * map a value of ieDriverEngine property to system property "webdriver.ie.driver.engine" > ** in class InternetExplorerDriverFactory -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 02:49:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 02:49:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1890) Support implementation of Microsoft WebDriver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1890: -------------------------------- Fix Version/s: drone_2.1.0.Alpha2 (was: drone_2.1.0.Final) > Support implementation of Microsoft WebDriver > --------------------------------------------- > > Key: ARQ-1890 > URL: https://issues.jboss.org/browse/ARQ-1890 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_1.3.1.Final > Reporter: Sona Jamborova > Assignee: Tomas David > Fix For: drone_2.1.0.Alpha2 > > > Selenium team adds support of Microsoft WebDriver in 2.43.0. Drone should use this vendor as well as selenium. > My Idea is: > 1) An user is responsible to install MS WebDriver > 2) Arquillian.xml presents new property (for example: IEDriverEngine). The values are LEGACY, VENDOR, AUTODETECT. The default value is LEGACY or AUTODETECT. I prefer AUTODETECT. > Unfortunately, this feature is not fully supported by Selenium for Java platforms (see comments). > Solution for branch drone 1.3.x: > * for enabling property in arquillian.xml: > ** add new field (attribute) in class WebDriverConfiguration > ** add setter and getter for this field > ** Note: properties in arquillian.xml are automaticaly mapped to fields in this class > * map a value of ieDriverEngine property to system property "webdriver.ie.driver.engine" > ** in class InternetExplorerDriverFactory -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 02:50:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 02:50:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1890) Support implementation of Microsoft WebDriver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-1890. ------------------------------- Resolution: Done > Support implementation of Microsoft WebDriver > --------------------------------------------- > > Key: ARQ-1890 > URL: https://issues.jboss.org/browse/ARQ-1890 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_1.3.1.Final > Reporter: Sona Jamborova > Assignee: Tomas David > Fix For: drone_2.1.0.Alpha2 > > > Selenium team adds support of Microsoft WebDriver in 2.43.0. Drone should use this vendor as well as selenium. > My Idea is: > 1) An user is responsible to install MS WebDriver > 2) Arquillian.xml presents new property (for example: IEDriverEngine). The values are LEGACY, VENDOR, AUTODETECT. The default value is LEGACY or AUTODETECT. I prefer AUTODETECT. > Unfortunately, this feature is not fully supported by Selenium for Java platforms (see comments). > Solution for branch drone 1.3.x: > * for enabling property in arquillian.xml: > ** add new field (attribute) in class WebDriverConfiguration > ** add setter and getter for this field > ** Note: properties in arquillian.xml are automaticaly mapped to fields in this class > * map a value of ieDriverEngine property to system property "webdriver.ie.driver.engine" > ** in class InternetExplorerDriverFactory -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 02:50:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 02:50:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-437) Introduce annotation to control lifecycle of selenium session In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-437: ------------------------------- Fix Version/s: (was: drone_2.1.0.Final) > Introduce annotation to control lifecycle of selenium session > ------------------------------------------------------------- > > Key: ARQ-437 > URL: https://issues.jboss.org/browse/ARQ-437 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Reporter: Luk?? Fry? > > Following options are being considered: > BEFORE_SUITE > BEFORE_CLASS > BEFORE_METHOD -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 02:51:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 02:51:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1693) Independent and flexible lifecycle for Drones In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1693: -------------------------------- Fix Version/s: (was: drone_2.1.0.Final) > Independent and flexible lifecycle for Drones > --------------------------------------------- > > Key: ARQ-1693 > URL: https://issues.jboss.org/browse/ARQ-1693 > Project: Arquillian > Issue Type: Task > Components: Extension - Drone > Reporter: Karel Piwko > > It should be possible to define lifecycle that is independent of existing Arquillian events. > Suite being one of the most prominent ones. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 02:51:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 02:51:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1179) Mark a test so it will only run against certain browsers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1179: -------------------------------- Fix Version/s: (was: drone_2.1.0.Final) > Mark a test so it will only run against certain browsers > -------------------------------------------------------- > > Key: ARQ-1179 > URL: https://issues.jboss.org/browse/ARQ-1179 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Reporter: Brian Leathem > > It would be useful to be able to annotate a particular test so it will only run when driven by a particular set of browsers. > Some sample use cases: > # Some tests cannot target the incomplete js impl found in html unit. I would mark such tests not to run when htmlunit is the configured browser (in CI for instance) > # Some tests may target non-standard behaviour in certain browsers (older IE versions for instance) and may not make sense to run in all browsers. I would mark such tests not to run only when IE is the configured browser. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 02:51:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 02:51:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1077) Persistence Plugin does not work with Drone/Graphene In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1077: -------------------------------- Fix Version/s: (was: drone_2.1.0.Final) > Persistence Plugin does not work with Drone/Graphene > ---------------------------------------------------- > > Key: ARQ-1077 > URL: https://issues.jboss.org/browse/ARQ-1077 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone, Extension - Persistence > Environment: JBoss AS 7 Container > Reporter: Bryan Saunders > Assignee: Bartosz Majsak > Labels: drone, persistence > > Persistence Extension does not execute when being used with the Drone/Graphene extensions. When you run the tests in Client Mode the @UsingDataSet annotations do not trigger and populate the database. @ApplyScriptBefore also does not work. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 02:51:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 02:51:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1545) Drone: allow to setup WebDriver's Capabilities programatically In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1545: -------------------------------- Fix Version/s: (was: drone_2.1.0.Final) > Drone: allow to setup WebDriver's Capabilities programatically > -------------------------------------------------------------- > > Key: ARQ-1545 > URL: https://issues.jboss.org/browse/ARQ-1545 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_1.2.0.Final > Reporter: Luk?? Fry? > > The programatic configuration comes when some capability is unsupported and it has complex type, such as collection or array. > ---- > Even though I can access WebDriverConfiguration programatically and retrieve #getCapabilities(), I will get clone of capabilities stored in configuration. > I suggest we allow to access capabilityMap in order to allow programatically configure. > ---- > Please document a sample of usage here once done, i.e. what even is expected to listen. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 04:17:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 04:17:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2022) Support starting Browser window in Fullscreen In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2022: -------------------------------- Fix Version/s: drone_2.1.0 > Support starting Browser window in Fullscreen > --------------------------------------------- > > Key: ARQ-2022 > URL: https://issues.jboss.org/browse/ARQ-2022 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Reporter: Aslak Knutsen > Fix For: drone_2.1.0 > > > Ref https://github.com/richfaces/richfaces/blob/master/build/build-resources/src/main/java/org/richfaces/arquillian/browser/WindowResizer.java -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 04:18:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 04:18:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2022) Support starting Browser window in Fullscreen In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reassigned ARQ-2022: ----------------------------------- Assignee: Matous Jobanek > Support starting Browser window in Fullscreen > --------------------------------------------- > > Key: ARQ-2022 > URL: https://issues.jboss.org/browse/ARQ-2022 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Reporter: Aslak Knutsen > Assignee: Matous Jobanek > Fix For: drone_2.1.0 > > > Ref https://github.com/richfaces/richfaces/blob/master/build/build-resources/src/main/java/org/richfaces/arquillian/browser/WindowResizer.java -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 04:19:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 04:19:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2022) Support starting Browser window in Fullscreen In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2022. ------------------------------- Resolution: Done Implemented by https://github.com/arquillian/arquillian-extension-drone/commit/eb812f783e014b566d85ab41831b1d5fca206d16 > Support starting Browser window in Fullscreen > --------------------------------------------- > > Key: ARQ-2022 > URL: https://issues.jboss.org/browse/ARQ-2022 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Reporter: Aslak Knutsen > Assignee: Matous Jobanek > Fix For: drone_2.1.0 > > > Ref https://github.com/richfaces/richfaces/blob/master/build/build-resources/src/main/java/org/richfaces/arquillian/browser/WindowResizer.java -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 04:33:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 04:33:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2060) Support for Edge browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2060: -------------------------------- Affects Version/s: drone_2.1.0.Alpha1 (was: drone_2.1.0.Final) > Support for Edge browser > ------------------------ > > Key: ARQ-2060 > URL: https://issues.jboss.org/browse/ARQ-2060 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.1.0.Alpha1 > Environment: Windows 10 > Reporter: Tomas David > Assignee: Tomas David > Fix For: drone_2.1.0.Alpha2 > > > Edge browser is not currently supported. Available options are: opera, safari, chrome, phantomjs, firefox, htmlUnit, internetExplorer. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 04:33:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 04:33:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2060) Support for Edge browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2060. ------------------------------- > Support for Edge browser > ------------------------ > > Key: ARQ-2060 > URL: https://issues.jboss.org/browse/ARQ-2060 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.1.0.Alpha1 > Environment: Windows 10 > Reporter: Tomas David > Assignee: Tomas David > Fix For: drone_2.1.0.Alpha2 > > > Edge browser is not currently supported. Available options are: opera, safari, chrome, phantomjs, firefox, htmlUnit, internetExplorer. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 04:35:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 04:35:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1906) IE driver 2.43+ fails to start due to missing capabilities type mapping In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1906: -------------------------------- Fix Version/s: (was: drone_1.3.2.Final) > IE driver 2.43+ fails to start due to missing capabilities type mapping > ----------------------------------------------------------------------- > > Key: ARQ-1906 > URL: https://issues.jboss.org/browse/ARQ-1906 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_1.3.1.Final > Reporter: Jiri Locker > Priority: Critical > > IE driver became sensitive to capabilities data types in version 2.43.0. If a capability has an unexpected type (e.g. Boolean capability with String value "true"), the driver will fail on the first command, which is obviously an absolute show stopper. > [Issue 8160|https://code.google.com/p/selenium/issues/detail?id=8160] has been filed in Selenium project. A fix has been made on master which prevents IE driver from crashing but wrongly typed capabilities will fall back to default values. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 04:37:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 04:37:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1906) IE driver 2.43+ fails to start due to missing capabilities type mapping In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-1906. ------------------------------- Assignee: Matous Jobanek Resolution: Won't Fix Closing as won't fix in 1.3.x stream - use 2.x.y instead > IE driver 2.43+ fails to start due to missing capabilities type mapping > ----------------------------------------------------------------------- > > Key: ARQ-1906 > URL: https://issues.jboss.org/browse/ARQ-1906 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_1.3.1.Final > Reporter: Jiri Locker > Assignee: Matous Jobanek > Priority: Critical > > IE driver became sensitive to capabilities data types in version 2.43.0. If a capability has an unexpected type (e.g. Boolean capability with String value "true"), the driver will fail on the first command, which is obviously an absolute show stopper. > [Issue 8160|https://code.google.com/p/selenium/issues/detail?id=8160] has been filed in Selenium project. A fix has been made on master which prevents IE driver from crashing but wrongly typed capabilities will fall back to default values. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 04:40:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 04:40:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1882) NPE in ConfigurationMapper In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reopened ARQ-1882: --------------------------------- Reopening to remove 1.3.2.Final version from the set of fixed versions - the version won't be released as 1.3.x branch is not maintained any more > NPE in ConfigurationMapper > -------------------------- > > Key: ARQ-1882 > URL: https://issues.jboss.org/browse/ARQ-1882 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2, drone_1.3.1.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_2.0.0.Alpha3 > > > If there is no name property in Drone configuration, configuration mapper tries to convert null value from dot-syntax to camel case syntax -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 04:40:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 04:40:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1882) NPE in ConfigurationMapper In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1882: -------------------------------- Fix Version/s: (was: drone_1.3.2.Final) > NPE in ConfigurationMapper > -------------------------- > > Key: ARQ-1882 > URL: https://issues.jboss.org/browse/ARQ-1882 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2, drone_1.3.1.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_2.0.0.Alpha3 > > > If there is no name property in Drone configuration, configuration mapper tries to convert null value from dot-syntax to camel case syntax -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 04:40:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 04:40:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1882) NPE in ConfigurationMapper In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-1882. ------------------------------- Resolution: Done > NPE in ConfigurationMapper > -------------------------- > > Key: ARQ-1882 > URL: https://issues.jboss.org/browse/ARQ-1882 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2, drone_1.3.1.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_2.0.0.Alpha3 > > > If there is no name property in Drone configuration, configuration mapper tries to convert null value from dot-syntax to camel case syntax -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 06:24:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 21 Apr 2017 06:24:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-401) Docs - JSFUnit section outdated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-401. ------------------------------ Resolution: Done > Docs - JSFUnit section outdated > ------------------------------- > > Key: ARQ-401 > URL: https://issues.jboss.org/browse/ARQ-401 > Project: Arquillian > Issue Type: Bug > Components: Documentation > Affects Versions: 1.0.0.Alpha5 > Reporter: Jozef Hartinger > > The following section > http://docs.jboss.org/arquillian/reference/1.0.0.Alpha5/en-US/html/extension.reference.html#extension.jsfunit > is outdated and should be rewritten to reflect this > http://community.jboss.org/wiki/InjectionCDIforJSFSessionJSFClientSessionandJSFServerSession -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 06:26:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 21 Apr 2017 06:26:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1545) Drone: allow to setup WebDriver's Capabilities programatically In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1545: -------------------------------- Fix Version/s: drone_2.1.0.Final > Drone: allow to setup WebDriver's Capabilities programatically > -------------------------------------------------------------- > > Key: ARQ-1545 > URL: https://issues.jboss.org/browse/ARQ-1545 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_1.2.0.Final > Reporter: Luk?? Fry? > Fix For: drone_2.1.0.Final > > > The programatic configuration comes when some capability is unsupported and it has complex type, such as collection or array. > ---- > Even though I can access WebDriverConfiguration programatically and retrieve #getCapabilities(), I will get clone of capabilities stored in configuration. > I suggest we allow to access capabilityMap in order to allow programatically configure. > ---- > Please document a sample of usage here once done, i.e. what even is expected to listen. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 06:26:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 21 Apr 2017 06:26:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1179) Mark a test so it will only run against certain browsers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1179: -------------------------------- Fix Version/s: (was: drone_2.1.0.Final) > Mark a test so it will only run against certain browsers > -------------------------------------------------------- > > Key: ARQ-1179 > URL: https://issues.jboss.org/browse/ARQ-1179 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Reporter: Brian Leathem > > It would be useful to be able to annotate a particular test so it will only run when driven by a particular set of browsers. > Some sample use cases: > # Some tests cannot target the incomplete js impl found in html unit. I would mark such tests not to run when htmlunit is the configured browser (in CI for instance) > # Some tests may target non-standard behaviour in certain browsers (older IE versions for instance) and may not make sense to run in all browsers. I would mark such tests not to run only when IE is the configured browser. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 06:26:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 21 Apr 2017 06:26:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1179) Mark a test so it will only run against certain browsers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1179: -------------------------------- Fix Version/s: drone_2.1.0.Final > Mark a test so it will only run against certain browsers > -------------------------------------------------------- > > Key: ARQ-1179 > URL: https://issues.jboss.org/browse/ARQ-1179 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Reporter: Brian Leathem > > It would be useful to be able to annotate a particular test so it will only run when driven by a particular set of browsers. > Some sample use cases: > # Some tests cannot target the incomplete js impl found in html unit. I would mark such tests not to run when htmlunit is the configured browser (in CI for instance) > # Some tests may target non-standard behaviour in certain browsers (older IE versions for instance) and may not make sense to run in all browsers. I would mark such tests not to run only when IE is the configured browser. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 06:27:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 21 Apr 2017 06:27:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1545) Drone: allow to setup WebDriver's Capabilities programatically In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1545: -------------------------------- Fix Version/s: (was: drone_2.1.0.Final) > Drone: allow to setup WebDriver's Capabilities programatically > -------------------------------------------------------------- > > Key: ARQ-1545 > URL: https://issues.jboss.org/browse/ARQ-1545 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_1.2.0.Final > Reporter: Luk?? Fry? > > The programatic configuration comes when some capability is unsupported and it has complex type, such as collection or array. > ---- > Even though I can access WebDriverConfiguration programatically and retrieve #getCapabilities(), I will get clone of capabilities stored in configuration. > I suggest we allow to access capabilityMap in order to allow programatically configure. > ---- > Please document a sample of usage here once done, i.e. what even is expected to listen. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 06:30:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 06:30:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2088) When test is skipped because of an assumption, Arquillian's test result is passed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396443#comment-13396443 ] Matous Jobanek commented on ARQ-2088: ------------------------------------- It seems that the TestResult is Passed in all cases - even when the test fails > When test is skipped because of an assumption, Arquillian's test result is passed > --------------------------------------------------------------------------------- > > Key: ARQ-2088 > URL: https://issues.jboss.org/browse/ARQ-2088 > Project: Arquillian > Issue Type: Enhancement > Components: core > Affects Versions: 1.1.13.Final > Reporter: Matous Jobanek > > When you run Arquillian test with an assumption: {{Assume.assumeFalse(true);}} then the test is skipped. The same also say both IDE and maven surefire, but Arquillian's {{TestResult}} retrieved in {{After}} phase contains status Passed. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 06:36:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 21 Apr 2017 06:36:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2082) "Could not inject members" when running inside glassfish-embedded-3.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396450#comment-13396450 ] Bartosz Majsak commented on ARQ-2082: ------------------------------------- Could you share reproducer on GitHub? That would tremendously help us analyzing the problem. > "Could not inject members" when running inside glassfish-embedded-3.1 > --------------------------------------------------------------------- > > Key: ARQ-2082 > URL: https://issues.jboss.org/browse/ARQ-2082 > Project: Arquillian > Issue Type: Feature Request > Components: GlassFish Containers > Affects Versions: 1.1.12.Final > Environment: payara.micro= 4.1.1.171.0.1 > arquillian.version = 1.1.12.Final > glassfish-embedded-3.1= 1.0.0.Final > Reporter: Abel Salgado Romero > > I have a project with some simple Rest services a some beans (with @ApplicationScoped) and a test that runs correctly when {@Deployment(testable = false)}. > However, if I set {testable = true} and try to retrive some component in the test, for instance: > {quote} > @Inject > private UserServiceImpl userService; > {quote} > Test fails with the message > {quote} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > ... > Caused by: org.jboss.weld.exceptions.IllegalArgumentException: WELD-001408: Unsatisfied dependencies for type HelloWorldResource with qualifiers @Default > at injection point [BackedAnnotatedField] @Inject private com..payara.HelloTest.helloWorldResource > at com..payara.HelloTest.helloWorldResource(HelloTest.java:0) > {quote} > Notes: > ? Same code runs (with appropriate changes) on Wildfly-swarm > ? Just in case it could be related, I have a multipart upload service, so I need to initialize the components like this: > {quote} > @ApplicationPath("/app/v1/") > public class DemoPayaraApplication extends ResourceConfig { > public DemoPayaraApplication() { > packages("com.everis.payara"); > register(MultiPartFeature.class); > } > } > {quote} > And add additional dpendencies > {quote} > > org.glassfish.jersey.media > jersey-media-multipart > 2.25.1 > provided > > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 06:39:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 21 Apr 2017 06:39:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1611) Arquillian doesn't handle Glassfish REST API redirect In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396454#comment-13396454 ] Bartosz Majsak commented on ARQ-1611: ------------------------------------- Hi [~rm_tanin] Could share reproducer on GitHub which we can use to analyze the problem? > Arquillian doesn't handle Glassfish REST API redirect > ----------------------------------------------------- > > Key: ARQ-1611 > URL: https://issues.jboss.org/browse/ARQ-1611 > Project: Arquillian > Issue Type: Bug > Components: GlassFish Containers > Affects Versions: glassfish_1.0.0.CR4 > Environment: Windows client and server > Windows client, Linux server > Linux client, Windows server > Glassfish 3.1.2.2, 4.0 and 4.0.1-b03-ml > Reporter: Andr? Pinheiro > > When deploying to a remote glassfish DAS instance, the REST API sends back a 302 redirect. Arquillian GlassFishClientUtil fails to handle that redirect - as it wasn't expecting that kind of response - and the following exception is thrown: > {quote} > com.sun.jersey.api.container.ContainerException: [status: REDIRECTION reason: Found] > at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientUtil.getResponseMap(GlassFishClientUtil.java:192) > at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientUtil.GETRequest(GlassFishClientUtil.java:109) > at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientUtil.getChildResources(GlassFishClientUtil.java:95) > at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientService.getServersList(GlassFishClientService.java:319) > at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientService.startUp(GlassFishClientService.java:102) > at org.jboss.arquillian.container.glassfish.CommonGlassFishManager.start(CommonGlassFishManager.java:72) > at org.jboss.arquillian.container.glassfish.remote_3_1.GlassFishRestDeployableContainer.start(GlassFishRestDeployableContainer.java:59) > at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:86) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:68) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:97) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68) > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 06:39:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 06:39:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2075) In debug mode print information about loaded extensions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reassigned ARQ-2075: ----------------------------------- Fix Version/s: 1.1.13.Final Git Pull Request: https://github.com/arquillian/arquillian-core/pull/124 Assignee: Alex Soto > In debug mode print information about loaded extensions > ------------------------------------------------------- > > Key: ARQ-2075 > URL: https://issues.jboss.org/browse/ARQ-2075 > Project: Arquillian > Issue Type: Enhancement > Components: core > Affects Versions: 1.1.12.Final > Reporter: Matous Jobanek > Assignee: Alex Soto > Fix For: 1.1.13.Final > > > When the test is run with a property arquillian.debug then there should be printed a list of all loaded extensions on the stdout. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 06:39:01 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 21 Apr 2017 06:39:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1611) Arquillian doesn't handle Glassfish REST API redirect In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396454#comment-13396454 ] Bartosz Majsak edited comment on ARQ-1611 at 4/21/17 6:38 AM: -------------------------------------------------------------- Hi [~rm_tanin] Could you share reproducer on GitHub which we can use to analyze the problem? was (Author: bmajsak): Hi [~rm_tanin] Could share reproducer on GitHub which we can use to analyze the problem? > Arquillian doesn't handle Glassfish REST API redirect > ----------------------------------------------------- > > Key: ARQ-1611 > URL: https://issues.jboss.org/browse/ARQ-1611 > Project: Arquillian > Issue Type: Bug > Components: GlassFish Containers > Affects Versions: glassfish_1.0.0.CR4 > Environment: Windows client and server > Windows client, Linux server > Linux client, Windows server > Glassfish 3.1.2.2, 4.0 and 4.0.1-b03-ml > Reporter: Andr? Pinheiro > > When deploying to a remote glassfish DAS instance, the REST API sends back a 302 redirect. Arquillian GlassFishClientUtil fails to handle that redirect - as it wasn't expecting that kind of response - and the following exception is thrown: > {quote} > com.sun.jersey.api.container.ContainerException: [status: REDIRECTION reason: Found] > at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientUtil.getResponseMap(GlassFishClientUtil.java:192) > at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientUtil.GETRequest(GlassFishClientUtil.java:109) > at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientUtil.getChildResources(GlassFishClientUtil.java:95) > at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientService.getServersList(GlassFishClientService.java:319) > at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientService.startUp(GlassFishClientService.java:102) > at org.jboss.arquillian.container.glassfish.CommonGlassFishManager.start(CommonGlassFishManager.java:72) > at org.jboss.arquillian.container.glassfish.remote_3_1.GlassFishRestDeployableContainer.start(GlassFishRestDeployableContainer.java:59) > at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:86) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:68) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:97) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68) > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 06:40:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 21 Apr 2017 06:40:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2075) In debug mode print information about loaded extensions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2075. ------------------------------- Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-core/commit/6445722a053af878f9e5568656d7d6c610459c80 > In debug mode print information about loaded extensions > ------------------------------------------------------- > > Key: ARQ-2075 > URL: https://issues.jboss.org/browse/ARQ-2075 > Project: Arquillian > Issue Type: Enhancement > Components: core > Affects Versions: 1.1.12.Final > Reporter: Matous Jobanek > Assignee: Alex Soto > Fix For: 1.1.13.Final > > > When the test is run with a property arquillian.debug then there should be printed a list of all loaded extensions on the stdout. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 06:40:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 21 Apr 2017 06:40:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2059) Arquillian Governor Jira get Value from properties In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396457#comment-13396457 ] Bartosz Majsak commented on ARQ-2059: ------------------------------------- I believe it's not available in the current version. If you are still interested in this feature let us know. > Arquillian Governor Jira get Value from properties > --------------------------------------------------- > > Key: ARQ-2059 > URL: https://issues.jboss.org/browse/ARQ-2059 > Project: Arquillian > Issue Type: Feature Request > Components: Configuration > Environment: In Arquillian Governor Jira, how set I issues from properties fiel in value field?? > Reporter: Rafael Garcia > Priority: Minor > > Hi, > In Arquillian Governor Jira, how set I issues from properties fiel in value field?? > For example: > In properties file > {noformat} > key.issue=PBT-2 > {noformat} > In test.java > @Jira(value = "*{color:red}${key.issue}{color}*") > public void exampleTest() {...} > Thanks in advance -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 06:47:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 21 Apr 2017 06:47:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2066) Support for JUnit 5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2066: -------------------------------- Summary: Support for JUnit 5 (was: Supprt for JUnit 5) > Support for JUnit 5 > ------------------- > > Key: ARQ-2066 > URL: https://issues.jboss.org/browse/ARQ-2066 > Project: Arquillian > Issue Type: Feature Request > Reporter: Tobias Stadler > > The final relase of JUnit 5 is scheduled for Q1 2017. It would be nice if Arquillian would support it then. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 06:51:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 21 Apr 2017 06:51:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1213) Add support for GlassFish 3.0 container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-1213. ------------------------------- Resolution: Out of Date > Add support for GlassFish 3.0 container > --------------------------------------- > > Key: ARQ-1213 > URL: https://issues.jboss.org/browse/ARQ-1213 > Project: Arquillian > Issue Type: Feature Request > Components: GlassFish Containers > Reporter: Vineet Reynolds > Priority: Minor > > The RESTful admin API provided by GlassFish 3.0 does not provide all the REST resources that are currently used by the GlassFish 3.1 adapter. Hence, the 3.1 adapter is not backward compatible with a GlassFish 3.0 instance. > Additionally, the message formats returned by the REST resources of GF 3.0 are different from the ones returned by GF 3.1, hence requiring different parsing semantics. > We must therefore implement a separate adapter to support GlassFish 3.0, that either uses the RESTful Admin APIs available in 3.0, or a supported API like JSR-88. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 06:52:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 21 Apr 2017 06:52:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1383) Support deployment of container wide resource.xml in GlassFish Managed and Remote In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak reassigned ARQ-1383: ----------------------------------- Assignee: (was: Bartosz Majsak) > Support deployment of container wide resource.xml in GlassFish Managed and Remote > ---------------------------------------------------------------------------------- > > Key: ARQ-1383 > URL: https://issues.jboss.org/browse/ARQ-1383 > Project: Arquillian > Issue Type: Feature Request > Components: GlassFish Containers > Affects Versions: glassfish_1.0.0.CR4 > Reporter: Aslak Knutsen > Fix For: glassfish_1.0.0.Final > > > As a User I would like to deploy Container wide resources > Given a Reference to a resource.xml file in ContainerConfiguration > When the Container starts up > Then the resource.xml should be deployed > When the Container shuts down > Then the resource.xml should be undeployed > This is similar to how GlassFish Embedded works. > Configuration: https://github.com/arquillian/arquillian-container-glassfish/blob/master/glassfish-embedded-3.1/src/main/java/org/jboss/arquillian/container/glassfish/embedded_3_1/GlassFishConfiguration.java#L156 > Container Impl: https://github.com/arquillian/arquillian-container-glassfish/blob/master/glassfish-embedded-3.1/src/main/java/org/jboss/arquillian/container/glassfish/embedded_3_1/GlassFishContainer.java#L186 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 06:53:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 21 Apr 2017 06:53:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1212) Add support for GlassFish 2.x containers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-1212. ------------------------------- Resolution: Out of Date > Add support for GlassFish 2.x containers > ---------------------------------------- > > Key: ARQ-1212 > URL: https://issues.jboss.org/browse/ARQ-1212 > Project: Arquillian > Issue Type: Feature Request > Components: GlassFish Containers > Reporter: Vineet Reynolds > Priority: Minor > > There has been atleast one request to support the GlassFish 2.x container. Since the RESTful admin API used by the current GlassFish adapter is available only since 3.0, we'll need to implement support for 2.x using a different mechanism (possibly using JSR-88 APIs). -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 21 07:03:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 21 Apr 2017 07:03:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1875) JaCoCo extension only works for simple use cases In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak closed ARQ-1875. ------------------------------- Resolution: Won't Fix Solution from JaCoCo team provided as mentioned n the PR comment > JaCoCo extension only works for simple use cases > ------------------------------------------------ > > Key: ARQ-1875 > URL: https://issues.jboss.org/browse/ARQ-1875 > Project: Arquillian > Issue Type: Bug > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha7 > Reporter: John Ament > > In JaCoCo Alpha 7, the tests pass on the build, however the extension itself only works if you have a very small use case. If you have a more robust test that uses database connections, external modules, you get ASM conflicts. > Here's an example output: > {quote} > Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label) > at java.lang.Class.getMethod(Class.java:1773) [rt.jar:1.8.0_20] > at org.apache.cxf.common.util.ReflectionInvokationHandler.invoke(ReflectionInvokationHandler.java:85) > ... 28 more > 13:34:21,040 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "api-webapp.war")]) - failure description: { > "JBAS014671: Failed services" => {"jboss.deployment.unit.\"api-webapp.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"api-webapp.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"api-webapp.war\" > Caused by: javax.xml.ws.WebServiceException: java.lang.reflect.UndeclaredThrowableException > Caused by: java.lang.reflect.UndeclaredThrowableException > Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label)"}, > "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"api-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"api-webapp.war\".beanmanager]"] > {quote} > My jboss-deployment-structure.xml looks like this: > {code} > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > Some of these are custom modules, usually just wrapping open source libraries. There's one private one I hid, but it doesn't have any ASM. It seems like hibernate's the culprit here. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Apr 24 04:25:01 2017 From: issues at jboss.org (Tomas Remes (JIRA)) Date: Mon, 24 Apr 2017 04:25:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-814) Should support injection of EJBs (as CDI Beans) in Weld Embedded In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Remes resolved ARQ-814. ----------------------------- Resolution: Won't Fix We don't plan to support EJBs in arquillian-container-weld. I think the proposed pull request is not 100% solution to this problem (as Aslak stated - injection points in EJB class wouldn't work) and IMO brings just possible confusion. This would require to introduce some embedded EJB container integration which wouldn't be so trivial I guess. I think it's still better to use some real EJB container (WFLY, GlassFish, etc) to test such testcases. > Should support injection of EJBs (as CDI Beans) in Weld Embedded > ---------------------------------------------------------------- > > Key: ARQ-814 > URL: https://issues.jboss.org/browse/ARQ-814 > Project: Arquillian > Issue Type: Bug > Components: Weld Containers > Affects Versions: weld_1.0.0.CR3 > Reporter: Anthony O. > Assignee: Marko Luk?a > Attachments: EJBTest.java > > > As seen in [this post on the Arquillian forum|https://community.jboss.org/message/723563], we cannot test that simple class as an NPE is thrown from {{org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.MockEjBServices}} which seems to be a copy of Weld code as [Aslak Knutsen|https://community.jboss.org/people/aslak] said. > {code} > @RunWith(Arquillian.class) > public class EJBTest { > @Deployment > public static JavaArchive createTestArchive() { > return ShrinkWrap > .create(JavaArchive.class, "test.jar") > .addAsManifestResource(EmptyAsset.INSTANCE, ArchivePaths.create("beans.xml")); > } > @Stateless > public static class SomeService { > public String someMethod() { > return "test"; > } > } > @Inject > SomeService someService; > @Test > public void testStatelessCall() { > Assert.assertEquals("test", someService.someMethod()); > } > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Apr 24 05:40:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 24 Apr 2017 05:40:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-502) Update Arquillian-core to 1.1.13.Final In-Reply-To: References: Message-ID: Matous Jobanek created ARQGRA-502: ------------------------------------- Summary: Update Arquillian-core to 1.1.13.Final Key: ARQGRA-502 URL: https://issues.jboss.org/browse/ARQGRA-502 Project: Arquillian Graphene Issue Type: Component Upgrade Affects Versions: 2.2.0 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: 2.2.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Apr 24 06:09:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 24 Apr 2017 06:09:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-503) Update Arquillian Drone to 2.1.0 In-Reply-To: References: Message-ID: Matous Jobanek created ARQGRA-503: ------------------------------------- Summary: Update Arquillian Drone to 2.1.0 Key: ARQGRA-503 URL: https://issues.jboss.org/browse/ARQGRA-503 Project: Arquillian Graphene Issue Type: Component Upgrade Affects Versions: 2.2.0 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: 2.2.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Apr 28 07:03:01 2017 From: issues at jboss.org (Ladislav Thon (JIRA)) Date: Fri, 28 Apr 2017 07:03:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2107) ResourceInjectionEnricher doesn't consult the @Resource(lookup = "...") value In-Reply-To: References: Message-ID: Ladislav Thon created ARQ-2107: ---------------------------------- Summary: ResourceInjectionEnricher doesn't consult the @Resource(lookup = "...") value Key: ARQ-2107 URL: https://issues.jboss.org/browse/ARQ-2107 Project: Arquillian Issue Type: Bug Components: Runtime Enricher SPI Reporter: Ladislav Thon The {{ResourceInjectionEnricher}} supports injecting the test instance fields annotated with {{javax.annotation.Resource}}. However, looking at the {{ResourceInjectionEnricher.getResourceName}} method, it only consults the annotation's {{name}} and {{mappedName}} attributes, falling back to some default afterward. The annotation's {{lookup}} attribute isn't considered at all. This might be because the {{lookup}} attribute was only added in Java EE 6 / Java SE 7, and Arquillian still supports Java 6, but that can be solved with a little bit of reflection. I don't know if this omission was intentional or not, but it could have easily gone unnoticed for a long while, because if CDI is present, the {{CDIInjectionEnricher}} will inject such field. However, CDI doesn't necessarily have to be present -- for example with WildFly Swarm. -- This message was sent by Atlassian JIRA (v7.2.3#72005)