December 2013 - arquillian-issues

[JBoss JIRA] (ARQ-1611) Arquillian doesn't handle Glassfish REST API redirect

by André Pinheiro (JIRA)

André Pinheiro created ARQ-1611: ----------------------------------- Summary: Arquillian doesn't handle Glassfish REST API redirect Key: ARQ-1611 URL: https://issues.jboss.org/browse/ARQ-1611 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: GlassFish Containers Affects Versions: glassfish_1.0.0.CR4 Environment: Windows client and server Windows client, Linux server Linux client, Windows server Glassfish 3.1.2.2, 4.0 and 4.0.1-b03-ml Reporter: André Pinheiro When deploying to a remote glassfish DAS instance, the REST API sends back a 302 redirect. Arquillian GlassFishClientUtil fails to handle that redirect - as it wasn't expecting that kind of response - and the following exception is thrown: {quote} com.sun.jersey.api.container.ContainerException: [status: REDIRECTION reason: Found] at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientUtil.getResponseMap(GlassFishClientUtil.java:192) at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientUtil.GETRequest(GlassFishClientUtil.java:109) at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientUtil.getChildResources(GlassFishClientUtil.java:95) at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientService.getServersList(GlassFishClientService.java:319) at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientService.startUp(GlassFishClientService.java:102) at org.jboss.arquillian.container.glassfish.CommonGlassFishManager.start(CommonGlassFishManager.java:72) at org.jboss.arquillian.container.glassfish.remote_3_1.GlassFishRestDeployableContainer.start(GlassFishRestDeployableContainer.java:59) at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:86) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:68) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:97) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68) {quote} -- This message 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

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1444) Oracle does not support query delimiter inside statements

by Michel Graciano (JIRA)

[ https://issues.jboss.org/browse/ARQ-1444?page=com.atlassian.jira.plugin.s... ] Michel Graciano updated ARQ-1444: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-persistence/pull/38 > Oracle does not support query delimiter inside statements > --------------------------------------------------------- > > Key: ARQ-1444 > URL: https://issues.jboss.org/browse/ARQ-1444 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Environment: Oracle Database. > Reporter: Michel Graciano > Assignee: Bartosz Majsak > > When we try to use @ApplyScriptBefore and the script file has more than one statement, we use ; as delimiter. The problem is that the delimiter is not removed from the statement before run it, so Oracle database return the following exception: > Caused by: java.sql.SQLSyntaxErrorException: ORA-00911: invalid character -- 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

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1444) Oracle does not support query delimiter inside statements

by Michel Graciano (JIRA)

[ https://issues.jboss.org/browse/ARQ-1444?page=com.atlassian.jira.plugin.s... ] Michel Graciano commented on ARQ-1444: -------------------------------------- I have created a pull request for this issue [1]. Can anyone review it? Thanks in advance. [1] https://github.com/arquillian/arquillian-extension-persistence/pull/38 > Oracle does not support query delimiter inside statements > --------------------------------------------------------- > > Key: ARQ-1444 > URL: https://issues.jboss.org/browse/ARQ-1444 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Environment: Oracle Database. > Reporter: Michel Graciano > Assignee: Bartosz Majsak > > When we try to use @ApplyScriptBefore and the script file has more than one statement, we use ; as delimiter. The problem is that the delimiter is not removed from the statement before run it, so Oracle database return the following exception: > Caused by: java.sql.SQLSyntaxErrorException: ORA-00911: invalid character -- 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

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1082) Allow to provide external data sources on the SPI level.

by Bernard Labno (JIRA)

[ https://issues.jboss.org/browse/ARQ-1082?page=com.atlassian.jira.plugin.s... ] Bernard Labno commented on ARQ-1082: ------------------------------------ This is awesome! Does that mean that we could use persistence on the client side? > Allow to provide external data sources on the SPI level. > -------------------------------------------------------- > > Key: ARQ-1082 > URL: https://issues.jboss.org/browse/ARQ-1082 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha4 > Reporter: Jakub Narloch > Assignee: Jakub Narloch > > I would like to be able to "inject" external data sources into the APE, like for example Spring ones. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic commented on ARQ-1534: ---------------------------------------- [~kpiwko] https://android-review.googlesource.com/#/c/73310/ > There is no way how to set server port of Android Debug Bridge > -------------------------------------------------------------- > > Key: ARQ-1534 > URL: https://issues.jboss.org/browse/ARQ-1534 > 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 > > *Given*: > I have Android tooling installed in Eclipse/JBDS. > *When:* > I use Droidium in tests fro IDE. > *Expect*: > No having any errors in DDMS output in IDE. > *Additional information*: > It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly. > See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037. > We need a way how to change this server port in Droidium configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ARQ-1610) Update Selenium to 2.39.0

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1610?page=com.atlassian.jira.plugin.s... ] Karel Piwko resolved ARQ-1610. ------------------------------ Assignee: Karel Piwko Fix Version/s: drone_1.2.next Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/60b3428a3... > 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.next > > > 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

11 years

1
0
0 / 0

[JBoss JIRA] (ARQ-1610) Update Selenium to 2.39.0

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1610: -------------------------------- Summary: 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 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

11 years

1
0
0 / 0

[JBoss JIRA] (ARQ-1609) Allow setting IE driver path in arquillian.xml configuration

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1609?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1609: ---------------------------------- Use property *ieDriverBinary* to set path to the IE driver binary. > 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.next > > > 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

11 years

1
0
0 / 0

[JBoss JIRA] (ARQ-1609) Allow setting IE driver path in arquillian.xml configuration

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1609?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1609: ----------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Oliver Kišš Fix Version/s: drone_1.2.next Resolution: Done > 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.next > > > 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

11 years

1
0
0 / 0

[JBoss JIRA] (ARQ-1609) Allow setting IE driver path in arquillian.xml configuration

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1609?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1609: ---------------------------------- Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/7ccc54510... > 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šš > > 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues December 2013