From issues at jboss.org Thu Jan 2 11:31:32 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 2 Jan 2014 11:31:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-416) @InFrame duplicitly switches to iframe with fragment method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-416: ------------------------------ Fix Version/s: 2.0.1.Final > @InFrame duplicitly switches to iframe with fragment method > ----------------------------------------------------------- > > Key: ARQGRA-416 > URL: https://issues.jboss.org/browse/ARQGRA-416 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Jan Dosoudil > Fix For: 2.0.1.Final > > > {code} > public class Fragment { > @FindBy(id="button") > private WebElement button; > public void clickButton() { > button.click(); > } > public WebElement getButton() { > return button; > } > } > {code} > {code} > @RunWith(Arquillian.class) > @RunAsClient > public class Test { > //... > @FindBy(id="content") > @InFrame(nameOrId="frame") > private Fragment Fragment; > @Test > public void testWebElement() { > fragment.getButton().click(); //PASS > } > @Test > public void testMethod() { > fragment.clickButton(); //FAIL > } > } > {code} > Exception is: org.openqa.selenium.NoSuchFrameException: Unable to locate frame: frame -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 2 11:33:32 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 2 Jan 2014 11:33:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-416) @InFrame duplicitly switches to iframe with fragment method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933405#comment-12933405 ] Luk?? Fry? commented on ARQGRA-416: ----------------------------------- [~dosoudilj] if you have a chance, could you please look at where in the code is the frame tried to be switched? > @InFrame duplicitly switches to iframe with fragment method > ----------------------------------------------------------- > > Key: ARQGRA-416 > URL: https://issues.jboss.org/browse/ARQGRA-416 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Jan Dosoudil > Assignee: Juraj H?ska > Fix For: 2.0.1.Final > > > {code} > public class Fragment { > @FindBy(id="button") > private WebElement button; > public void clickButton() { > button.click(); > } > public WebElement getButton() { > return button; > } > } > {code} > {code} > @RunWith(Arquillian.class) > @RunAsClient > public class Test { > //... > @FindBy(id="content") > @InFrame(nameOrId="frame") > private Fragment Fragment; > @Test > public void testWebElement() { > fragment.getButton().click(); //PASS > } > @Test > public void testMethod() { > fragment.clickButton(); //FAIL > } > } > {code} > Exception is: org.openqa.selenium.NoSuchFrameException: Unable to locate frame: frame -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 2 11:33:32 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 2 Jan 2014 11:33:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-416) @InFrame duplicitly switches to iframe with fragment method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned ARQGRA-416: --------------------------------- Assignee: Juraj H?ska Juraj, could you please look at it? I assume it is related to switching frame once for a fragment and then once for an element. > @InFrame duplicitly switches to iframe with fragment method > ----------------------------------------------------------- > > Key: ARQGRA-416 > URL: https://issues.jboss.org/browse/ARQGRA-416 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Jan Dosoudil > Assignee: Juraj H?ska > Fix For: 2.0.1.Final > > > {code} > public class Fragment { > @FindBy(id="button") > private WebElement button; > public void clickButton() { > button.click(); > } > public WebElement getButton() { > return button; > } > } > {code} > {code} > @RunWith(Arquillian.class) > @RunAsClient > public class Test { > //... > @FindBy(id="content") > @InFrame(nameOrId="frame") > private Fragment Fragment; > @Test > public void testWebElement() { > fragment.getButton().click(); //PASS > } > @Test > public void testMethod() { > fragment.clickButton(); //FAIL > } > } > {code} > Exception is: org.openqa.selenium.NoSuchFrameException: Unable to locate frame: frame -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 3 04:24:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 3 Jan 2014 04:24:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1605) APK export/import does not work correcty on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1605: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-droidium/tree/ARQ-1605 PR sent https://github.com/arquillian/arquillian-droidium/tree/ARQ-1605 > APK export/import does not work correcty on Windows > --------------------------------------------------- > > Key: ARQ-1605 > URL: https://issues.jboss.org/browse/ARQ-1605 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Priority: Blocker > > On Windows platform, deployment written to temporary directory to be re-signed is empty for some reason: > {code} > org.jboss.shrinkwrap.api.exporter.ArchiveExportException: Failed to write asset to output: /res/layout/abc_action_bar_view_list_nav_layout.xml > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.read(AbstractOnDemandInputStream.java:132) > at java.io.InputStream.read(InputStream.java:170) > at java.io.InputStream.read(InputStream.java:101) > at org.arquillian.droidium.container.utils.DroidiumFileUtils.write(DroidiumFileUtils.java:175) > at org.arquillian.droidium.container.utils.DroidiumFileUtils.export(DroidiumFileUtils.java:158) > at org.arquillian.droidium.container.sign.APKSigner.resign(APKSigner.java:107) > at org.arquillian.droidium.container.deployment.AndroidDeploymentInstaller.onAndroidDeployArchive(AndroidDeploymentInstaller.java:81) > 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.arquillian.droidium.container.AndroidDeployableContainer.deploy(AndroidDeployableContainer.java:171) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127) > 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.createDeploymentContext(ContainerDeploymentContextHandler.java:78) > 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.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.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50) > 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.ContainerDeployController$1.perform(ContainerDeployController.java:95) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79) > 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:101) > 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.createClassContext(TestContextHandler.java:75) > 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.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.beforeClass(EventTestRunnerAdaptor.java:80) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > 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) > Caused by: java.lang.NullPointerException > at org.jboss.shrinkwrap.impl.base.io.IOUtil.copy(IOUtil.java:159) > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.doCopy(AbstractOnDemandInputStream.java:170) > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.read(AbstractOnDemandInputStream.java:130) > ... 110 more > {code} > This leads to NPE exception when trying to open InputStream to get archive content deployed. > {code} > @Deployment(name = "shortener-apk") > @Instrumentable(viaPort = 8081) > @TargetsContainer("android") > @OverProtocol("Android 1.0") > public static JavaArchive getAndroidDeployment() { > // FIXME There is no APK builder yet at this moment, so we need to import file > // FIXME this should point to the APK generated from latest sources, it should not be included here > return ShrinkWrap.createFromZipFile(JavaArchive.class, new File("aerogear-android-shortener.apk")); > } > {code} > {code} > HOME C:\Users\Karel\ > JAVA_HOME C:\Program Files\Java\jdk1.7.0_45\jre\ > ANDROID_HOME C:\workspace\workspace\mobile-picketlink-test\android-sdk-windows\ > ANDROID_SDK_HOME C:\workspace\workspace\mobile-picketlink-test\ > avdName random-avd > serialId null > apiLevel 17 > abi x86 > consolePort null > adbPort null > emuBoot 600 > emuShut 60 > emuOpts > keystore C:\workspace\workspace\mobile-picketlink-test\.android\debug.keystore > keypass android > storepass android > alias androiddebugkey > sigalg SHA1withRSA > keyalg RSA > sdCard null > sdSize 128M > generateSD false > logLevel W > logType disable > logFilePath target\logcat.log > logPackageWhitelist null > logPackageBlacklist null > removeTmpDir false > tmpDir C:\home\kpiwko\devel\mobile\jbossqe-mobile\integration-testse3247fe9-b479-4720-98b4-bb10f67d74b0 > force true > {code} > Test errors with Failed to write asset to output: /res/layout/abc_action_bar_view_list_nav_layout.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 3 04:24:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 3 Jan 2014 04:24:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1605) APK export/import does not work correcty on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1605: ----------------------------------- Comment: was deleted (was: PR sent https://github.com/arquillian/arquillian-droidium/tree/ARQ-1605) > APK export/import does not work correcty on Windows > --------------------------------------------------- > > Key: ARQ-1605 > URL: https://issues.jboss.org/browse/ARQ-1605 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Priority: Blocker > > On Windows platform, deployment written to temporary directory to be re-signed is empty for some reason: > {code} > org.jboss.shrinkwrap.api.exporter.ArchiveExportException: Failed to write asset to output: /res/layout/abc_action_bar_view_list_nav_layout.xml > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.read(AbstractOnDemandInputStream.java:132) > at java.io.InputStream.read(InputStream.java:170) > at java.io.InputStream.read(InputStream.java:101) > at org.arquillian.droidium.container.utils.DroidiumFileUtils.write(DroidiumFileUtils.java:175) > at org.arquillian.droidium.container.utils.DroidiumFileUtils.export(DroidiumFileUtils.java:158) > at org.arquillian.droidium.container.sign.APKSigner.resign(APKSigner.java:107) > at org.arquillian.droidium.container.deployment.AndroidDeploymentInstaller.onAndroidDeployArchive(AndroidDeploymentInstaller.java:81) > 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.arquillian.droidium.container.AndroidDeployableContainer.deploy(AndroidDeployableContainer.java:171) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127) > 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.createDeploymentContext(ContainerDeploymentContextHandler.java:78) > 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.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.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50) > 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.ContainerDeployController$1.perform(ContainerDeployController.java:95) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79) > 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:101) > 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.createClassContext(TestContextHandler.java:75) > 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.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.beforeClass(EventTestRunnerAdaptor.java:80) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > 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) > Caused by: java.lang.NullPointerException > at org.jboss.shrinkwrap.impl.base.io.IOUtil.copy(IOUtil.java:159) > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.doCopy(AbstractOnDemandInputStream.java:170) > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.read(AbstractOnDemandInputStream.java:130) > ... 110 more > {code} > This leads to NPE exception when trying to open InputStream to get archive content deployed. > {code} > @Deployment(name = "shortener-apk") > @Instrumentable(viaPort = 8081) > @TargetsContainer("android") > @OverProtocol("Android 1.0") > public static JavaArchive getAndroidDeployment() { > // FIXME There is no APK builder yet at this moment, so we need to import file > // FIXME this should point to the APK generated from latest sources, it should not be included here > return ShrinkWrap.createFromZipFile(JavaArchive.class, new File("aerogear-android-shortener.apk")); > } > {code} > {code} > HOME C:\Users\Karel\ > JAVA_HOME C:\Program Files\Java\jdk1.7.0_45\jre\ > ANDROID_HOME C:\workspace\workspace\mobile-picketlink-test\android-sdk-windows\ > ANDROID_SDK_HOME C:\workspace\workspace\mobile-picketlink-test\ > avdName random-avd > serialId null > apiLevel 17 > abi x86 > consolePort null > adbPort null > emuBoot 600 > emuShut 60 > emuOpts > keystore C:\workspace\workspace\mobile-picketlink-test\.android\debug.keystore > keypass android > storepass android > alias androiddebugkey > sigalg SHA1withRSA > keyalg RSA > sdCard null > sdSize 128M > generateSD false > logLevel W > logType disable > logFilePath target\logcat.log > logPackageWhitelist null > logPackageBlacklist null > removeTmpDir false > tmpDir C:\home\kpiwko\devel\mobile\jbossqe-mobile\integration-testse3247fe9-b479-4720-98b4-bb10f67d74b0 > force true > {code} > Test errors with Failed to write asset to output: /res/layout/abc_action_bar_view_list_nav_layout.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 3 04:24:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 3 Jan 2014 04:24:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1605) APK export/import does not work correcty on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1605: ----------------------------------- Git Pull Request: (was: https://github.com/arquillian/arquillian-droidium/tree/ARQ-1605) > APK export/import does not work correcty on Windows > --------------------------------------------------- > > Key: ARQ-1605 > URL: https://issues.jboss.org/browse/ARQ-1605 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Priority: Blocker > > On Windows platform, deployment written to temporary directory to be re-signed is empty for some reason: > {code} > org.jboss.shrinkwrap.api.exporter.ArchiveExportException: Failed to write asset to output: /res/layout/abc_action_bar_view_list_nav_layout.xml > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.read(AbstractOnDemandInputStream.java:132) > at java.io.InputStream.read(InputStream.java:170) > at java.io.InputStream.read(InputStream.java:101) > at org.arquillian.droidium.container.utils.DroidiumFileUtils.write(DroidiumFileUtils.java:175) > at org.arquillian.droidium.container.utils.DroidiumFileUtils.export(DroidiumFileUtils.java:158) > at org.arquillian.droidium.container.sign.APKSigner.resign(APKSigner.java:107) > at org.arquillian.droidium.container.deployment.AndroidDeploymentInstaller.onAndroidDeployArchive(AndroidDeploymentInstaller.java:81) > 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.arquillian.droidium.container.AndroidDeployableContainer.deploy(AndroidDeployableContainer.java:171) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127) > 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.createDeploymentContext(ContainerDeploymentContextHandler.java:78) > 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.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.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50) > 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.ContainerDeployController$1.perform(ContainerDeployController.java:95) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79) > 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:101) > 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.createClassContext(TestContextHandler.java:75) > 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.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.beforeClass(EventTestRunnerAdaptor.java:80) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > 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) > Caused by: java.lang.NullPointerException > at org.jboss.shrinkwrap.impl.base.io.IOUtil.copy(IOUtil.java:159) > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.doCopy(AbstractOnDemandInputStream.java:170) > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.read(AbstractOnDemandInputStream.java:130) > ... 110 more > {code} > This leads to NPE exception when trying to open InputStream to get archive content deployed. > {code} > @Deployment(name = "shortener-apk") > @Instrumentable(viaPort = 8081) > @TargetsContainer("android") > @OverProtocol("Android 1.0") > public static JavaArchive getAndroidDeployment() { > // FIXME There is no APK builder yet at this moment, so we need to import file > // FIXME this should point to the APK generated from latest sources, it should not be included here > return ShrinkWrap.createFromZipFile(JavaArchive.class, new File("aerogear-android-shortener.apk")); > } > {code} > {code} > HOME C:\Users\Karel\ > JAVA_HOME C:\Program Files\Java\jdk1.7.0_45\jre\ > ANDROID_HOME C:\workspace\workspace\mobile-picketlink-test\android-sdk-windows\ > ANDROID_SDK_HOME C:\workspace\workspace\mobile-picketlink-test\ > avdName random-avd > serialId null > apiLevel 17 > abi x86 > consolePort null > adbPort null > emuBoot 600 > emuShut 60 > emuOpts > keystore C:\workspace\workspace\mobile-picketlink-test\.android\debug.keystore > keypass android > storepass android > alias androiddebugkey > sigalg SHA1withRSA > keyalg RSA > sdCard null > sdSize 128M > generateSD false > logLevel W > logType disable > logFilePath target\logcat.log > logPackageWhitelist null > logPackageBlacklist null > removeTmpDir false > tmpDir C:\home\kpiwko\devel\mobile\jbossqe-mobile\integration-testse3247fe9-b479-4720-98b4-bb10f67d74b0 > force true > {code} > Test errors with Failed to write asset to output: /res/layout/abc_action_bar_view_list_nav_layout.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 3 04:26:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 3 Jan 2014 04:26:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1605) APK export/import does not work correcty on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1605: -------------------------------------- Assignee: Stefan Miklosovic > APK export/import does not work correcty on Windows > --------------------------------------------------- > > Key: ARQ-1605 > URL: https://issues.jboss.org/browse/ARQ-1605 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Priority: Blocker > > On Windows platform, deployment written to temporary directory to be re-signed is empty for some reason: > {code} > org.jboss.shrinkwrap.api.exporter.ArchiveExportException: Failed to write asset to output: /res/layout/abc_action_bar_view_list_nav_layout.xml > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.read(AbstractOnDemandInputStream.java:132) > at java.io.InputStream.read(InputStream.java:170) > at java.io.InputStream.read(InputStream.java:101) > at org.arquillian.droidium.container.utils.DroidiumFileUtils.write(DroidiumFileUtils.java:175) > at org.arquillian.droidium.container.utils.DroidiumFileUtils.export(DroidiumFileUtils.java:158) > at org.arquillian.droidium.container.sign.APKSigner.resign(APKSigner.java:107) > at org.arquillian.droidium.container.deployment.AndroidDeploymentInstaller.onAndroidDeployArchive(AndroidDeploymentInstaller.java:81) > 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.arquillian.droidium.container.AndroidDeployableContainer.deploy(AndroidDeployableContainer.java:171) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127) > 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.createDeploymentContext(ContainerDeploymentContextHandler.java:78) > 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.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.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50) > 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.ContainerDeployController$1.perform(ContainerDeployController.java:95) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79) > 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:101) > 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.createClassContext(TestContextHandler.java:75) > 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.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.beforeClass(EventTestRunnerAdaptor.java:80) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > 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) > Caused by: java.lang.NullPointerException > at org.jboss.shrinkwrap.impl.base.io.IOUtil.copy(IOUtil.java:159) > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.doCopy(AbstractOnDemandInputStream.java:170) > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.read(AbstractOnDemandInputStream.java:130) > ... 110 more > {code} > This leads to NPE exception when trying to open InputStream to get archive content deployed. > {code} > @Deployment(name = "shortener-apk") > @Instrumentable(viaPort = 8081) > @TargetsContainer("android") > @OverProtocol("Android 1.0") > public static JavaArchive getAndroidDeployment() { > // FIXME There is no APK builder yet at this moment, so we need to import file > // FIXME this should point to the APK generated from latest sources, it should not be included here > return ShrinkWrap.createFromZipFile(JavaArchive.class, new File("aerogear-android-shortener.apk")); > } > {code} > {code} > HOME C:\Users\Karel\ > JAVA_HOME C:\Program Files\Java\jdk1.7.0_45\jre\ > ANDROID_HOME C:\workspace\workspace\mobile-picketlink-test\android-sdk-windows\ > ANDROID_SDK_HOME C:\workspace\workspace\mobile-picketlink-test\ > avdName random-avd > serialId null > apiLevel 17 > abi x86 > consolePort null > adbPort null > emuBoot 600 > emuShut 60 > emuOpts > keystore C:\workspace\workspace\mobile-picketlink-test\.android\debug.keystore > keypass android > storepass android > alias androiddebugkey > sigalg SHA1withRSA > keyalg RSA > sdCard null > sdSize 128M > generateSD false > logLevel W > logType disable > logFilePath target\logcat.log > logPackageWhitelist null > logPackageBlacklist null > removeTmpDir false > tmpDir C:\home\kpiwko\devel\mobile\jbossqe-mobile\integration-testse3247fe9-b479-4720-98b4-bb10f67d74b0 > force true > {code} > Test errors with Failed to write asset to output: /res/layout/abc_action_bar_view_list_nav_layout.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 3 08:43:33 2014 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Fri, 3 Jan 2014 08:43:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1612) Add support for managed Karaf container In-Reply-To: References: Message-ID: Thomas Diesler created ARQ-1612: ----------------------------------- Summary: Add support for managed Karaf container Key: ARQ-1612 URL: https://issues.jboss.org/browse/ARQ-1612 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 3 09:01:33 2014 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Fri, 3 Jan 2014 09:01:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1612) Add support for managed Karaf container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler resolved ARQ-1612. --------------------------------- Labels: osgi (was: ) Fix Version/s: osgi_2.0.0.Final Resolution: Done Done https://github.com/arquillian/arquillian-container-osgi/commit/3ba892aca > Add support for managed Karaf container > --------------------------------------- > > Key: ARQ-1612 > URL: https://issues.jboss.org/browse/ARQ-1612 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Labels: osgi > Fix For: osgi_2.0.0.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 3 11:34:33 2014 From: issues at jboss.org (Nikolay Nikolov (JIRA)) Date: Fri, 3 Jan 2014 11:34:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-332) Add support for injectable configuration options In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933621#comment-12933621 ] Nikolay Nikolov commented on ARQ-332: ------------------------------------- If we consider junit and surefire there is property injection and it is the system properties. But as arquillian defines a separate configuration file (arquillian.xml) I also think it makes sense to provide a way to take something that you have already configured in the arquillian.xml and use it in the test in a "breezy" way instead of using workarounds with maven and placeholders. IN addition if you have for a specific container properties that if not defined are generated by the container adapter (random name, or something else) injection of the container configuration will again be very useful. > Add support for injectable configuration options > ------------------------------------------------ > > Key: ARQ-332 > URL: https://issues.jboss.org/browse/ARQ-332 > Project: Arquillian > Issue Type: Feature Request > Components: Configuration > Environment: All > Reporter: John Ament > Priority: Minor > > I may have more of a unique situation here, not sure, but I figure something like this would be useful to a lot of people. In my case, I have to test my application against multiple RDBMSs. Amongst the test cases I need to execute, the only deltas between them is really the orm.xml and persistence.xml for JPA, since we override the configuration. Currently, arquillian requires me to point to the files in my test cases. Granted, I could use a static string to manage them, but I was wondering if arquillian could provide something like this in arquillian.xml > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:glassfish="urn:arq:org.jboss.arquillian.container.glassfish.embedded_3"> > > src/test/resources/sun-resources-mysql.xml > > > > > > > And then in the test case itself > @Inject ArquillianConfiguration config; > config.getProperty("orm-xml"); > in order to access the property. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 3 14:28:32 2014 From: issues at jboss.org (John Ament (JIRA)) Date: Fri, 3 Jan 2014 14:28:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-332) Add support for injectable configuration options In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933654#comment-12933654 ] John Ament commented on ARQ-332: -------------------------------- I've essentially dealt with this by reading system properties specified in the test. The XML structure of arquillian.xml has changed dramatically though, so I don't know if what I had in here is even relevant any longer. > Add support for injectable configuration options > ------------------------------------------------ > > Key: ARQ-332 > URL: https://issues.jboss.org/browse/ARQ-332 > Project: Arquillian > Issue Type: Feature Request > Components: Configuration > Environment: All > Reporter: John Ament > Priority: Minor > > I may have more of a unique situation here, not sure, but I figure something like this would be useful to a lot of people. In my case, I have to test my application against multiple RDBMSs. Amongst the test cases I need to execute, the only deltas between them is really the orm.xml and persistence.xml for JPA, since we override the configuration. Currently, arquillian requires me to point to the files in my test cases. Granted, I could use a static string to manage them, but I was wondering if arquillian could provide something like this in arquillian.xml > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:glassfish="urn:arq:org.jboss.arquillian.container.glassfish.embedded_3"> > > src/test/resources/sun-resources-mysql.xml > > > > > > > And then in the test case itself > @Inject ArquillianConfiguration config; > config.getProperty("orm-xml"); > in order to access the property. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 6 06:03:33 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 6 Jan 2014 06:03:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1605) APK export/import does not work correcty on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933759#comment-12933759 ] Karel Piwko commented on ARQ-1605: ---------------------------------- Fix here looks good - https://github.com/arquillian/arquillian-droidium/commit/f607b3468d554d5131e1a026a7d7c2db3a550063, [~smikloso] you can proceed with merging it upstream. > APK export/import does not work correcty on Windows > --------------------------------------------------- > > Key: ARQ-1605 > URL: https://issues.jboss.org/browse/ARQ-1605 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Priority: Blocker > > On Windows platform, deployment written to temporary directory to be re-signed is empty for some reason: > {code} > org.jboss.shrinkwrap.api.exporter.ArchiveExportException: Failed to write asset to output: /res/layout/abc_action_bar_view_list_nav_layout.xml > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.read(AbstractOnDemandInputStream.java:132) > at java.io.InputStream.read(InputStream.java:170) > at java.io.InputStream.read(InputStream.java:101) > at org.arquillian.droidium.container.utils.DroidiumFileUtils.write(DroidiumFileUtils.java:175) > at org.arquillian.droidium.container.utils.DroidiumFileUtils.export(DroidiumFileUtils.java:158) > at org.arquillian.droidium.container.sign.APKSigner.resign(APKSigner.java:107) > at org.arquillian.droidium.container.deployment.AndroidDeploymentInstaller.onAndroidDeployArchive(AndroidDeploymentInstaller.java:81) > 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.arquillian.droidium.container.AndroidDeployableContainer.deploy(AndroidDeployableContainer.java:171) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127) > 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.createDeploymentContext(ContainerDeploymentContextHandler.java:78) > 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.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.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50) > 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.ContainerDeployController$1.perform(ContainerDeployController.java:95) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79) > 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:101) > 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.createClassContext(TestContextHandler.java:75) > 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.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.beforeClass(EventTestRunnerAdaptor.java:80) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > 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) > Caused by: java.lang.NullPointerException > at org.jboss.shrinkwrap.impl.base.io.IOUtil.copy(IOUtil.java:159) > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.doCopy(AbstractOnDemandInputStream.java:170) > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.read(AbstractOnDemandInputStream.java:130) > ... 110 more > {code} > This leads to NPE exception when trying to open InputStream to get archive content deployed. > {code} > @Deployment(name = "shortener-apk") > @Instrumentable(viaPort = 8081) > @TargetsContainer("android") > @OverProtocol("Android 1.0") > public static JavaArchive getAndroidDeployment() { > // FIXME There is no APK builder yet at this moment, so we need to import file > // FIXME this should point to the APK generated from latest sources, it should not be included here > return ShrinkWrap.createFromZipFile(JavaArchive.class, new File("aerogear-android-shortener.apk")); > } > {code} > {code} > HOME C:\Users\Karel\ > JAVA_HOME C:\Program Files\Java\jdk1.7.0_45\jre\ > ANDROID_HOME C:\workspace\workspace\mobile-picketlink-test\android-sdk-windows\ > ANDROID_SDK_HOME C:\workspace\workspace\mobile-picketlink-test\ > avdName random-avd > serialId null > apiLevel 17 > abi x86 > consolePort null > adbPort null > emuBoot 600 > emuShut 60 > emuOpts > keystore C:\workspace\workspace\mobile-picketlink-test\.android\debug.keystore > keypass android > storepass android > alias androiddebugkey > sigalg SHA1withRSA > keyalg RSA > sdCard null > sdSize 128M > generateSD false > logLevel W > logType disable > logFilePath target\logcat.log > logPackageWhitelist null > logPackageBlacklist null > removeTmpDir false > tmpDir C:\home\kpiwko\devel\mobile\jbossqe-mobile\integration-testse3247fe9-b479-4720-98b4-bb10f67d74b0 > force true > {code} > Test errors with Failed to write asset to output: /res/layout/abc_action_bar_view_list_nav_layout.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 6 06:25:32 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 6 Jan 2014 06:25:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1613) Allow Android Shell command timeouts In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1613: -------------------------------- Summary: Allow Android Shell command timeouts Key: ARQ-1613 URL: https://issues.jboss.org/browse/ARQ-1613 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha3 Reporter: Karel Piwko It would be handy, if Droidium can setup timeout for DDMS related operations, such as executing a shell commands. It looks like it should be possible with: {code} DdmPreferences.setTimeOut(timeout); {code} By default, timeout is set to 5 seconds, which might be not enough when running in emulated env. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 6 07:53:32 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 6 Jan 2014 07:53:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1605) APK export/import does not work correcty on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1605: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: droidium_1.0.0.Alpha4 Resolution: Done > APK export/import does not work correcty on Windows > --------------------------------------------------- > > Key: ARQ-1605 > URL: https://issues.jboss.org/browse/ARQ-1605 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Priority: Blocker > Fix For: droidium_1.0.0.Alpha4 > > > On Windows platform, deployment written to temporary directory to be re-signed is empty for some reason: > {code} > org.jboss.shrinkwrap.api.exporter.ArchiveExportException: Failed to write asset to output: /res/layout/abc_action_bar_view_list_nav_layout.xml > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.read(AbstractOnDemandInputStream.java:132) > at java.io.InputStream.read(InputStream.java:170) > at java.io.InputStream.read(InputStream.java:101) > at org.arquillian.droidium.container.utils.DroidiumFileUtils.write(DroidiumFileUtils.java:175) > at org.arquillian.droidium.container.utils.DroidiumFileUtils.export(DroidiumFileUtils.java:158) > at org.arquillian.droidium.container.sign.APKSigner.resign(APKSigner.java:107) > at org.arquillian.droidium.container.deployment.AndroidDeploymentInstaller.onAndroidDeployArchive(AndroidDeploymentInstaller.java:81) > 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.arquillian.droidium.container.AndroidDeployableContainer.deploy(AndroidDeployableContainer.java:171) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127) > 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.createDeploymentContext(ContainerDeploymentContextHandler.java:78) > 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.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.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50) > 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.ContainerDeployController$1.perform(ContainerDeployController.java:95) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79) > 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:101) > 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.createClassContext(TestContextHandler.java:75) > 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.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.beforeClass(EventTestRunnerAdaptor.java:80) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > 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) > Caused by: java.lang.NullPointerException > at org.jboss.shrinkwrap.impl.base.io.IOUtil.copy(IOUtil.java:159) > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.doCopy(AbstractOnDemandInputStream.java:170) > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.read(AbstractOnDemandInputStream.java:130) > ... 110 more > {code} > This leads to NPE exception when trying to open InputStream to get archive content deployed. > {code} > @Deployment(name = "shortener-apk") > @Instrumentable(viaPort = 8081) > @TargetsContainer("android") > @OverProtocol("Android 1.0") > public static JavaArchive getAndroidDeployment() { > // FIXME There is no APK builder yet at this moment, so we need to import file > // FIXME this should point to the APK generated from latest sources, it should not be included here > return ShrinkWrap.createFromZipFile(JavaArchive.class, new File("aerogear-android-shortener.apk")); > } > {code} > {code} > HOME C:\Users\Karel\ > JAVA_HOME C:\Program Files\Java\jdk1.7.0_45\jre\ > ANDROID_HOME C:\workspace\workspace\mobile-picketlink-test\android-sdk-windows\ > ANDROID_SDK_HOME C:\workspace\workspace\mobile-picketlink-test\ > avdName random-avd > serialId null > apiLevel 17 > abi x86 > consolePort null > adbPort null > emuBoot 600 > emuShut 60 > emuOpts > keystore C:\workspace\workspace\mobile-picketlink-test\.android\debug.keystore > keypass android > storepass android > alias androiddebugkey > sigalg SHA1withRSA > keyalg RSA > sdCard null > sdSize 128M > generateSD false > logLevel W > logType disable > logFilePath target\logcat.log > logPackageWhitelist null > logPackageBlacklist null > removeTmpDir false > tmpDir C:\home\kpiwko\devel\mobile\jbossqe-mobile\integration-testse3247fe9-b479-4720-98b4-bb10f67d74b0 > force true > {code} > Test errors with Failed to write asset to output: /res/layout/abc_action_bar_view_list_nav_layout.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 8 04:31:33 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 8 Jan 2014 04:31:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1601) adb is not found on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1601. ---------------------------- > adb is not found on Windows > --------------------------- > > Key: ARQ-1601 > URL: https://issues.jboss.org/browse/ARQ-1601 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Critical > Fix For: droidium_1.0.0.Alpha4 > > > Current logic for searching tool location does not work correctly on windows. > For instance, setup is not able to find adb if arquillian.xml file contains androidHome with backslashes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 8 04:31:33 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 8 Jan 2014 04:31:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1602) Emulator process returns immediately on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1602. ---------------------------- > Emulator process returns immediately on Windows > ----------------------------------------------- > > Key: ARQ-1602 > URL: https://issues.jboss.org/browse/ARQ-1602 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Critical > Fix For: droidium_1.0.0.Alpha4 > > > Changes introduced in ARQ-1583 are not compatible with Windows, where emulator.exe spawns another process itself and returns immediately. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 8 04:31:33 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 8 Jan 2014 04:31:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1600) ProcessExecutor might get stuck on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1600. ---------------------------- > ProcessExecutor might get stuck on Windows > ------------------------------------------- > > Key: ARQ-1600 > URL: https://issues.jboss.org/browse/ARQ-1600 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Blocker > Fix For: droidium_1.0.0.Alpha4 > > > Current execution of external process on Windows might lead to following issues, causing process deadlock: > 1/ Process stdin is not closed if no longer needed > 2/ Process stdout and stderr never reach EOF > This behavior is observed when a .bat file file is executed on Windows. This behavior is caused by missing file descriptors to underlying process spawned by bat file. > Implementation note: There are two ways how to resolve the issue. > * read output stream and consider them finished if specific message is encountered > * unwrap bat execution and execute directly underlying command -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 8 04:31:33 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 8 Jan 2014 04:31:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1603) tmpDir specification should allow to be without trailing slash In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1603. ---------------------------- > tmpDir specification should allow to be without trailing slash > -------------------------------------------------------------- > > Key: ARQ-1603 > URL: https://issues.jboss.org/browse/ARQ-1603 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha4 > > > *Given*: > I define tmpDir like "C:\temp" or /tmp > *Then*: > Droidium creates a temp directory like C:\temp-1223-1454-1245-12545 > *Expect*: > I expect directory to be rather C:\temp\1223-1454-1245-12545 > Current behavior is problematic as it requires user to be slash aware as otherwise he might want to create a directory in tree hierarchy where elevated permissions are needed. > Implemenation note: > new File(File parent, String childPath) would be the best way how to handle this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 8 04:31:33 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 8 Jan 2014 04:31:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1605) APK export/import does not work correcty on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1605. ---------------------------- > APK export/import does not work correcty on Windows > --------------------------------------------------- > > Key: ARQ-1605 > URL: https://issues.jboss.org/browse/ARQ-1605 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Priority: Blocker > Fix For: droidium_1.0.0.Alpha4 > > > On Windows platform, deployment written to temporary directory to be re-signed is empty for some reason: > {code} > org.jboss.shrinkwrap.api.exporter.ArchiveExportException: Failed to write asset to output: /res/layout/abc_action_bar_view_list_nav_layout.xml > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.read(AbstractOnDemandInputStream.java:132) > at java.io.InputStream.read(InputStream.java:170) > at java.io.InputStream.read(InputStream.java:101) > at org.arquillian.droidium.container.utils.DroidiumFileUtils.write(DroidiumFileUtils.java:175) > at org.arquillian.droidium.container.utils.DroidiumFileUtils.export(DroidiumFileUtils.java:158) > at org.arquillian.droidium.container.sign.APKSigner.resign(APKSigner.java:107) > at org.arquillian.droidium.container.deployment.AndroidDeploymentInstaller.onAndroidDeployArchive(AndroidDeploymentInstaller.java:81) > 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.arquillian.droidium.container.AndroidDeployableContainer.deploy(AndroidDeployableContainer.java:171) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127) > 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.createDeploymentContext(ContainerDeploymentContextHandler.java:78) > 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.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.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50) > 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.ContainerDeployController$1.perform(ContainerDeployController.java:95) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79) > 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:101) > 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.createClassContext(TestContextHandler.java:75) > 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.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.beforeClass(EventTestRunnerAdaptor.java:80) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > 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) > Caused by: java.lang.NullPointerException > at org.jboss.shrinkwrap.impl.base.io.IOUtil.copy(IOUtil.java:159) > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.doCopy(AbstractOnDemandInputStream.java:170) > at org.jboss.shrinkwrap.impl.base.exporter.AbstractOnDemandInputStream.read(AbstractOnDemandInputStream.java:130) > ... 110 more > {code} > This leads to NPE exception when trying to open InputStream to get archive content deployed. > {code} > @Deployment(name = "shortener-apk") > @Instrumentable(viaPort = 8081) > @TargetsContainer("android") > @OverProtocol("Android 1.0") > public static JavaArchive getAndroidDeployment() { > // FIXME There is no APK builder yet at this moment, so we need to import file > // FIXME this should point to the APK generated from latest sources, it should not be included here > return ShrinkWrap.createFromZipFile(JavaArchive.class, new File("aerogear-android-shortener.apk")); > } > {code} > {code} > HOME C:\Users\Karel\ > JAVA_HOME C:\Program Files\Java\jdk1.7.0_45\jre\ > ANDROID_HOME C:\workspace\workspace\mobile-picketlink-test\android-sdk-windows\ > ANDROID_SDK_HOME C:\workspace\workspace\mobile-picketlink-test\ > avdName random-avd > serialId null > apiLevel 17 > abi x86 > consolePort null > adbPort null > emuBoot 600 > emuShut 60 > emuOpts > keystore C:\workspace\workspace\mobile-picketlink-test\.android\debug.keystore > keypass android > storepass android > alias androiddebugkey > sigalg SHA1withRSA > keyalg RSA > sdCard null > sdSize 128M > generateSD false > logLevel W > logType disable > logFilePath target\logcat.log > logPackageWhitelist null > logPackageBlacklist null > removeTmpDir false > tmpDir C:\home\kpiwko\devel\mobile\jbossqe-mobile\integration-testse3247fe9-b479-4720-98b4-bb10f67d74b0 > force true > {code} > Test errors with Failed to write asset to output: /res/layout/abc_action_bar_view_list_nav_layout.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 9 05:33:32 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 9 Jan 2014 05:33:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1614) Warp tests redirecting to wrong address In-Reply-To: References: Message-ID: Matej Novotny created ARQ-1614: ---------------------------------- Summary: Warp tests redirecting to wrong address Key: ARQ-1614 URL: https://issues.jboss.org/browse/ARQ-1614 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Environment: Fedora, Firefox Reporter: Matej Novotny When executing Warp annotated test (RF integration [test|https://github.com/richfaces/richfaces/blob/master/framework/src/test/integration/org/richfaces/ui/toggle/panelMenu/ITPanelMenu.java] to be specific), I get redirected to a *non-localhost* adress (ether adress in fact). So instead of 127.0.0.1:/... (or localhost:) I get to something like 10.25..... This is likely caused by [this|https://github.com/arquillian/arquillian-extension-warp/blob/master/impl/src/main/java/org/jboss/arquillian/warp/impl/client/proxy/DefaultURLMapping.java#L60] code. Instead of getLocalHost().getHostAddress() we should try isLoopbackAddress(). The same address should then be propagated [here|https://github.com/arquillian/arquillian-extension-warp/blob/master/impl/src/main/java/org/jboss/arquillian/warp/impl/client/proxy/WarpHttpProxyServer.java#L39] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 9 06:25:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 9 Jan 2014 06:25:33 -0500 (EST) Subject: [arquillian-issues] =?utf-8?q?=5BJBoss_JIRA=5D_=28ARQ-1615=29_War?= =?utf-8?q?p_JSF=3A_detect_and_sanitize_FacesContextWrapper=C2=A0chain?= In-Reply-To: References: Message-ID: Luk?? Fry? created ARQ-1615: ------------------------------- Summary: Warp JSF: detect and sanitize FacesContextWrapper?chain Key: ARQ-1615 URL: https://issues.jboss.org/browse/ARQ-1615 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Warp Affects Versions: warp_1.0.0.Alpha5 Reporter: Luk?? Fry? When there is a chain of {{FacesContextWrapper}}s then Warp's WrappedFacesContext might fail to be detected and Warp itself may fail. Use a while loop to iterate through wrappers in order to detect correct wrapper. Needs to be accompanied with a ftest. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 9 06:25:34 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 9 Jan 2014 06:25:34 -0500 (EST) Subject: [arquillian-issues] =?utf-8?q?=5BJBoss_JIRA=5D_=28ARQ-1615=29_War?= =?utf-8?q?p_JSF=3A_detect_and_sanitize_FacesContextWrapper=C2=A0chain?= In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934655#comment-12934655 ] Luk?? Fry? commented on ARQ-1615: --------------------------------- {code} while (facesContext instanceof FacesContextWrapper && !(facesContext instanceof WrappedFacesContext)) facesContext = ((FacesContextWrapper) facesContext).getWrapped(); } LifecycleManager manager = LifecycleManagerStore.get(FacesContext.class, facesContext); {code} > Warp JSF: detect and sanitize FacesContextWrapper?chain > ------------------------------------------------------- > > Key: ARQ-1615 > URL: https://issues.jboss.org/browse/ARQ-1615 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > > When there is a chain of {{FacesContextWrapper}}s then Warp's WrappedFacesContext might fail to be detected and Warp itself may fail. > Use a while loop to iterate through wrappers in order to detect correct wrapper. > Needs to be accompanied with a ftest. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 9 06:27:32 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 9 Jan 2014 06:27:32 -0500 (EST) Subject: [arquillian-issues] =?utf-8?q?=5BJBoss_JIRA=5D_=28ARQ-1615=29_War?= =?utf-8?q?p_JSF=3A_detect_and_sanitize_FacesContextWrapper=C2=A0chain?= In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1615: ---------------------------- Fix Version/s: warp_1.0.0.Alpha6 > Warp JSF: detect and sanitize FacesContextWrapper?chain > ------------------------------------------------------- > > Key: ARQ-1615 > URL: https://issues.jboss.org/browse/ARQ-1615 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Alpha6 > > > When there is a chain of {{FacesContextWrapper}}s then Warp's WrappedFacesContext might fail to be detected and Warp itself may fail. > Use a while loop to iterate through wrappers in order to detect correct wrapper. > Needs to be accompanied with a ftest. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 9 07:05:32 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 9 Jan 2014 07:05:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1616) Warp: upgrade WildFLy to In-Reply-To: References: Message-ID: Luk?? Fry? created ARQ-1616: ------------------------------- Summary: Warp: upgrade WildFLy to Key: ARQ-1616 URL: https://issues.jboss.org/browse/ARQ-1616 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Reporter: Luk?? Fry? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 9 07:07:32 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 9 Jan 2014 07:07:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1616) Warp: upgrade WildFly to CR1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1616: ---------------------------- Summary: Warp: upgrade WildFly to CR1 (was: Warp: upgrade WildFLy to ) Fix Version/s: warp_1.0.0.Alpha6 Assignee: Luk?? Fry? Affects Version/s: warp_1.0.0.Alpha5 Component/s: Extension - Warp > Warp: upgrade WildFly to CR1 > ---------------------------- > > Key: ARQ-1616 > URL: https://issues.jboss.org/browse/ARQ-1616 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Alpha6 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 9 07:09:32 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 9 Jan 2014 07:09:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1598) Warp on WildFly: CDI fails to inject into inspection that is inner static class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQ-1598. ----------------------------- Assignee: Luk?? Fry? Resolution: Done > Warp on WildFly: CDI fails to inject into inspection that is inner static class > ------------------------------------------------------------------------------- > > Key: ARQ-1598 > URL: https://issues.jboss.org/browse/ARQ-1598 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Environment: WildFly 8.0.0.Beta2-SNAPSHOT > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Alpha6 > > > When class is inner static class: > {code} > public class MyTest { > @Test > public void test1() { > Warp....inspect(new MyInspection()); > Warp....inspect(new MyInspection()); // fails > } > @Test > public void test2() { > Warp....inspect(new MyInspection()); // fails > } > public static class MyInspection() { > } > } > {code} > the first inspection pass, but all subsequent inspections fails in the scope of one deployment. > ---- > I think that is because the class is already loaded in classloader and its scanning might be cached by Weld. > ---- > A issue was originally reproduced and reported here: > https://issues.jboss.org/browse/RF-13417 > ---- > Exception and cause: > {code} > 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) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > 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.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValue > {code} > {code} > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 9 07:09:32 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 9 Jan 2014 07:09:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1616) Warp: upgrade WildFly to CR1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQ-1616. ----------------------------- Resolution: Done > Warp: upgrade WildFly to CR1 > ---------------------------- > > Key: ARQ-1616 > URL: https://issues.jboss.org/browse/ARQ-1616 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Alpha6 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 9 07:11:32 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 9 Jan 2014 07:11:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1562) Warp: doesn't provide a built-in support for matching GET/POST requests by their parameters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1562: ---------------------------- Issue Type: Enhancement (was: Bug) > Warp: doesn't provide a built-in support for matching GET/POST requests by their parameters > ------------------------------------------------------------------------------------------- > > Key: ARQ-1562 > URL: https://issues.jboss.org/browse/ARQ-1562 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Priority: Critical > Fix For: warp_1.0.0.Alpha6 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 9 07:19:32 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 9 Jan 2014 07:19:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1560) Having Warp in Classpath causes NPE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934663#comment-12934663 ] Luk?? Fry? commented on ARQ-1560: --------------------------------- Lukas, I believe this test isn't valid as with no @Deployment method you won't get any URL in {code} @ArquillianResource URL deploymentPath; {code} The {{@ArquillianResource URL}} stands for an URL of the {{@Deployment}}. --- Could you describe your use case little bit more? Aren't you using custom URL provider registered into Arquillian? > Having Warp in Classpath causes NPE > ----------------------------------- > > Key: ARQ-1560 > URL: https://issues.jboss.org/browse/ARQ-1560 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Environment: Windows 8 64 Bit Jboss 7.1.1 > Reporter: Lukas Eichler > Priority: Blocker > Fix For: warp_1.0.0.Alpha6 > > > This basic test creates a NPE for having Wrap in the classpath and not containing a @Deployment method. Although it isn't a wrap test it gets treated as one. > {code} > @RunWith(Arquillian.class) > public class BasicTest { > @Drone > WebDriver browser; > @ArquillianResource > URL deploymentPath; > @Test > public void firstTest() throws Exception { > browser.navigate().to("http://google.com"); > assertEquals("Google", browser.getTitle()); > } > } > {code} > {code} > Stacktrace > java.lang.NullPointerException > at org.jboss.arquillian.warp.impl.client.proxy.ProxyURLProvider.lookup(ProxyURLProvider.java:70) > at org.jboss.arquillian.graphene.location.ContextRootStoreInitializer.getContextRoot(ContextRootStoreInitializer.java:54) > at org.jboss.arquillian.graphene.location.ContextRootStoreInitializer.setupLocationForClass(ContextRootStoreInitializer.java:47) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:48) > at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.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 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.before(EventTestRunnerAdaptor.java:95) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:222) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:77) > at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:195) > at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at com.intellij.rt.execution.CommandLineWrapper.main(CommandLineWrapper.java:121) > java.lang.IllegalStateException: Unexpected callable present in Drone Context, should be already instantiated at this moment. > at org.jboss.arquillian.drone.impl.InstanceOrCallableInstanceImpl.asInstance(InstanceOrCallableInstanceImpl.java:57) > at org.jboss.arquillian.drone.impl.DroneEnhancer.deenhanceDrone(DroneEnhancer.java:119) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.drone.impl.DroneDestructor.destroyClassScopedDrone(DroneDestructor.java:83) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.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 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.afterClass(EventTestRunnerAdaptor.java:87) > at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:77) > at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:195) > at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at com.intellij.rt.execution.CommandLineWrapper.main(CommandLineWrapper.java:121) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 9 07:19:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 9 Jan 2014 07:19:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1560) Having Warp in Classpath causes NPE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1560: ---------------------------- Priority: Major (was: Blocker) > Having Warp in Classpath causes NPE > ----------------------------------- > > Key: ARQ-1560 > URL: https://issues.jboss.org/browse/ARQ-1560 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Environment: Windows 8 64 Bit Jboss 7.1.1 > Reporter: Lukas Eichler > Fix For: warp_1.0.0.Alpha6 > > > This basic test creates a NPE for having Wrap in the classpath and not containing a @Deployment method. Although it isn't a wrap test it gets treated as one. > {code} > @RunWith(Arquillian.class) > public class BasicTest { > @Drone > WebDriver browser; > @ArquillianResource > URL deploymentPath; > @Test > public void firstTest() throws Exception { > browser.navigate().to("http://google.com"); > assertEquals("Google", browser.getTitle()); > } > } > {code} > {code} > Stacktrace > java.lang.NullPointerException > at org.jboss.arquillian.warp.impl.client.proxy.ProxyURLProvider.lookup(ProxyURLProvider.java:70) > at org.jboss.arquillian.graphene.location.ContextRootStoreInitializer.getContextRoot(ContextRootStoreInitializer.java:54) > at org.jboss.arquillian.graphene.location.ContextRootStoreInitializer.setupLocationForClass(ContextRootStoreInitializer.java:47) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:48) > at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.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 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.before(EventTestRunnerAdaptor.java:95) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:222) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:77) > at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:195) > at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at com.intellij.rt.execution.CommandLineWrapper.main(CommandLineWrapper.java:121) > java.lang.IllegalStateException: Unexpected callable present in Drone Context, should be already instantiated at this moment. > at org.jboss.arquillian.drone.impl.InstanceOrCallableInstanceImpl.asInstance(InstanceOrCallableInstanceImpl.java:57) > at org.jboss.arquillian.drone.impl.DroneEnhancer.deenhanceDrone(DroneEnhancer.java:119) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.drone.impl.DroneDestructor.destroyClassScopedDrone(DroneDestructor.java:83) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.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 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.afterClass(EventTestRunnerAdaptor.java:87) > at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:77) > at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:195) > at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at com.intellij.rt.execution.CommandLineWrapper.main(CommandLineWrapper.java:121) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 9 07:19:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 9 Jan 2014 07:19:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1560) Having Warp in Classpath causes NPE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1560: ---------------------------- Fix Version/s: (was: warp_1.0.0.Alpha6) > Having Warp in Classpath causes NPE > ----------------------------------- > > Key: ARQ-1560 > URL: https://issues.jboss.org/browse/ARQ-1560 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Environment: Windows 8 64 Bit Jboss 7.1.1 > Reporter: Lukas Eichler > > This basic test creates a NPE for having Wrap in the classpath and not containing a @Deployment method. Although it isn't a wrap test it gets treated as one. > {code} > @RunWith(Arquillian.class) > public class BasicTest { > @Drone > WebDriver browser; > @ArquillianResource > URL deploymentPath; > @Test > public void firstTest() throws Exception { > browser.navigate().to("http://google.com"); > assertEquals("Google", browser.getTitle()); > } > } > {code} > {code} > Stacktrace > java.lang.NullPointerException > at org.jboss.arquillian.warp.impl.client.proxy.ProxyURLProvider.lookup(ProxyURLProvider.java:70) > at org.jboss.arquillian.graphene.location.ContextRootStoreInitializer.getContextRoot(ContextRootStoreInitializer.java:54) > at org.jboss.arquillian.graphene.location.ContextRootStoreInitializer.setupLocationForClass(ContextRootStoreInitializer.java:47) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:48) > at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.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 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.before(EventTestRunnerAdaptor.java:95) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:222) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:77) > at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:195) > at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at com.intellij.rt.execution.CommandLineWrapper.main(CommandLineWrapper.java:121) > java.lang.IllegalStateException: Unexpected callable present in Drone Context, should be already instantiated at this moment. > at org.jboss.arquillian.drone.impl.InstanceOrCallableInstanceImpl.asInstance(InstanceOrCallableInstanceImpl.java:57) > at org.jboss.arquillian.drone.impl.DroneEnhancer.deenhanceDrone(DroneEnhancer.java:119) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.drone.impl.DroneDestructor.destroyClassScopedDrone(DroneDestructor.java:83) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.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 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.afterClass(EventTestRunnerAdaptor.java:87) > at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:77) > at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:195) > at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at com.intellij.rt.execution.CommandLineWrapper.main(CommandLineWrapper.java:121) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 9 07:21:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 9 Jan 2014 07:21:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1560) Having Warp in Classpath causes NPE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934664#comment-12934664 ] Luk?? Fry? commented on ARQ-1560: --------------------------------- https://gist.github.com/lfryc/8333275 > Having Warp in Classpath causes NPE > ----------------------------------- > > Key: ARQ-1560 > URL: https://issues.jboss.org/browse/ARQ-1560 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Environment: Windows 8 64 Bit Jboss 7.1.1 > Reporter: Lukas Eichler > > This basic test creates a NPE for having Wrap in the classpath and not containing a @Deployment method. Although it isn't a wrap test it gets treated as one. > {code} > @RunWith(Arquillian.class) > public class BasicTest { > @Drone > WebDriver browser; > @ArquillianResource > URL deploymentPath; > @Test > public void firstTest() throws Exception { > browser.navigate().to("http://google.com"); > assertEquals("Google", browser.getTitle()); > } > } > {code} > {code} > Stacktrace > java.lang.NullPointerException > at org.jboss.arquillian.warp.impl.client.proxy.ProxyURLProvider.lookup(ProxyURLProvider.java:70) > at org.jboss.arquillian.graphene.location.ContextRootStoreInitializer.getContextRoot(ContextRootStoreInitializer.java:54) > at org.jboss.arquillian.graphene.location.ContextRootStoreInitializer.setupLocationForClass(ContextRootStoreInitializer.java:47) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:48) > at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.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 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.before(EventTestRunnerAdaptor.java:95) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:222) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:77) > at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:195) > at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at com.intellij.rt.execution.CommandLineWrapper.main(CommandLineWrapper.java:121) > java.lang.IllegalStateException: Unexpected callable present in Drone Context, should be already instantiated at this moment. > at org.jboss.arquillian.drone.impl.InstanceOrCallableInstanceImpl.asInstance(InstanceOrCallableInstanceImpl.java:57) > at org.jboss.arquillian.drone.impl.DroneEnhancer.deenhanceDrone(DroneEnhancer.java:119) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.drone.impl.DroneDestructor.destroyClassScopedDrone(DroneDestructor.java:83) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 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.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 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.afterClass(EventTestRunnerAdaptor.java:87) > at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:77) > at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:195) > at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at com.intellij.rt.execution.CommandLineWrapper.main(CommandLineWrapper.java:121) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 9 09:11:32 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 9 Jan 2014 09:11:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1613) Allow Android Shell command timeouts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1613: -------------------------------------- Assignee: Stefan Miklosovic > Allow Android Shell command timeouts > ------------------------------------ > > Key: ARQ-1613 > URL: https://issues.jboss.org/browse/ARQ-1613 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > It would be handy, if Droidium can setup timeout for DDMS related operations, such as executing a shell commands. > It looks like it should be possible with: > {code} > DdmPreferences.setTimeOut(timeout); > {code} > By default, timeout is set to 5 seconds, which might be not enough when running in emulated env. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 9 12:47:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 9 Jan 2014 12:47:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1617) Warp: reconsider httpcore dependency of Warp impl In-Reply-To: References: Message-ID: Luk?? Fry? created ARQ-1617: ------------------------------- Summary: Warp: reconsider httpcore dependency of Warp impl Key: ARQ-1617 URL: https://issues.jboss.org/browse/ARQ-1617 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Warp Affects Versions: warp_1.0.0.Alpha6 Reporter: Luk?? Fry? We could either shade it or bring own implementation - that poses quite a risk to get that right. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 9 12:55:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 9 Jan 2014 12:55:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1561) Warp proxy tries to rewrite binary files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQ-1561. ----------------------------- Assignee: Luk?? Fry? Resolution: Done > Warp proxy tries to rewrite binary files > ---------------------------------------- > > Key: ARQ-1561 > URL: https://issues.jboss.org/browse/ARQ-1561 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha5 > Reporter: Jan Dosoudil > Assignee: Luk?? Fry? > Priority: Critical > Fix For: warp_1.0.0.Alpha6 > > Attachments: empty.png, empty2.png > > > It's related to ARQ-1552 - rewrite calls new String(byte[]) on response byte[] which may fail on binary files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 9 12:57:32 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 9 Jan 2014 12:57:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1562) Warp: doesn't provide a built-in support for matching GET/POST requests by their parameters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1562: ---------------------------- Forum Reference: https://community.jboss.org/thread/234234 > Warp: doesn't provide a built-in support for matching GET/POST requests by their parameters > ------------------------------------------------------------------------------------------- > > Key: ARQ-1562 > URL: https://issues.jboss.org/browse/ARQ-1562 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Priority: Critical > Fix For: warp_1.0.0.Alpha6 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 10 04:57:32 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 10 Jan 2014 04:57:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1489) response payload was never registered when used with OCPsoft Rewrite In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1489: ---------------------------- Description: I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp. Warp tests work as long as I use the original unaliased URLs. Warp tests using the aliased URLs fail with {quote} ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered {quote} I created a demonstration project, see README.md for details: https://github.com/albers/arquillian-showcase/tree/rewrite was: I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp. Warp tests work as long as I use the original unaliased URLs. Warp tests using the aliased URLs fail with ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered I created a demonstration project, see README.md for details: https://github.com/albers/arquillian-showcase/tree/rewrite > response payload was never registered when used with OCPsoft Rewrite > -------------------------------------------------------------------- > > Key: ARQ-1489 > URL: https://issues.jboss.org/browse/ARQ-1489 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha4 > Environment: Arquillian Warp 1.0.0.Alpha4 with Rewrite 2.0.7.Final in a JBoss AS 7.1.1.Final > Reporter: Harald Albers > Fix For: warp_1.0.0.Alpha6 > > > I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp. > Warp tests work as long as I use the original unaliased URLs. > Warp tests using the aliased URLs fail with > {quote} > ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered > {quote} > I created a demonstration project, see README.md for details: > https://github.com/albers/arquillian-showcase/tree/rewrite -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 10 07:25:33 2014 From: issues at jboss.org (Tom Eicher (JIRA)) Date: Fri, 10 Jan 2014 07:25:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-540) Support @ArquillianResource URL for in-container test cases In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934938#comment-12934938 ] Tom Eicher commented on ARQ-540: -------------------------------- There are valid use cases for "mixed tests" (in-container http tests), e.g. setup test using EJBs and Persistence Context, then send http request to the server, then user EJBs and Persistence Context again to verify the effects of the http call's operation. Thus, we need a way to know the URL in testable=true / non-RunAsClient tests. Injection like suggested in this issue would be the most straightforward solution from the user perspective. If that's not possible, or too much effort, please consider at least adding the URL to System.getProperties() or similar, so we can get the URL in any legal way. (currently there is none that I know of ... https://community.jboss.org/thread/235866 ) > Support @ArquillianResource URL for in-container test cases > ----------------------------------------------------------- > > Key: ARQ-540 > URL: https://issues.jboss.org/browse/ARQ-540 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.CR2 > Reporter: Ian Brandt > Fix For: 2.0.0.Beta1 > > > From [IRC|http://echelog.matzon.dk/logs/browse/jbosstesting/1312408800]: > {quote} > [2:13pm] ianbrandt: aslak, Should @ArquillianResource injection work for in-container test cases? It works fine when I try it for an as-client test, but when I do the same in-container the org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider.protocolMetadata.get() is null, so no context URL. I verified the container is returning a non-null ProtocolMetaData from deploy(...). > [2:15pm] aslak: ianbrandt, no it currently doesn't work > [2:16pm] aslak: ianbrandt, it probably should, but i'm not sure we have the info incontianer without doing a callback to the client.. > [2:16pm] aslak: ianbrandt, but then we don't know which deployment we are when incontianer, so we have a little problem there.. > [2:17pm] ianbrandt: aslak, Ah, okay. > [2:17pm] aslak: no wait we do > [2:18pm] aslak: the Protocol is executed within a DeploymentScope/ContainerScope, so when it gets the callback, it has the correct context.. > [2:18pm] aslak: we tho need OperatesOnDeployment support for that tho, cuz you possible want to inject URLs not to your self, but to another deployment on possible another contianer that you should invoke from incontainer > [2:19pm] aslak: so from incontianer on dep 1, we can do @ArqRes @OperatesOnDep("dep2") URL url; > [2:23pm] ianbrandt: aslak, Makes sense. It's a little more than I could take on at the moment. I was just augmenting the Tomcat tests to show @ArqRes usage. I'll skip it for shouldBeAbleToInvokeServletInDeployedWebApp, and JIRA+Wiki the limitation. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Sun Jan 12 13:32:32 2014 From: issues at jboss.org (=?UTF-8?Q?P=C3=ABtr_Andreev_=28JIRA=29?=) Date: Sun, 12 Jan 2014 13:32:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1618) Transaction extension configuration is not loaded early enough if working with ArquillianSuiteExtension In-Reply-To: References: Message-ID: P?tr Andreev created ARQ-1618: --------------------------------- Summary: Transaction extension configuration is not loaded early enough if working with ArquillianSuiteExtension Key: ARQ-1618 URL: https://issues.jboss.org/browse/ARQ-1618 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Transaction Affects Versions: transaction_1.0.0.Final Environment: Win7,CentOS Jboss7, Wildfly8 Reporter: P?tr Andreev Priority: Minor The TransactionConfigurationProducer loads an extension configuration on demand using the BeforeSuite event. This behaviour appears to be insufficient when Aslak`s Brute Force Arquillian Suite Extension is in play, since the Suite Extension interferes the test case bootstrap process and enforces early usage of ARQ components. As a suggestion for TX-ext to support such a constellation the configuration loading of transaction extension can be moved right into the phase where ConfigurationRegistrar loads configurations and notifies observers about available ArquillianDescriptors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Sun Jan 12 13:36:32 2014 From: issues at jboss.org (=?UTF-8?Q?P=C3=ABtr_Andreev_=28JIRA=29?=) Date: Sun, 12 Jan 2014 13:36:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1618) Transaction extension configuration is not loaded early enough when working with ArquillianSuiteExtension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P?tr Andreev updated ARQ-1618: ------------------------------ Summary: Transaction extension configuration is not loaded early enough when working with ArquillianSuiteExtension (was: Transaction extension configuration is not loaded early enough if working with ArquillianSuiteExtension) > Transaction extension configuration is not loaded early enough when working with ArquillianSuiteExtension > --------------------------------------------------------------------------------------------------------- > > Key: ARQ-1618 > URL: https://issues.jboss.org/browse/ARQ-1618 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Transaction > Affects Versions: transaction_1.0.0.Final > Environment: Win7,CentOS > Jboss7, Wildfly8 > Reporter: P?tr Andreev > Priority: Minor > > The TransactionConfigurationProducer loads an extension configuration on demand using the BeforeSuite event. This behaviour appears to be insufficient when Aslak`s Brute Force Arquillian Suite Extension is in play, since the Suite Extension interferes the test case bootstrap process and enforces early usage of ARQ components. > As a suggestion for TX-ext to support such a constellation the configuration loading of transaction extension can be moved right into the phase where ConfigurationRegistrar loads configurations and notifies observers about available ArquillianDescriptors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Sun Jan 12 13:40:32 2014 From: issues at jboss.org (=?UTF-8?Q?P=C3=ABtr_Andreev_=28JIRA=29?=) Date: Sun, 12 Jan 2014 13:40:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1618) Transaction extension configuration is not loaded early enough when working with ArquillianSuiteExtension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P?tr Andreev updated ARQ-1618: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-transaction/pull/8 > Transaction extension configuration is not loaded early enough when working with ArquillianSuiteExtension > --------------------------------------------------------------------------------------------------------- > > Key: ARQ-1618 > URL: https://issues.jboss.org/browse/ARQ-1618 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Transaction > Affects Versions: transaction_1.0.0.Final > Environment: Win7,CentOS > Jboss7, Wildfly8 > Reporter: P?tr Andreev > Priority: Minor > > The TransactionConfigurationProducer loads an extension configuration on demand using the BeforeSuite event. This behaviour appears to be insufficient when Aslak`s Brute Force Arquillian Suite Extension is in play, since the Suite Extension interferes the test case bootstrap process and enforces early usage of ARQ components. > As a suggestion for TX-ext to support such a constellation the configuration loading of transaction extension can be moved right into the phase where ConfigurationRegistrar loads configurations and notifies observers about available ArquillianDescriptors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Sun Jan 12 13:42:32 2014 From: issues at jboss.org (=?UTF-8?Q?P=C3=ABtr_Andreev_=28JIRA=29?=) Date: Sun, 12 Jan 2014 13:42:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1618) Transaction extension configuration is not loaded early enough when working with ArquillianSuiteExtension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935180#comment-12935180 ] P?tr Andreev commented on ARQ-1618: ----------------------------------- @Aslak: are there (m)any other issues preventing the Brute Force Extension to be incorporated into the ARQ master? I find that this extension is great enhancement saving lot of development time. > Transaction extension configuration is not loaded early enough when working with ArquillianSuiteExtension > --------------------------------------------------------------------------------------------------------- > > Key: ARQ-1618 > URL: https://issues.jboss.org/browse/ARQ-1618 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Transaction > Affects Versions: transaction_1.0.0.Final > Environment: Win7,CentOS > Jboss7, Wildfly8 > Reporter: P?tr Andreev > Priority: Minor > > The TransactionConfigurationProducer loads an extension configuration on demand using the BeforeSuite event. This behaviour appears to be insufficient when Aslak`s Brute Force Arquillian Suite Extension is in play, since the Suite Extension interferes the test case bootstrap process and enforces early usage of ARQ components. > As a suggestion for TX-ext to support such a constellation the configuration loading of transaction extension can be moved right into the phase where ConfigurationRegistrar loads configurations and notifies observers about available ArquillianDescriptors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 13 07:40:32 2014 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Mon, 13 Jan 2014 07:40:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1619) Tomcat managed container ignores allowConnectingToRunningServer In-Reply-To: References: Message-ID: Thomas Diesler created ARQ-1619: ----------------------------------- Summary: Tomcat managed container ignores allowConnectingToRunningServer Key: ARQ-1619 URL: https://issues.jboss.org/browse/ARQ-1619 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Tomcat Containers Affects Versions: tomcat_1.0.0.CR5 Reporter: Thomas Diesler The flag is not checked {code} if(manager.isRunning()) { throw new LifecycleException( "The server is already running! " + "Managed containers does not support connecting to running server instances due to the " + "possible harmful effect of connecting to the wrong server. Please stop server before running or " + "change to another type of container.\n" + "To disable this check and allow Arquillian to connect to a running server, " + "set allowConnectingToRunningServer to true in the container configuration" ); } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 13 10:45:34 2014 From: issues at jboss.org (Iwan Zarembo (JIRA)) Date: Mon, 13 Jan 2014 10:45:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-553) NullPointerException in arquillianBeforeClass when running with testng in parallel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935352#comment-12935352 ] Iwan Zarembo commented on ARQ-553: ---------------------------------- Hi, will this issue be resolved? It is already a few years old and nothing happened. The Issue in https://issues.jboss.org/browse/ARQ-127 contains also a test project to reproduce the issue. > NullPointerException in arquillianBeforeClass when running with testng in parallel > ---------------------------------------------------------------------------------- > > Key: ARQ-553 > URL: https://issues.jboss.org/browse/ARQ-553 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.0.CR1, 1.0.0.CR2 > Reporter: Tom Hintz > Priority: Critical > > Running with testng in parallel causes a NPE in org.jboss.arquillian.testng.Arquillian.arquillianBeforeClass(Arquillian.java:76), even with one thread. > testng runs arquillianBeforeSuite on main, but arquillianBeforeClass on pool-2-thread-1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Jan 14 03:09:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 14 Jan 2014 03:09:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1620) Switch integration tests to WildFly as a default container In-Reply-To: References: Message-ID: Luk?? Fry? created ARQ-1620: ------------------------------- Summary: Switch integration tests to WildFly as a default container Key: ARQ-1620 URL: https://issues.jboss.org/browse/ARQ-1620 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Warp Reporter: Luk?? Fry? Assignee: Luk?? Fry? Fix For: warp_1.0.0.Alpha6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Jan 14 03:13:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 14 Jan 2014 03:13:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1621) Upgrade LittleProxy to 1.0.0-beta-5 In-Reply-To: References: Message-ID: Luk?? Fry? created ARQ-1621: ------------------------------- Summary: Upgrade LittleProxy to 1.0.0-beta-5 Key: ARQ-1621 URL: https://issues.jboss.org/browse/ARQ-1621 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Extension - Warp Affects Versions: warp_1.0.0.Alpha5 Reporter: Luk?? Fry? Fix For: warp_1.0.0.Alpha6 I assume that an upgrade from 0.5.3 to 1.0.0-beta-5 will be rather breaking, but it promises to fix some intermitent issues we are seeing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Jan 14 03:21:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 14 Jan 2014 03:21:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1620) Switch integration tests to WildFly as a default container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQ-1620. ----------------------------- Resolution: Done > Switch integration tests to WildFly as a default container > ---------------------------------------------------------- > > Key: ARQ-1620 > URL: https://issues.jboss.org/browse/ARQ-1620 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Alpha6 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Jan 14 03:21:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 14 Jan 2014 03:21:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1621) Upgrade LittleProxy to 1.0.0-beta-5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQ-1621. ----------------------------- Resolution: Done > Upgrade LittleProxy to 1.0.0-beta-5 > ----------------------------------- > > Key: ARQ-1621 > URL: https://issues.jboss.org/browse/ARQ-1621 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Alpha6 > > > I assume that an upgrade from 0.5.3 to 1.0.0-beta-5 will be rather breaking, but it promises to fix some intermitent issues we are seeing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Jan 14 03:21:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 14 Jan 2014 03:21:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1621) Upgrade LittleProxy to 1.0.0-beta-5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned ARQ-1621: ------------------------------- Assignee: Luk?? Fry? > Upgrade LittleProxy to 1.0.0-beta-5 > ----------------------------------- > > Key: ARQ-1621 > URL: https://issues.jboss.org/browse/ARQ-1621 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Alpha6 > > > I assume that an upgrade from 0.5.3 to 1.0.0-beta-5 will be rather breaking, but it promises to fix some intermitent issues we are seeing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Jan 14 03:23:32 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 14 Jan 2014 03:23:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1242) Warp: test exception thrown during Proxy processing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1242: ---------------------------- Fix Version/s: warp_1.0.0.Beta1 (was: warp_1.0.0.Alpha6) > Warp: test exception thrown during Proxy processing > --------------------------------------------------- > > Key: ARQ-1242 > URL: https://issues.jboss.org/browse/ARQ-1242 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: warp_1.0.0.Beta1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > We should test what happens when Proxy fails, > and make sure the errors are handled properly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Jan 14 03:39:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 14 Jan 2014 03:39:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1562) Warp: doesn't provide a built-in support for matching GET/POST requests by their parameters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935516#comment-12935516 ] Luk?? Fry? commented on ARQ-1562: --------------------------------- *query parameters:* http://docs.jboss.org/netty/3.2/api/org/jboss/netty/handler/codec/http/QueryStringDecoder.html *form data:* {code} public void messageReceived(ChannelHandlerContext ctx, MessageEvent e) throws Exception { HttpRequest request = (HttpRequest) e.getMessage(); HttpPostRequestDecoder decoder = new HttpPostRequestDecoder(new DefaultHttpDataFactory(false), request); InterfaceHttpData data = decoder.getBodyHttpData("fromField1"); if (data.getHttpDataType() == HttpDataType.Attribute) { Attribute attribute = (Attribute) data; String value = attribute.getValue() System.out.println("fromField1 :" + value); } } {code} > Warp: doesn't provide a built-in support for matching GET/POST requests by their parameters > ------------------------------------------------------------------------------------------- > > Key: ARQ-1562 > URL: https://issues.jboss.org/browse/ARQ-1562 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Priority: Critical > Fix For: warp_1.0.0.Alpha6 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Jan 14 03:39:34 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 14 Jan 2014 03:39:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1562) Warp: doesn't provide a built-in support for matching GET/POST requests by their parameters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935516#comment-12935516 ] Luk?? Fry? edited comment on ARQ-1562 at 1/14/14 3:38 AM: ---------------------------------------------------------- *query parameters:* http://docs.jboss.org/netty/3.2/api/org/jboss/netty/handler/codec/http/QueryStringDecoder.html *form data:* {code} public void messageReceived(ChannelHandlerContext ctx, MessageEvent e) throws Exception { HttpRequest request = (HttpRequest) e.getMessage(); HttpPostRequestDecoder decoder = new HttpPostRequestDecoder(new DefaultHttpDataFactory(false), request); InterfaceHttpData data = decoder.getBodyHttpData("fromField1"); if (data.getHttpDataType() == HttpDataType.Attribute) { Attribute attribute = (Attribute) data; String value = attribute.getValue() System.out.println("fromField1 :" + value); } } {code} http://stackoverflow.com/questions/8659522/how-to-decode-http-post-data-in-java was (Author: lfryc): *query parameters:* http://docs.jboss.org/netty/3.2/api/org/jboss/netty/handler/codec/http/QueryStringDecoder.html *form data:* {code} public void messageReceived(ChannelHandlerContext ctx, MessageEvent e) throws Exception { HttpRequest request = (HttpRequest) e.getMessage(); HttpPostRequestDecoder decoder = new HttpPostRequestDecoder(new DefaultHttpDataFactory(false), request); InterfaceHttpData data = decoder.getBodyHttpData("fromField1"); if (data.getHttpDataType() == HttpDataType.Attribute) { Attribute attribute = (Attribute) data; String value = attribute.getValue() System.out.println("fromField1 :" + value); } } {code} > Warp: doesn't provide a built-in support for matching GET/POST requests by their parameters > ------------------------------------------------------------------------------------------- > > Key: ARQ-1562 > URL: https://issues.jboss.org/browse/ARQ-1562 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Priority: Critical > Fix For: warp_1.0.0.Alpha6 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Jan 14 09:05:32 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 14 Jan 2014 09:05:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-417) Support for automatic scrolling to element before its usage In-Reply-To: References: Message-ID: Juraj H?ska created ARQGRA-417: ---------------------------------- Summary: Support for automatic scrolling to element before its usage Key: ARQGRA-417 URL: https://issues.jboss.org/browse/ARQGRA-417 Project: Arquillian Graphene Issue Type: Feature Request Components: core Affects Versions: 2.0.1.Final Reporter: Juraj H?ska Priority: Minor It would be nice if Graphene supports automatic scrolling of browser window to {{WebElement}} / Page Fragment before its is used. It can be useful for interactions with various popups web components: contextMenu, tooltip, ... Those components can not be interacted correctly when they are not in the viewport, and thus one needs to scroll to them manually in his test. It is often problem in CI environment, where tests run on screens with lower resolution (smaller part of the page fit the browser window, and lot of elements are not in the viewport). My naive implementation of this would look like: * intercept all calls to {{WebElements}} and PageFragments root elements * in the interceptor method get the location of the element by: {{Point location = element.getLocation();}} * a then scroll to it: {{jsExecutor.executeScript("window.scrollTo("" + location.getX() +", " + location.getY() + ")");}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 15 02:51:32 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 15 Jan 2014 02:51:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1562) Warp: doesn't provide a built-in support for matching GET/POST requests by their parameters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935782#comment-12935782 ] Luk?? Fry? commented on ARQ-1562: --------------------------------- Feature branch: https://github.com/arquillian/arquillian-extension-warp/tree/ARQ-1562-filtering-requests-by-parameters > Warp: doesn't provide a built-in support for matching GET/POST requests by their parameters > ------------------------------------------------------------------------------------------- > > Key: ARQ-1562 > URL: https://issues.jboss.org/browse/ARQ-1562 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Priority: Critical > Fix For: warp_1.0.0.Alpha6 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 15 02:51:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 15 Jan 2014 02:51:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1562) Warp: doesn't provide a built-in support for matching GET/POST requests by their parameters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935783#comment-12935783 ] Luk?? Fry? commented on ARQ-1562: --------------------------------- We need some tests in place. > Warp: doesn't provide a built-in support for matching GET/POST requests by their parameters > ------------------------------------------------------------------------------------------- > > Key: ARQ-1562 > URL: https://issues.jboss.org/browse/ARQ-1562 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Priority: Critical > Fix For: warp_1.0.0.Alpha6 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 15 02:59:32 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 15 Jan 2014 02:59:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1622) Warp: resolves wrong URL for communication with proxy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1622: ---------------------------- Fix Version/s: warp_1.0.0.Alpha6 > Warp: resolves wrong URL for communication with proxy > ----------------------------------------------------- > > Key: ARQ-1622 > URL: https://issues.jboss.org/browse/ARQ-1622 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Alpha6 > > > That's because we use > InetAddress.getLocalHost().getHostAddress(); > https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Alpha5/impl/src/main/java/org/jboss/arquillian/warp/impl/client/proxy/DefaultURLMapping.java#L60 > ---- > I think we should either > 1) copy the host from realUrl or > 2) iterate over all network interfaces and choose loopback one > [1] http://stackoverflow.com/questions/16444753/inetaddress-getlocalhost-gethostaddress-is-returning-127-0-1-1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 15 02:59:32 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 15 Jan 2014 02:59:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1622) Warp: resolves wrong URL for communication with proxy In-Reply-To: References: Message-ID: Luk?? Fry? created ARQ-1622: ------------------------------- Summary: Warp: resolves wrong URL for communication with proxy Key: ARQ-1622 URL: https://issues.jboss.org/browse/ARQ-1622 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Warp Affects Versions: warp_1.0.0.Alpha5 Reporter: Luk?? Fry? That's because we use InetAddress.getLocalHost().getHostAddress(); https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Alpha5/impl/src/main/java/org/jboss/arquillian/warp/impl/client/proxy/DefaultURLMapping.java#L60 ---- I think we should either 1) copy the host from realUrl or 2) iterate over all network interfaces and choose loopback one [1] http://stackoverflow.com/questions/16444753/inetaddress-getlocalhost-gethostaddress-is-returning-127-0-1-1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 15 03:05:32 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 15 Jan 2014 03:05:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1489) Warp: response payload was never registered when used with OCPsoft Rewrite In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1489: ---------------------------- Summary: Warp: response payload was never registered when used with OCPsoft Rewrite (was: response payload was never registered when used with OCPsoft Rewrite) > Warp: response payload was never registered when used with OCPsoft Rewrite > -------------------------------------------------------------------------- > > Key: ARQ-1489 > URL: https://issues.jboss.org/browse/ARQ-1489 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha4 > Environment: Arquillian Warp 1.0.0.Alpha4 with Rewrite 2.0.7.Final in a JBoss AS 7.1.1.Final > Reporter: Harald Albers > Fix For: warp_1.0.0.Alpha6 > > > I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp. > Warp tests work as long as I use the original unaliased URLs. > Warp tests using the aliased URLs fail with > {quote} > ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered > {quote} > I created a demonstration project, see README.md for details: > https://github.com/albers/arquillian-showcase/tree/rewrite -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 15 03:07:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 15 Jan 2014 03:07:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1622) Warp: resolves wrong URL for communication with proxy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935786#comment-12935786 ] Luk?? Fry? commented on ARQ-1622: --------------------------------- We can't use host from realProxy directly, since it doesn't have to be a local host. > Warp: resolves wrong URL for communication with proxy > ----------------------------------------------------- > > Key: ARQ-1622 > URL: https://issues.jboss.org/browse/ARQ-1622 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Alpha6 > > > That's because we use > InetAddress.getLocalHost().getHostAddress(); > https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Alpha5/impl/src/main/java/org/jboss/arquillian/warp/impl/client/proxy/DefaultURLMapping.java#L60 > ---- > I think we should either > 1) copy the host from realUrl or > 2) iterate over all network interfaces and choose loopback one > [1] http://stackoverflow.com/questions/16444753/inetaddress-getlocalhost-gethostaddress-is-returning-127-0-1-1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 15 03:07:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 15 Jan 2014 03:07:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1622) Warp: resolves wrong URL for communication with proxy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935786#comment-12935786 ] Luk?? Fry? edited comment on ARQ-1622 at 1/15/14 3:06 AM: ---------------------------------------------------------- We can't use host from realProxy directly, since it doesn't have to be a local host. We should use approach (2), but the proxy needs to be started on the specified. was (Author: lfryc): We can't use host from realProxy directly, since it doesn't have to be a local host. > Warp: resolves wrong URL for communication with proxy > ----------------------------------------------------- > > Key: ARQ-1622 > URL: https://issues.jboss.org/browse/ARQ-1622 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Alpha6 > > > That's because we use > InetAddress.getLocalHost().getHostAddress(); > https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Alpha5/impl/src/main/java/org/jboss/arquillian/warp/impl/client/proxy/DefaultURLMapping.java#L60 > ---- > I think we should either > 1) --copy the host from realUrl-- or > 2) iterate over all network interfaces and choose loopback one > [1] http://stackoverflow.com/questions/16444753/inetaddress-getlocalhost-gethostaddress-is-returning-127-0-1-1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 15 03:07:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 15 Jan 2014 03:07:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1622) Warp: resolves wrong URL for communication with proxy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1622: ---------------------------- Description: That's because we use InetAddress.getLocalHost().getHostAddress(); https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Alpha5/impl/src/main/java/org/jboss/arquillian/warp/impl/client/proxy/DefaultURLMapping.java#L60 ---- I think we should either 1) --copy the host from realUrl-- or 2) iterate over all network interfaces and choose loopback one [1] http://stackoverflow.com/questions/16444753/inetaddress-getlocalhost-gethostaddress-is-returning-127-0-1-1 was: That's because we use InetAddress.getLocalHost().getHostAddress(); https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Alpha5/impl/src/main/java/org/jboss/arquillian/warp/impl/client/proxy/DefaultURLMapping.java#L60 ---- I think we should either 1) copy the host from realUrl or 2) iterate over all network interfaces and choose loopback one [1] http://stackoverflow.com/questions/16444753/inetaddress-getlocalhost-gethostaddress-is-returning-127-0-1-1 > Warp: resolves wrong URL for communication with proxy > ----------------------------------------------------- > > Key: ARQ-1622 > URL: https://issues.jboss.org/browse/ARQ-1622 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Alpha6 > > > That's because we use > InetAddress.getLocalHost().getHostAddress(); > https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Alpha5/impl/src/main/java/org/jboss/arquillian/warp/impl/client/proxy/DefaultURLMapping.java#L60 > ---- > I think we should either > 1) --copy the host from realUrl-- or > 2) iterate over all network interfaces and choose loopback one > [1] http://stackoverflow.com/questions/16444753/inetaddress-getlocalhost-gethostaddress-is-returning-127-0-1-1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 15 03:31:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 15 Jan 2014 03:31:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1622) Warp: resolves wrong URL for communication with proxy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQ-1622. ----------------------------- Assignee: Luk?? Fry? Resolution: Done > Warp: resolves wrong URL for communication with proxy > ----------------------------------------------------- > > Key: ARQ-1622 > URL: https://issues.jboss.org/browse/ARQ-1622 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Alpha6 > > > That's because we use > InetAddress.getLocalHost().getHostAddress(); > https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Alpha5/impl/src/main/java/org/jboss/arquillian/warp/impl/client/proxy/DefaultURLMapping.java#L60 > ---- > I think we should either > 1) --copy the host from realUrl-- or > 2) iterate over all network interfaces and choose loopback one > [1] http://stackoverflow.com/questions/16444753/inetaddress-getlocalhost-gethostaddress-is-returning-127-0-1-1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 16 03:34:32 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 16 Jan 2014 03:34:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1623) Warp: mark tests with category FullEEProfile that will indicate where they can run In-Reply-To: References: Message-ID: Luk?? Fry? created ARQ-1623: ------------------------------- Summary: Warp: mark tests with category FullEEProfile that will indicate where they can run Key: ARQ-1623 URL: https://issues.jboss.org/browse/ARQ-1623 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Warp Affects Versions: warp_1.0.0.Alpha5 Reporter: Luk?? Fry? E.g. these tests can't run on Tomee: {code} org.jboss.arquillian.warp.ftest.ear.EarWarpTest.test 0.0 1 org.jboss.arquillian.warp.ftest.ear.EarWarpTest.test {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 16 05:36:32 2014 From: issues at jboss.org (Philippe Mazenauer (JIRA)) Date: Thu, 16 Jan 2014 05:36:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1624) Create a DeployableContainer integration for remote WAS V8.5 In-Reply-To: References: Message-ID: Philippe Mazenauer created ARQ-1624: --------------------------------------- Summary: Create a DeployableContainer integration for remote WAS V8.5 Key: ARQ-1624 URL: https://issues.jboss.org/browse/ARQ-1624 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WebSphere Containers Reporter: Philippe Mazenauer Assignee: Gerhard Poul Adding Websphere Application Server V8.5 to possible WAS Connectors by simply copying the WAS 8 Connector and changing the following section in the POM: com.ibm.websphere ws-admin-client 8.5.0 system ${was_home}/runtimes/com.ibm.ws.admin.client_8.5.0.jar And Probably making a proper release out of it, so you don't have to compile it local. Thanks fandji -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 16 05:38:33 2014 From: issues at jboss.org (Philippe Mazenauer (JIRA)) Date: Thu, 16 Jan 2014 05:38:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1624) Create a DeployableContainer integration for remote WAS V8.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philippe Mazenauer updated ARQ-1624: ------------------------------------ Description: Adding Websphere Application Server V8.5 to possible WAS Connectors by simply copying the WAS 8 Connector and changing the following section in the POM: com.ibm.websphere ws-admin-client 8.5.0 system ${was_home}/runtimes/com.ibm.ws.admin.client_8.5.0.jar And Probably making a proper release out of it, so you don't have to compile it local. Thanks Philippe Mazenauer was: Adding Websphere Application Server V8.5 to possible WAS Connectors by simply copying the WAS 8 Connector and changing the following section in the POM: com.ibm.websphere ws-admin-client 8.5.0 system ${was_home}/runtimes/com.ibm.ws.admin.client_8.5.0.jar And Probably making a proper release out of it, so you don't have to compile it local. Thanks fandji > Create a DeployableContainer integration for remote WAS V8.5 > ------------------------------------------------------------ > > Key: ARQ-1624 > URL: https://issues.jboss.org/browse/ARQ-1624 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Reporter: Philippe Mazenauer > Assignee: Gerhard Poul > > Adding Websphere Application Server V8.5 to possible WAS Connectors by simply copying the WAS 8 Connector and changing the following section in the POM: > > com.ibm.websphere > ws-admin-client > 8.5.0 > system ${was_home}/runtimes/com.ibm.ws.admin.client_8.5.0.jar > > And Probably making a proper release out of it, so you don't have to compile it local. > Thanks > Philippe Mazenauer -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 16 08:20:32 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 16 Jan 2014 08:20:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1625) Create an extension to handle platform dependent code In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1625: -------------------------------- Summary: Create an extension to handle platform dependent code Key: ARQ-1625 URL: https://issues.jboss.org/browse/ARQ-1625 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Spacelift Reporter: Karel Piwko Assignee: Karel Piwko Fix For: spacelift_1.0.0.Alpha1 Create an extension that would simply running external processes and fetching platform dependent data for other extensions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 16 09:38:32 2014 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Thu, 16 Jan 2014 09:38:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-828) Documentation doesn't specify that WebSphere artifactions are not available in a maven repository In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Poul closed ARQ-828. ---------------------------- Resolution: Incomplete Description Addressed everything that I knew to address and haven't gotten any further feedback. [~kito99] When you have additional information and this needs more work, please reopen and update. tnx! > Documentation doesn't specify that WebSphere artifactions are not available in a maven repository > ------------------------------------------------------------------------------------------------- > > Key: ARQ-828 > URL: https://issues.jboss.org/browse/ARQ-828 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation, WebSphere Containers > Reporter: Kito Mann > Assignee: Gerhard Poul > > The reference guide lists the WAS container artifact ids, but doesn't point out that they're not available in any Maven repository, and doesn't provide a link to the instructions in the Wiki for building it from github. > The official docs say that WAS support isn't available yet and doesn't list the artifact ids at all. It should list the WAS artifact ids and provide instructions for building as well. > FYI, the instructions for building was-remote-8, was-embedded-8, and/or was-remote-7 are here: https://community.jboss.org/wiki/BuildingArquillianWASContainer -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 16 10:42:32 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 16 Jan 2014 10:42:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1626) Document requirements for PhantomJS on headless machines In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1626: -------------------------------- Summary: Document requirements for PhantomJS on headless machines Key: ARQ-1626 URL: https://issues.jboss.org/browse/ARQ-1626 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Karel Piwko *When*: I want to execute PhantomJS based job on a headless Linux based machine. *Then*: There are still some dependencies that might not be available on the machine. And it might fail. *Expecting*: Missing dependencies/native packages are documented. Depedencies are: fontconfig, openssl, freetype -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 16 10:42:33 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 16 Jan 2014 10:42:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1626) Document requirements for PhantomJS on headless machines In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1626: ----------------------------- Affects Version/s: drone_1.2.1.Final > Document requirements for PhantomJS on headless machines > -------------------------------------------------------- > > Key: ARQ-1626 > URL: https://issues.jboss.org/browse/ARQ-1626 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: drone_1.2.1.Final > Reporter: Karel Piwko > > *When*: > I want to execute PhantomJS based job on a headless Linux based machine. > *Then*: > There are still some dependencies that might not be available on the machine. And it might fail. > *Expecting*: > Missing dependencies/native packages are documented. > Depedencies are: > fontconfig, openssl, freetype -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 17 04:09:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 17 Jan 2014 04:09:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1562) Warp: doesn't provide a built-in support for matching GET/POST requests by their parameters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQ-1562. ----------------------------- Assignee: Luk?? Fry? Resolution: Done > Warp: doesn't provide a built-in support for matching GET/POST requests by their parameters > ------------------------------------------------------------------------------------------- > > Key: ARQ-1562 > URL: https://issues.jboss.org/browse/ARQ-1562 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: warp_1.0.0.Alpha6 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 17 04:09:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 17 Jan 2014 04:09:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1498) Warp: get frozen when testing RichFaces FileUpload In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1498: ---------------------------- Fix Version/s: warp_1.0.0.Beta1 (was: warp_1.0.0.Alpha6) > Warp: get frozen when testing RichFaces FileUpload > -------------------------------------------------- > > Key: ARQ-1498 > URL: https://issues.jboss.org/browse/ARQ-1498 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha4 > Reporter: Luk?? Fry? > Priority: Critical > Fix For: warp_1.0.0.Beta1 > > > Upstream issue: RF-13217 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 17 04:11:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 17 Jan 2014 04:11:33 -0500 (EST) Subject: [arquillian-issues] =?utf-8?q?=5BJBoss_JIRA=5D_=28ARQ-1615=29_War?= =?utf-8?q?p_JSF=3A_detect_and_sanitize_FacesContextWrapper=C2=A0chain?= In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1615: ---------------------------- Fix Version/s: warp_1.0.0.Beta1 (was: warp_1.0.0.Alpha6) > Warp JSF: detect and sanitize FacesContextWrapper?chain > ------------------------------------------------------- > > Key: ARQ-1615 > URL: https://issues.jboss.org/browse/ARQ-1615 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Beta1 > > > When there is a chain of {{FacesContextWrapper}}s then Warp's WrappedFacesContext might fail to be detected and Warp itself may fail. > Use a while loop to iterate through wrappers in order to detect correct wrapper. > Needs to be accompanied with a ftest. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 17 04:15:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 17 Jan 2014 04:15:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1489) Warp: response payload was never registered when used with OCPsoft Rewrite In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1489: ---------------------------- Fix Version/s: warp_1.0.0.Beta1 (was: warp_1.0.0.Alpha6) > Warp: response payload was never registered when used with OCPsoft Rewrite > -------------------------------------------------------------------------- > > Key: ARQ-1489 > URL: https://issues.jboss.org/browse/ARQ-1489 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha4 > Environment: Arquillian Warp 1.0.0.Alpha4 with Rewrite 2.0.7.Final in a JBoss AS 7.1.1.Final > Reporter: Harald Albers > Fix For: warp_1.0.0.Beta1 > > > I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp. > Warp tests work as long as I use the original unaliased URLs. > Warp tests using the aliased URLs fail with > {quote} > ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered > {quote} > I created a demonstration project, see README.md for details: > https://github.com/albers/arquillian-showcase/tree/rewrite -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 17 06:19:34 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Fri, 17 Jan 2014 06:19:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1625) Create an extension to handle platform dependent code In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1625. ------------------------------ Resolution: Done Extension is available at https://github.com/arquillian/arquillian-spacelift > Create an extension to handle platform dependent code > ----------------------------------------------------- > > Key: ARQ-1625 > URL: https://issues.jboss.org/browse/ARQ-1625 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: spacelift_1.0.0.Alpha1 > > > Create an extension that would simply running external processes and fetching platform dependent data for other extensions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 17 06:21:32 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Fri, 17 Jan 2014 06:21:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1625) Create an extension to handle platform dependent code In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1625. ---------------------------- > Create an extension to handle platform dependent code > ----------------------------------------------------- > > Key: ARQ-1625 > URL: https://issues.jboss.org/browse/ARQ-1625 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: spacelift_1.0.0.Alpha1 > > > Create an extension that would simply running external processes and fetching platform dependent data for other extensions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 20 09:06:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 20 Jan 2014 09:06:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1627) Warp: refactor fluent observer specification API for clarity In-Reply-To: References: Message-ID: Luk?? Fry? created ARQ-1627: ------------------------------- Summary: Warp: refactor fluent observer specification API for clarity Key: ARQ-1627 URL: https://issues.jboss.org/browse/ARQ-1627 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Warp Affects Versions: warp_1.0.0.Alpha6 Reporter: Luk?? Fry? {code} request().header("Content-Type").equalTo("application/json"); request().parameter().containsValue("id", "12345"); {code} should be {code} request().header("Content-Type").equalTo("application/json"); request().parameter("id").contains("12345"); {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 20 11:16:29 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 20 Jan 2014 11:16:29 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1628) Warp: fails to verify async servlets In-Reply-To: References: Message-ID: Luk?? Fry? created ARQ-1628: ------------------------------- Summary: Warp: fails to verify async servlets Key: ARQ-1628 URL: https://issues.jboss.org/browse/ARQ-1628 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Warp Reporter: Luk?? Fry? Upstream issue: RF-13290 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 20 11:16:29 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 20 Jan 2014 11:16:29 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1628) Warp: fails to verify async servlets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1628: ---------------------------- Affects Version/s: warp_1.0.0.Alpha6 > Warp: fails to verify async servlets > ------------------------------------ > > Key: ARQ-1628 > URL: https://issues.jboss.org/browse/ARQ-1628 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha6 > Reporter: Luk?? Fry? > > Upstream issue: RF-13290 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 20 11:16:29 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 20 Jan 2014 11:16:29 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1628) Warp: fails to verify async servlets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12937267#comment-12937267 ] Luk?? Fry? commented on ARQ-1628: --------------------------------- We need to reproduce this on ftests to confirm that is the issue. > Warp: fails to verify async servlets > ------------------------------------ > > Key: ARQ-1628 > URL: https://issues.jboss.org/browse/ARQ-1628 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha6 > Reporter: Luk?? Fry? > > Upstream issue: RF-13290 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 20 11:16:30 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 20 Jan 2014 11:16:30 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1628) Warp: fails to verify async servlets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1628: ---------------------------- Fix Version/s: warp_1.0.0.Beta1 > Warp: fails to verify async servlets > ------------------------------------ > > Key: ARQ-1628 > URL: https://issues.jboss.org/browse/ARQ-1628 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha6 > Reporter: Luk?? Fry? > Priority: Critical > Fix For: warp_1.0.0.Beta1 > > > Upstream issue: RF-13290 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 20 11:16:30 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 20 Jan 2014 11:16:30 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1628) Warp: fails to verify async servlets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1628: ---------------------------- Priority: Critical (was: Major) > Warp: fails to verify async servlets > ------------------------------------ > > Key: ARQ-1628 > URL: https://issues.jboss.org/browse/ARQ-1628 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha6 > Reporter: Luk?? Fry? > Priority: Critical > > Upstream issue: RF-13290 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 20 17:18:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 20 Jan 2014 17:18:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1629) Integrate Android driver web testing from Selendroid into Droidium and deprecate web plugin In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1629: -------------------------------------- Summary: Integrate Android driver web testing from Selendroid into Droidium and deprecate web plugin Key: ARQ-1629 URL: https://issues.jboss.org/browse/ARQ-1629 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: droidium_1.0.0.Alpha4 Reporter: Stefan Miklosovic -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 20 17:18:35 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 20 Jan 2014 17:18:35 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1629) Integrate Android driver web testing from Selendroid into Droidium and deprecate web plugin In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1629: ----------------------------------- Component/s: Extension - Droidium > Integrate Android driver web testing from Selendroid into Droidium and deprecate web plugin > ------------------------------------------------------------------------------------------- > > Key: ARQ-1629 > URL: https://issues.jboss.org/browse/ARQ-1629 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 20 17:28:28 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 20 Jan 2014 17:28:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1629) Integrate Android driver web testing from Selendroid into Droidium and deprecate web plugin In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1629: -------------------------------------- Assignee: Stefan Miklosovic > Integrate Android driver web testing from Selendroid into Droidium and deprecate web plugin > ------------------------------------------------------------------------------------------- > > Key: ARQ-1629 > URL: https://issues.jboss.org/browse/ARQ-1629 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Jan 21 03:08:28 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 21 Jan 2014 03:08:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1581) Droidium does not work with remote emulators In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12937413#comment-12937413 ] Stefan Miklosovic commented on ARQ-1581: ---------------------------------------- It was pushed in upstream few days ago: https://android-review.googlesource.com/#/c/79532/ > Droidium does not work with remote emulators > -------------------------------------------- > > Key: ARQ-1581 > URL: https://issues.jboss.org/browse/ARQ-1581 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > *When*: > I use Android Jenkins Plugin to start the device > *Then*: > It starts the emulator using remote syntax, that is including --port port1,port2 > *Expect*: > Drodium will connect to already running emulator. > *Actual problem*: > AndroidDevice and IDevice isEmulator() call is not able to parse the data retrieved from adb devices. This results into Droidium trying to start emulator with the same name, however this emulator is already started so event marking correct startup is never send and test fails. > Output: > {code} > export ANDROID_ADB_SERVER_PORT=52892 > [tester at fedora19 ~]$ ANDROID_SDK_HOME=`pwd`/workspace/mobile-eap-test ./tools/android-sdk/platform-tools/adb devices > List of devices attached > localhost:46689 device > {code} > However, emulators are expected to be in format of emulator-XYZ. > Drodium should be able to modify the behavior to handle this correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 22 02:16:29 2014 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Wed, 22 Jan 2014 02:16:29 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-264) Create a DeployableContainer integration for remote WAS V7.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Poul closed ARQ-264. ---------------------------- Fix Version/s: was_1.0.0.Alpha2 (was: was_1.0.0.next) Resolution: Done > Create a DeployableContainer integration for remote WAS V7.0 > ------------------------------------------------------------ > > Key: ARQ-264 > URL: https://issues.jboss.org/browse/ARQ-264 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Reporter: Aslak Knutsen > Assignee: Gerhard Poul > Priority: Minor > Fix For: was_1.0.0.Alpha2 > > > Create a DeployableContainer integration for remote WebSphere Application Server V7.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 22 02:18:28 2014 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Wed, 22 Jan 2014 02:18:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1624) Create a DeployableContainer integration for remote WAS V8.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Poul updated ARQ-1624: ------------------------------ Assignee: (was: Gerhard Poul) > Create a DeployableContainer integration for remote WAS V8.5 > ------------------------------------------------------------ > > Key: ARQ-1624 > URL: https://issues.jboss.org/browse/ARQ-1624 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Reporter: Philippe Mazenauer > > Adding Websphere Application Server V8.5 to possible WAS Connectors by simply copying the WAS 8 Connector and changing the following section in the POM: > > com.ibm.websphere > ws-admin-client > 8.5.0 > system ${was_home}/runtimes/com.ibm.ws.admin.client_8.5.0.jar > > And Probably making a proper release out of it, so you don't have to compile it local. > Thanks > Philippe Mazenauer -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 22 08:00:30 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 22 Jan 2014 08:00:30 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1623) Warp: mark tests with category FullEEProfile that will indicate where they can run In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12937857#comment-12937857 ] Aslak Knutsen commented on ARQ-1623: ------------------------------------ Why not? TomEE supports EAR. I believe their Arquillian integration had some ear issues but that should be fixed.. > Warp: mark tests with category FullEEProfile that will indicate where they can run > ---------------------------------------------------------------------------------- > > Key: ARQ-1623 > URL: https://issues.jboss.org/browse/ARQ-1623 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > > E.g. these tests can't run on Tomee: > {code} > org.jboss.arquillian.warp.ftest.ear.EarWarpTest.test 0.0 1 > org.jboss.arquillian.warp.ftest.ear.EarWarpTest.test > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 22 10:24:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 22 Jan 2014 10:24:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1623) Warp: mark tests with category FullEEProfile that will indicate where they can run In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12937925#comment-12937925 ] Luk?? Fry? commented on ARQ-1623: --------------------------------- Good point, I will check that. > Warp: mark tests with category FullEEProfile that will indicate where they can run > ---------------------------------------------------------------------------------- > > Key: ARQ-1623 > URL: https://issues.jboss.org/browse/ARQ-1623 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > > E.g. these tests can't run on Tomee: > {code} > org.jboss.arquillian.warp.ftest.ear.EarWarpTest.test 0.0 1 > org.jboss.arquillian.warp.ftest.ear.EarWarpTest.test > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 22 10:24:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 22 Jan 2014 10:24:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1623) Warp: mark tests with category FullEEProfile that will indicate where they can run In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1623: ---------------------------- Fix Version/s: warp_1.0.0.Beta1 > Warp: mark tests with category FullEEProfile that will indicate where they can run > ---------------------------------------------------------------------------------- > > Key: ARQ-1623 > URL: https://issues.jboss.org/browse/ARQ-1623 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Beta1 > > > E.g. these tests can't run on Tomee: > {code} > org.jboss.arquillian.warp.ftest.ear.EarWarpTest.test 0.0 1 > org.jboss.arquillian.warp.ftest.ear.EarWarpTest.test > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 22 11:26:28 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 22 Jan 2014 11:26:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1630) Misspelled Permanent in Drone reusable implementation In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1630: -------------------------------- Summary: Misspelled Permanent in Drone reusable implementation Key: ARQ-1630 URL: https://issues.jboss.org/browse/ARQ-1630 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.2.1.Final Reporter: Karel Piwko Priority: Minor There is plenty of classes that misspell word permanent - they are using pernament instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 22 11:28:28 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 22 Jan 2014 11:28:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1425) Drone: unnecessary warning about unserializable capability 'droneAugmented' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1425: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-drone/pull/32 > Drone: unnecessary warning about unserializable capability 'droneAugmented' > --------------------------------------------------------------------------- > > Key: ARQ-1425 > URL: https://issues.jboss.org/browse/ARQ-1425 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Alpha2 > Reporter: Luk?? Fry? > Fix For: drone_1.3.next > > > This capability is known to be unserializable and we don't need to serialize it since it will be constructed again. > {code} > WARNING: The capability 'droneAugmented' has unserializable value of type 'org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver' and value 'ReusableRemoteWebDriver: phantomjs on LINUX (89f4b7d0-bd61-11e2-a0ae-732f3e2bcb83) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 22 11:28:28 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 22 Jan 2014 11:28:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1425) Drone: unnecessary warning about unserializable capability 'droneAugmented' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1425: ----------------------------- Fix Version/s: drone_1.2.2.Final (was: drone_1.3.next) > Drone: unnecessary warning about unserializable capability 'droneAugmented' > --------------------------------------------------------------------------- > > Key: ARQ-1425 > URL: https://issues.jboss.org/browse/ARQ-1425 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Alpha2 > Reporter: Luk?? Fry? > Fix For: drone_1.2.2.Final > > > This capability is known to be unserializable and we don't need to serialize it since it will be constructed again. > {code} > WARNING: The capability 'droneAugmented' has unserializable value of type 'org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver' and value 'ReusableRemoteWebDriver: phantomjs on LINUX (89f4b7d0-bd61-11e2-a0ae-732f3e2bcb83) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 22 11:30:28 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 22 Jan 2014 11:30:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1630) Misspelled Permanent in Drone reusable implementation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1630: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-drone/pull/32 > Misspelled Permanent in Drone reusable implementation > ----------------------------------------------------- > > Key: ARQ-1630 > URL: https://issues.jboss.org/browse/ARQ-1630 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.1.Final > Reporter: Karel Piwko > Priority: Minor > > There is plenty of classes that misspell word permanent - they are using pernament instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 22 11:30:28 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 22 Jan 2014 11:30:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1630) Misspelled Permanent in Drone reusable implementation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1630: ----------------------------- Fix Version/s: drone_1.2.2.Final > Misspelled Permanent in Drone reusable implementation > ----------------------------------------------------- > > Key: ARQ-1630 > URL: https://issues.jboss.org/browse/ARQ-1630 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.1.Final > Reporter: Karel Piwko > Priority: Minor > Fix For: drone_1.2.2.Final > > > There is plenty of classes that misspell word permanent - they are using pernament instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 22 11:58:28 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 22 Jan 2014 11:58:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1425) Drone: unnecessary warning about unserializable capability 'droneAugmented' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reassigned ARQ-1425: -------------------------------- Assignee: Karel Piwko > Drone: unnecessary warning about unserializable capability 'droneAugmented' > --------------------------------------------------------------------------- > > Key: ARQ-1425 > URL: https://issues.jboss.org/browse/ARQ-1425 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Karel Piwko > Fix For: drone_1.2.2.Final > > > This capability is known to be unserializable and we don't need to serialize it since it will be constructed again. > {code} > WARNING: The capability 'droneAugmented' has unserializable value of type 'org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver' and value 'ReusableRemoteWebDriver: phantomjs on LINUX (89f4b7d0-bd61-11e2-a0ae-732f3e2bcb83) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 22 11:58:29 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 22 Jan 2014 11:58:29 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1630) Misspelled Permanent in Drone reusable implementation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reassigned ARQ-1630: -------------------------------- Assignee: Karel Piwko > Misspelled Permanent in Drone reusable implementation > ----------------------------------------------------- > > Key: ARQ-1630 > URL: https://issues.jboss.org/browse/ARQ-1630 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.1.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Minor > Fix For: drone_1.2.2.Final > > > There is plenty of classes that misspell word permanent - they are using pernament instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 24 05:52:28 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 24 Jan 2014 05:52:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1613) Allow Android Shell command timeouts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12938508#comment-12938508 ] Stefan Miklosovic commented on ARQ-1613: ---------------------------------------- https://github.com/arquillian/arquillian-droidium/commit/d52633a35a63881a5e09f0245e6182131b5de9cb > Allow Android Shell command timeouts > ------------------------------------ > > Key: ARQ-1613 > URL: https://issues.jboss.org/browse/ARQ-1613 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > It would be handy, if Droidium can setup timeout for DDMS related operations, such as executing a shell commands. > It looks like it should be possible with: > {code} > DdmPreferences.setTimeOut(timeout); > {code} > By default, timeout is set to 5 seconds, which might be not enough when running in emulated env. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 24 05:52:29 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 24 Jan 2014 05:52:29 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1613) Allow Android Shell command timeouts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1613: ----------------------------------- Fix Version/s: droidium_1.0.0.Beta1 > Allow Android Shell command timeouts > ------------------------------------ > > Key: ARQ-1613 > URL: https://issues.jboss.org/browse/ARQ-1613 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Beta1 > > > It would be handy, if Droidium can setup timeout for DDMS related operations, such as executing a shell commands. > It looks like it should be possible with: > {code} > DdmPreferences.setTimeOut(timeout); > {code} > By default, timeout is set to 5 seconds, which might be not enough when running in emulated env. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 24 05:52:29 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 24 Jan 2014 05:52:29 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1613) Allow Android Shell command timeouts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1613. ------------------------------------ Resolution: Done > Allow Android Shell command timeouts > ------------------------------------ > > Key: ARQ-1613 > URL: https://issues.jboss.org/browse/ARQ-1613 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Beta1 > > > It would be handy, if Droidium can setup timeout for DDMS related operations, such as executing a shell commands. > It looks like it should be possible with: > {code} > DdmPreferences.setTimeOut(timeout); > {code} > By default, timeout is set to 5 seconds, which might be not enough when running in emulated env. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 27 09:01:29 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 27 Jan 2014 09:01:29 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1425) Drone: unnecessary warning about unserializable capability 'droneAugmented' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1425: ----------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/ee2e22e47b4f464c049f2d45b4b5efcff6fb08e9. Log level was reduced to FINE. > Drone: unnecessary warning about unserializable capability 'droneAugmented' > --------------------------------------------------------------------------- > > Key: ARQ-1425 > URL: https://issues.jboss.org/browse/ARQ-1425 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Karel Piwko > Fix For: drone_1.2.2.Final > > > This capability is known to be unserializable and we don't need to serialize it since it will be constructed again. > {code} > WARNING: The capability 'droneAugmented' has unserializable value of type 'org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver' and value 'ReusableRemoteWebDriver: phantomjs on LINUX (89f4b7d0-bd61-11e2-a0ae-732f3e2bcb83) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 27 09:03:28 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 27 Jan 2014 09:03:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1630) Misspelled Permanent in Drone reusable implementation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1630: ----------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/7719e84571896df21f26c0ec23c44fd578303197 > Misspelled Permanent in Drone reusable implementation > ----------------------------------------------------- > > Key: ARQ-1630 > URL: https://issues.jboss.org/browse/ARQ-1630 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.1.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Minor > Fix For: drone_1.2.2.Final > > > There is plenty of classes that misspell word permanent - they are using pernament instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 27 11:45:32 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 27 Jan 2014 11:45:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1609) Allow setting IE driver path in arquillian.xml configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1609: ----------------------------- Fix Version/s: drone_1.2.2.Final (was: drone_1.2.next) > Allow setting IE driver path in arquillian.xml configuration > ------------------------------------------------------------ > > Key: ARQ-1609 > URL: https://issues.jboss.org/browse/ARQ-1609 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.1.Final > Reporter: Oliver Ki?? > Assignee: Oliver Ki?? > Fix For: drone_1.2.2.Final > > > Currently, path to IE driver executable can be set by {{webdriver.ie.driver}} system property. It would be more convenient if the path could also be configured in {{arquillian.xml}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 27 11:45:32 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 27 Jan 2014 11:45:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1610) Update Selenium to 2.39.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1610: ----------------------------- Fix Version/s: drone_1.2.2.Final (was: drone_1.2.next) > Update Selenium to 2.39.0 > ------------------------- > > Key: ARQ-1610 > URL: https://issues.jboss.org/browse/ARQ-1610 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.1.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.2.Final > > > Update Selenium to 2.39.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 27 11:45:32 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 27 Jan 2014 11:45:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1425) Drone: unnecessary warning about unserializable capability 'droneAugmented' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1425. ---------------------------- > Drone: unnecessary warning about unserializable capability 'droneAugmented' > --------------------------------------------------------------------------- > > Key: ARQ-1425 > URL: https://issues.jboss.org/browse/ARQ-1425 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Karel Piwko > Fix For: drone_1.2.2.Final > > > This capability is known to be unserializable and we don't need to serialize it since it will be constructed again. > {code} > WARNING: The capability 'droneAugmented' has unserializable value of type 'org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver' and value 'ReusableRemoteWebDriver: phantomjs on LINUX (89f4b7d0-bd61-11e2-a0ae-732f3e2bcb83) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 27 11:45:32 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 27 Jan 2014 11:45:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1610) Update Selenium to 2.39.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1610. ---------------------------- > Update Selenium to 2.39.0 > ------------------------- > > Key: ARQ-1610 > URL: https://issues.jboss.org/browse/ARQ-1610 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.1.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.2.Final > > > Update Selenium to 2.39.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 27 11:45:33 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 27 Jan 2014 11:45:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1630) Misspelled Permanent in Drone reusable implementation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1630. ---------------------------- > Misspelled Permanent in Drone reusable implementation > ----------------------------------------------------- > > Key: ARQ-1630 > URL: https://issues.jboss.org/browse/ARQ-1630 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.1.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Minor > Fix For: drone_1.2.2.Final > > > There is plenty of classes that misspell word permanent - they are using pernament instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 27 11:45:33 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 27 Jan 2014 11:45:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1609) Allow setting IE driver path in arquillian.xml configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1609. ---------------------------- > Allow setting IE driver path in arquillian.xml configuration > ------------------------------------------------------------ > > Key: ARQ-1609 > URL: https://issues.jboss.org/browse/ARQ-1609 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.1.Final > Reporter: Oliver Ki?? > Assignee: Oliver Ki?? > Fix For: drone_1.2.2.Final > > > Currently, path to IE driver executable can be set by {{webdriver.ie.driver}} system property. It would be more convenient if the path could also be configured in {{arquillian.xml}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 27 12:43:28 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 27 Jan 2014 12:43:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-416) @InFrame duplicitly switches to iframe with fragment/page object method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-416: ------------------------------- Summary: @InFrame duplicitly switches to iframe with fragment/page object method (was: @InFrame duplicitly switches to iframe with fragment method) > @InFrame duplicitly switches to iframe with fragment/page object method > ----------------------------------------------------------------------- > > Key: ARQGRA-416 > URL: https://issues.jboss.org/browse/ARQGRA-416 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Jan Dosoudil > Assignee: Juraj H?ska > Fix For: 2.0.1.Final > > > {code} > public class Fragment { > @FindBy(id="button") > private WebElement button; > public void clickButton() { > button.click(); > } > public WebElement getButton() { > return button; > } > } > {code} > {code} > @RunWith(Arquillian.class) > @RunAsClient > public class Test { > //... > @FindBy(id="content") > @InFrame(nameOrId="frame") > private Fragment Fragment; > @Test > public void testWebElement() { > fragment.getButton().click(); //PASS > } > @Test > public void testMethod() { > fragment.clickButton(); //FAIL > } > } > {code} > Exception is: org.openqa.selenium.NoSuchFrameException: Unable to locate frame: frame -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 27 12:45:28 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 27 Jan 2014 12:45:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-416) @InFrame duplicitly switches to iframe with fragment/page object method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12939083#comment-12939083 ] Juraj H?ska commented on ARQGRA-416: ------------------------------------ It is the same for Page Object methods. The fix would be removing the further enrichment of the Page Object/Page Fragments, which is now IMO redundant. Because, the PO/PF are enriched recursively by interceptor, [here|https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/enricher/InFrameInterceptor.java#L62-64]. > @InFrame duplicitly switches to iframe with fragment/page object method > ----------------------------------------------------------------------- > > Key: ARQGRA-416 > URL: https://issues.jboss.org/browse/ARQGRA-416 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Jan Dosoudil > Assignee: Juraj H?ska > Fix For: 2.0.1.Final > > > {code} > public class Fragment { > @FindBy(id="button") > private WebElement button; > public void clickButton() { > button.click(); > } > public WebElement getButton() { > return button; > } > } > {code} > {code} > @RunWith(Arquillian.class) > @RunAsClient > public class Test { > //... > @FindBy(id="content") > @InFrame(nameOrId="frame") > private Fragment Fragment; > @Test > public void testWebElement() { > fragment.getButton().click(); //PASS > } > @Test > public void testMethod() { > fragment.clickButton(); //FAIL > } > } > {code} > Exception is: org.openqa.selenium.NoSuchFrameException: Unable to locate frame: frame -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 27 12:47:28 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 27 Jan 2014 12:47:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-416) @InFrame duplicitly switches to iframe with fragment/page object method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12939083#comment-12939083 ] Juraj H?ska edited comment on ARQGRA-416 at 1/27/14 12:46 PM: -------------------------------------------------------------- It is the same for Page Object methods. The fix would be removing the further enrichment of the Page Object/Page Fragments, which is now IMO redundant. Because, the PO/PF are enriched recursively by interceptor, [here|https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/enricher/InFrameInterceptor.java#L62-64] - so by demand, not in advance. was (Author: jhuska): It is the same for Page Object methods. The fix would be removing the further enrichment of the Page Object/Page Fragments, which is now IMO redundant. Because, the PO/PF are enriched recursively by interceptor, [here|https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/enricher/InFrameInterceptor.java#L62-64]. > @InFrame duplicitly switches to iframe with fragment/page object method > ----------------------------------------------------------------------- > > Key: ARQGRA-416 > URL: https://issues.jboss.org/browse/ARQGRA-416 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Jan Dosoudil > Assignee: Juraj H?ska > Fix For: 2.0.1.Final > > > {code} > public class Fragment { > @FindBy(id="button") > private WebElement button; > public void clickButton() { > button.click(); > } > public WebElement getButton() { > return button; > } > } > {code} > {code} > @RunWith(Arquillian.class) > @RunAsClient > public class Test { > //... > @FindBy(id="content") > @InFrame(nameOrId="frame") > private Fragment Fragment; > @Test > public void testWebElement() { > fragment.getButton().click(); //PASS > } > @Test > public void testMethod() { > fragment.clickButton(); //FAIL > } > } > {code} > Exception is: org.openqa.selenium.NoSuchFrameException: Unable to locate frame: frame -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Jan 27 12:49:28 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 27 Jan 2014 12:49:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-416) @InFrame duplicitly switches to iframe with fragment/page object method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-416: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/94 > @InFrame duplicitly switches to iframe with fragment/page object method > ----------------------------------------------------------------------- > > Key: ARQGRA-416 > URL: https://issues.jboss.org/browse/ARQGRA-416 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Jan Dosoudil > Assignee: Juraj H?ska > Fix For: 2.0.1.Final > > > {code} > public class Fragment { > @FindBy(id="button") > private WebElement button; > public void clickButton() { > button.click(); > } > public WebElement getButton() { > return button; > } > } > {code} > {code} > @RunWith(Arquillian.class) > @RunAsClient > public class Test { > //... > @FindBy(id="content") > @InFrame(nameOrId="frame") > private Fragment Fragment; > @Test > public void testWebElement() { > fragment.getButton().click(); //PASS > } > @Test > public void testMethod() { > fragment.clickButton(); //FAIL > } > } > {code} > Exception is: org.openqa.selenium.NoSuchFrameException: Unable to locate frame: frame -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Jan 28 03:13:28 2014 From: issues at jboss.org (Vitalii Chepeliuk (JIRA)) Date: Tue, 28 Jan 2014 03:13:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1631) Deployment on isolated WLS managed servers In-Reply-To: References: Message-ID: Vitalii Chepeliuk created ARQ-1631: -------------------------------------- Summary: Deployment on isolated WLS managed servers Key: ARQ-1631 URL: https://issues.jboss.org/browse/ARQ-1631 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Vitalii Chepeliuk If WLS managed servers are clustered then to deploy any APP I need only specify target attr in arquillian.xml and one Deployment method But if they are isolated and I need to deploy APP on each managed servers, like in following code @Deployment(name = "wls_managed_8001") @TargetsContainer("wsl01") public static WebArchive createDeployment() { WebArchive jar = createWebArchive(WAR_NAME) .addAsManifestResource(MANIFEST_FILE_NAME); return jar; } @Deployment(name = "wls_managed_8002") @TargetsContainer("wls02") public static WebArchive createDeployment2() { WebArchive jar = createWebArchive(WAR_NAME) .addAsManifestResource(MANIFEST_FILE_NAME); return jar; } @Test @InSequence(1) @OperateOnDeployment("wls_managed_8001") public void testAddData_wls01() throws Exception { // Add some data to APP } @Test @InSequence(2) @OperateOnDeployment("wls_managed_8002") public void testCheckData_wls02() throws Exception { // Verify if data are propagated } But there is NO support for it cause every APP we want to deploy is managed through AdminServer and then it is sending it to managed servers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Jan 28 07:23:28 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 28 Jan 2014 07:23:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1632) Update PhantomJS Driver to 1.1.2.Final to have 1.9.7 PhantomJS binary In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1632: -------------------------------- Summary: Update PhantomJS Driver to 1.1.2.Final to have 1.9.7 PhantomJS binary Key: ARQ-1632 URL: https://issues.jboss.org/browse/ARQ-1632 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.2.2.Final Reporter: Karel Piwko Update to latest available phantomjs driver. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Jan 28 07:41:28 2014 From: issues at jboss.org (Vineet Reynolds (JIRA)) Date: Tue, 28 Jan 2014 07:41:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1631) Deployment on isolated WLS managed servers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Reynolds updated ARQ-1631: --------------------------------- Component/s: WebLogic Containers > Deployment on isolated WLS managed servers > ------------------------------------------ > > Key: ARQ-1631 > URL: https://issues.jboss.org/browse/ARQ-1631 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebLogic Containers > Reporter: Vitalii Chepeliuk > > If WLS managed servers are clustered then to deploy any APP I need only specify target attr in arquillian.xml and one Deployment method > But if they are isolated and I need to deploy APP on each managed servers, like in following code > @Deployment(name = "wls_managed_8001") > @TargetsContainer("wsl01") > public static WebArchive createDeployment() { > WebArchive jar = createWebArchive(WAR_NAME) > .addAsManifestResource(MANIFEST_FILE_NAME); > return jar; > } > @Deployment(name = "wls_managed_8002") > @TargetsContainer("wls02") > public static WebArchive createDeployment2() { > WebArchive jar = createWebArchive(WAR_NAME) > .addAsManifestResource(MANIFEST_FILE_NAME); > return jar; > } > @Test > @InSequence(1) > @OperateOnDeployment("wls_managed_8001") > public void testAddData_wls01() throws Exception { > // Add some data to APP > } > @Test > @InSequence(2) > @OperateOnDeployment("wls_managed_8002") > public void testCheckData_wls02() throws Exception { > // Verify if data are propagated > } > But there is NO support for it cause every APP we want to deploy is managed through AdminServer and then it is sending it to managed servers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Jan 28 07:41:28 2014 From: issues at jboss.org (Vineet Reynolds (JIRA)) Date: Tue, 28 Jan 2014 07:41:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1631) Deployment on isolated WLS managed servers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Reynolds updated ARQ-1631: --------------------------------- Affects Version/s: wls_1.0.0.Alpha2 > Deployment on isolated WLS managed servers > ------------------------------------------ > > Key: ARQ-1631 > URL: https://issues.jboss.org/browse/ARQ-1631 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebLogic Containers > Affects Versions: wls_1.0.0.Alpha2 > Reporter: Vitalii Chepeliuk > > If WLS managed servers are clustered then to deploy any APP I need only specify target attr in arquillian.xml and one Deployment method > But if they are isolated and I need to deploy APP on each managed servers, like in following code > @Deployment(name = "wls_managed_8001") > @TargetsContainer("wsl01") > public static WebArchive createDeployment() { > WebArchive jar = createWebArchive(WAR_NAME) > .addAsManifestResource(MANIFEST_FILE_NAME); > return jar; > } > @Deployment(name = "wls_managed_8002") > @TargetsContainer("wls02") > public static WebArchive createDeployment2() { > WebArchive jar = createWebArchive(WAR_NAME) > .addAsManifestResource(MANIFEST_FILE_NAME); > return jar; > } > @Test > @InSequence(1) > @OperateOnDeployment("wls_managed_8001") > public void testAddData_wls01() throws Exception { > // Add some data to APP > } > @Test > @InSequence(2) > @OperateOnDeployment("wls_managed_8002") > public void testCheckData_wls02() throws Exception { > // Verify if data are propagated > } > But there is NO support for it cause every APP we want to deploy is managed through AdminServer and then it is sending it to managed servers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Jan 28 10:25:28 2014 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Tue, 28 Jan 2014 10:25:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1633) Add osgi bundle on demand to managed karaf container In-Reply-To: References: Message-ID: Thomas Diesler created ARQ-1633: ----------------------------------- Summary: Add osgi bundle on demand to managed karaf container Key: ARQ-1633 URL: https://issues.jboss.org/browse/ARQ-1633 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: osgi_2.0.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Jan 28 10:25:28 2014 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Tue, 28 Jan 2014 10:25:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1633) Add osgi bundle on demand to managed karaf container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler resolved ARQ-1633. --------------------------------- Resolution: Done Done in arquillian-container-karaf-managed-2.1.0.CR7 > Add osgi bundle on demand to managed karaf container > ---------------------------------------------------- > > Key: ARQ-1633 > URL: https://issues.jboss.org/browse/ARQ-1633 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: osgi_2.0.0.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 31 04:41:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 31 Jan 2014 04:41:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-418) Upgrade to Selenium 2.39.0 In-Reply-To: References: Message-ID: Luk?? Fry? created ARQGRA-418: --------------------------------- Summary: Upgrade to Selenium 2.39.0 Key: ARQGRA-418 URL: https://issues.jboss.org/browse/ARQGRA-418 Project: Arquillian Graphene Issue Type: Component Upgrade Components: integration Affects Versions: 2.0.0.Final Reporter: Luk?? Fry? Assignee: Luk?? Fry? Fix For: 2.0.1.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 31 04:41:28 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 31 Jan 2014 04:41:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-419) Upgrade to Drone 1.2.3.Final In-Reply-To: References: Message-ID: Luk?? Fry? created ARQGRA-419: --------------------------------- Summary: Upgrade to Drone 1.2.3.Final Key: ARQGRA-419 URL: https://issues.jboss.org/browse/ARQGRA-419 Project: Arquillian Graphene Issue Type: Component Upgrade Components: integration Affects Versions: 2.0.0.Final Reporter: Luk?? Fry? Assignee: Luk?? Fry? Fix For: 2.0.1.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 31 04:45:29 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 31 Jan 2014 04:45:29 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-416) @InFrame duplicitly switches to iframe with fragment/page object method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-416: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > @InFrame duplicitly switches to iframe with fragment/page object method > ----------------------------------------------------------------------- > > Key: ARQGRA-416 > URL: https://issues.jboss.org/browse/ARQGRA-416 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Jan Dosoudil > Assignee: Juraj H?ska > Fix For: 2.0.1.Final > > > {code} > public class Fragment { > @FindBy(id="button") > private WebElement button; > public void clickButton() { > button.click(); > } > public WebElement getButton() { > return button; > } > } > {code} > {code} > @RunWith(Arquillian.class) > @RunAsClient > public class Test { > //... > @FindBy(id="content") > @InFrame(nameOrId="frame") > private Fragment Fragment; > @Test > public void testWebElement() { > fragment.getButton().click(); //PASS > } > @Test > public void testMethod() { > fragment.clickButton(); //FAIL > } > } > {code} > Exception is: org.openqa.selenium.NoSuchFrameException: Unable to locate frame: frame -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 31 04:45:29 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 31 Jan 2014 04:45:29 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-418) Upgrade to Selenium 2.39.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQGRA-418. ------------------------------- Resolution: Done > Upgrade to Selenium 2.39.0 > -------------------------- > > Key: ARQGRA-418 > URL: https://issues.jboss.org/browse/ARQGRA-418 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Components: integration > Affects Versions: 2.0.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 2.0.1.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 31 04:45:29 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 31 Jan 2014 04:45:29 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-419) Upgrade to Drone 1.2.3.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQGRA-419. ------------------------------- Resolution: Done > Upgrade to Drone 1.2.3.Final > ---------------------------- > > Key: ARQGRA-419 > URL: https://issues.jboss.org/browse/ARQGRA-419 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Components: integration > Affects Versions: 2.0.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 2.0.1.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Jan 31 14:59:28 2014 From: issues at jboss.org (Martin Andersson (JIRA)) Date: Fri, 31 Jan 2014 14:59:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1099) Add arquillian.xml configuration section to the documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12940598#comment-12940598 ] Martin Andersson commented on ARQ-1099: --------------------------------------- If you ask me, I can't understand why one would wanna write one single user guide or any other type of documentation before writing documentation about Arquillian.xml. We seriously need this file covered. > Add arquillian.xml configuration section to the documentation > -------------------------------------------------------------- > > Key: ARQ-1099 > URL: https://issues.jboss.org/browse/ARQ-1099 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: Hardy Ferentschik > > At the moment there is no chapter in the documentation which describes the different workings of arquillian.xml. AFAIU each container adapter can have its own properties, but I think there is still a need to describe the basic workings, eg how to select a named container configuration via arquillian.launch. > See also: > * http://stackoverflow.com/questions/9740938/how-to-select-a-container-by-qualifyer-from-arquillian-xml > * http://stackoverflow.com/questions/10119544/where-can-i-find-the-arquillian-xml-configuration-documentation > Given that arquillian.xml is the main configuration file it is only reasonable that people try to understand Arquillian from this angle. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira