[JBoss JIRA] (ARQ-1365) Warp: CommandEventBus doesn't support (port) redirects
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1365?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on ARQ-1365:
---------------------------------
Hey Oliver, thanks to Aris' fix, the CommandService should now deal with redirects correctly, could you please check that?
> Warp: CommandEventBus doesn't support (port) redirects
> ------------------------------------------------------
>
> Key: ARQ-1365
> URL: https://issues.jboss.org/browse/ARQ-1365
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Beta1
> Reporter: Oliver Bock
> Assignee: Aris Tzoumas
> Labels: redirect, ssl, warp
> Fix For: warp_1.0.0.Alpha3
>
>
> When JBosss AS 7 is configured to redirect HTTP (port 8888) to HTTPS (8889) in standalone.xml (web subsystem) using:
> {noformat}
> <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" redirect-port="8889"/>
> <connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true">
> <ssl password="[Your_password_here]" session-timeout="900"/>
> </connector>
> {noformat}
> All Warp tests (client- and server-side) fail like this when using 1.0.0.Beta1-SNAPSHOT (client-side tests do work with 1.0.0.Alpha2):
> {noformat}
> java.lang.IllegalStateException: Error launching test at http://0.0.0.0:8888/test/CommandEventBus?className=TestClass&methodName=t.... Got 302 (Moved Temporarily)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus.execute(CommandEventBus.java:266)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus.access$100(CommandEventBus.java:67)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus$2.run(CommandEventBus.java:147)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> or
> java.lang.IllegalStateException: Error launching test at http://0.0.0.0:8888/test/CommandEventBus?className=TestClass&methodName=t.... Got 302 (Moved Temporarily)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus.execute(CommandEventBus.java:266)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus.executeCommandRemotely(CommandEventBus.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java: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.warp.impl.client.eventbus.RemoteSuiteLifecyclePropagation.sendBefore(RemoteSuiteLifecyclePropagation.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 java.lang.reflect.Method.invoke(Method.java:601)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (ARQ-1365) Warp: CommandEventBus doesn't support (port) redirects
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1365?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1365:
----------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: warp_1.0.0.Alpha3
Resolution: Done
> Warp: CommandEventBus doesn't support (port) redirects
> ------------------------------------------------------
>
> Key: ARQ-1365
> URL: https://issues.jboss.org/browse/ARQ-1365
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Beta1
> Reporter: Oliver Bock
> Assignee: Aris Tzoumas
> Labels: redirect, ssl, warp
> Fix For: warp_1.0.0.Alpha3
>
>
> When JBosss AS 7 is configured to redirect HTTP (port 8888) to HTTPS (8889) in standalone.xml (web subsystem) using:
> {noformat}
> <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" redirect-port="8889"/>
> <connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true">
> <ssl password="[Your_password_here]" session-timeout="900"/>
> </connector>
> {noformat}
> All Warp tests (client- and server-side) fail like this when using 1.0.0.Beta1-SNAPSHOT (client-side tests do work with 1.0.0.Alpha2):
> {noformat}
> java.lang.IllegalStateException: Error launching test at http://0.0.0.0:8888/test/CommandEventBus?className=TestClass&methodName=t.... Got 302 (Moved Temporarily)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus.execute(CommandEventBus.java:266)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus.access$100(CommandEventBus.java:67)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus$2.run(CommandEventBus.java:147)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> or
> java.lang.IllegalStateException: Error launching test at http://0.0.0.0:8888/test/CommandEventBus?className=TestClass&methodName=t.... Got 302 (Moved Temporarily)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus.execute(CommandEventBus.java:266)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus.executeCommandRemotely(CommandEventBus.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java: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.warp.impl.client.eventbus.RemoteSuiteLifecyclePropagation.sendBefore(RemoteSuiteLifecyclePropagation.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 java.lang.reflect.Method.invoke(Method.java:601)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (ARQGRA-289) JavaScript interfaces fails on Chrome and PhantomJS
by Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-289?page=com.atlassian.jira.plugin... ]
Jan Papousek edited comment on ARQGRA-289 at 4/4/13 4:04 AM:
-------------------------------------------------------------
This is a big problem. The process of invocation of a method on javascript interfaces is:
- assume the target JS object is defined and try to invoke its method
-- if success => return the result
-- if an exception is thrown
--- execute the installation JS script (and also dependencies)
--- check whether the page extansion is installed
--- repeat from the first point
I've tried to run EnrichmentTestCase.testUnstable on Google Chrome and the webdriver freezes instead of throwing an exception (exception is correctly logged in the console) during the first method invocation.
was (Author: jpapouse):
This is a big problem. The process of invocation of a method on javascript interfaces is:
- assume the target JS object is defined and try to invoke its method
-- if success => return the result
-- if an exception is thrown
--- execute the installation JS script (and also dependencies)
--- check whether the page extansion is installed
--- repeat from the first point
I've tried to run EnrichmentTestCase.testUnstable on Google Chrome and the webdriver freezes instead of throwing an exception (exception is correctly logged in the console).
> JavaScript interfaces fails on Chrome and PhantomJS
> ---------------------------------------------------
>
> Key: ARQGRA-289
> URL: https://issues.jboss.org/browse/ARQGRA-289
> Project: Arquillian Graphene
> Issue Type: Bug
> Reporter: Lukáš Fryč
> Assignee: Juraj Húska
> Priority: Blocker
> Fix For: 2.0.0.Alpha4
>
>
> The test is blocked so it will never end.
> Test cases are ignored before it will be fixed.
> * {{JavaScriptPageExtensionTestCase.*}}
> * {{EnrichmentTestCase.testUnstable.*}}
--
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, 9 months
[JBoss JIRA] (ARQGRA-289) JavaScript interfaces fails on Chrome and PhantomJS
by Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-289?page=com.atlassian.jira.plugin... ]
Jan Papousek commented on ARQGRA-289:
-------------------------------------
This is a big problem. The process of invocation of a method on javascript interfaces is:
- assume the target JS object is defined and try to invoke its method
-- if success => return the result
-- if an exception is thrown
--- execute the installation JS script (and also dependencies)
--- check whether the page extansion is installed
--- repeat from the first point
I've tried to run EnrichmentTestCase.testUnstable on Google Chrome and the webdriver freezes instead of throwing an exception (exception is correctly logged in the console).
> JavaScript interfaces fails on Chrome and PhantomJS
> ---------------------------------------------------
>
> Key: ARQGRA-289
> URL: https://issues.jboss.org/browse/ARQGRA-289
> Project: Arquillian Graphene
> Issue Type: Bug
> Reporter: Lukáš Fryč
> Assignee: Juraj Húska
> Priority: Blocker
> Fix For: 2.0.0.Alpha4
>
>
> The test is blocked so it will never end.
> Test cases are ignored before it will be fixed.
> * {{JavaScriptPageExtensionTestCase.*}}
> * {{EnrichmentTestCase.testUnstable.*}}
--
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, 9 months
[JBoss JIRA] (ARQ-1077) Persistence Plugin does not work with Drone/Graphene
by Eduardo de Vera Toquero (JIRA)
[ https://issues.jboss.org/browse/ARQ-1077?page=com.atlassian.jira.plugin.s... ]
Eduardo de Vera Toquero commented on ARQ-1077:
----------------------------------------------
Unfortunately, this did not work in my case. Only the test that runs in container gets the dataset injected. In the case of tests running as client, the database is not fed.
> Persistence Plugin does not work with Drone/Graphene
> ----------------------------------------------------
>
> Key: ARQ-1077
> URL: https://issues.jboss.org/browse/ARQ-1077
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Drone, Extension - Persistence
> Environment: JBoss AS 7 Container
> Reporter: Bryan Saunders
> Labels: drone, persistence
>
> Persistence Extension does not execute when being used with the Drone/Graphene extensions. When you run the tests in Client Mode the @UsingDataSet annotations do not trigger and populate the database. @ApplyScriptBefore also does not work.
--
This message 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, 9 months