[JBoss JIRA] (ARQ-1365) Warp: CommandEventBus doesn't support (port) redirects
by Oliver Bock (JIRA)
[ https://issues.jboss.org/browse/ARQ-1365?page=com.atlassian.jira.plugin.s... ]
Oliver Bock updated ARQ-1365:
-----------------------------
Labels: redirect ssl warp (was: warp)
> 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
> Labels: redirect, ssl, warp
>
> 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, 1 month
[JBoss JIRA] (ARQ-1366) Warp: support server-side testing of web pages that require authentication
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1366?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1366:
----------------------------
Assignee: Oliver Bock
> Warp: support server-side testing of web pages that require authentication
> --------------------------------------------------------------------------
>
> Key: ARQ-1366
> URL: https://issues.jboss.org/browse/ARQ-1366
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha2
> Reporter: Oliver Bock
> Assignee: Oliver Bock
> Labels: authentication, exception, warp
>
> When web pages are protected by a security-constraint (web.xml) that requires authentication, Warp JSF runs into a {{SynchronizationPoint$ServerResponseTimeoutException}} while executing server-side tests using {{inspect()}}, like the second one below. Standard FORM authentication (via {{j_security_check}}) and Web Driver's {{htmlunit}} browser are used in this case.
> More observations:
> * Client-side tests work just fine (first test below)
> * Disabling the security-constraint (no authentication) allows the server-side test to finish successfully
> {noformat}
> @Test
> @RunAsClient
> public void testOnClient() {
> browser.get(deploymentUrl + "index.xhtml");
> doLoginIfNeeded(browser);
> // this works just fine!
> Assert.assertEquals("INDEX", browser.getTitle());
> }
> @Test
> @RunAsClient
> public void testOnServer() {
> Warp.initiate(new Activity() {
> @Override
> public void perform() {
> browser.get(deploymentUrl + "index.xhtml");
> doLoginIfNeeded(browser);
> // this works just fine!
> Assert.assertEquals("INDEX", browser.getTitle());
> }
> })
> .group()
> .observe(request().uri().contains("index.xhtml"))
> .inspect(new Inspection() {
> private static final long serialVersionUID = 1L;
> @ArquillianResource
> private FacesContext facesContext;
> @AfterPhase(RENDER_RESPONSE)
> @SuppressWarnings("unused")
> public void testNavigation() {
> // timeout exception before we reach this
> Assert.assertTrue(facesContext.getViewRoot().getViewId().contains("index.xhtml"));
> }
> })
> .execute();
> }
> {noformat}
> Note: {{doLoginIfNeeded()}} is just a helper method that enters user name and password and hits the login button if the login form popped-up (in case there's no active session) following the initial {{browser.get()}} request in the test.
> Exception:
> {noformat}
> org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint$ServerResponseTimeoutException
> at org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint.awaitResponses(SynchronizationPoint.java:155)
> at org.jboss.arquillian.warp.impl.client.execution.DefaultExecutionSynchronizer.waitForResponse(DefaultExecutionSynchronizer.java:60)
> at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.awaitResponse(WarpExecutionObserver.java:64)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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.execution.DefaultWarpExecutor.awaitServerExecution(DefaultWarpExecutor.java:95)
> at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpExecutor.execute(DefaultWarpExecutor.java:65)
> at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.executeWarp(WarpExecutionObserver.java:45)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> {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, 1 month
[JBoss JIRA] (ARQ-1366) Warp: support server-side testing of web pages that require authentication
by Oliver Bock (JIRA)
[ https://issues.jboss.org/browse/ARQ-1366?page=com.atlassian.jira.plugin.s... ]
Oliver Bock updated ARQ-1366:
-----------------------------
Description:
When web pages are protected by a security-constraint (web.xml) that requires authentication, Warp JSF runs into a {{SynchronizationPoint$ServerResponseTimeoutException}} while executing server-side tests using {{inspect()}}, like the second one below. Standard FORM authentication (via {{j_security_check}}) and Web Driver's {{htmlunit}} browser are used in this case.
More observations:
* Client-side tests work just fine (first test below)
* Disabling the security-constraint (no authentication) allows the server-side test to finish successfully
{noformat}
@Test
@RunAsClient
public void testOnClient() {
browser.get(deploymentUrl + "index.xhtml");
doLoginIfNeeded(browser);
// this works just fine!
Assert.assertEquals("INDEX", browser.getTitle());
}
@Test
@RunAsClient
public void testOnServer() {
Warp.initiate(new Activity() {
@Override
public void perform() {
browser.get(deploymentUrl + "index.xhtml");
doLoginIfNeeded(browser);
// this works just fine!
Assert.assertEquals("INDEX", browser.getTitle());
}
})
.group()
.observe(request().uri().contains("index.xhtml"))
.inspect(new Inspection() {
private static final long serialVersionUID = 1L;
@ArquillianResource
private FacesContext facesContext;
@AfterPhase(RENDER_RESPONSE)
@SuppressWarnings("unused")
public void testNavigation() {
// timeout exception before we reach this
Assert.assertTrue(facesContext.getViewRoot().getViewId().contains("index.xhtml"));
}
})
.execute();
}
{noformat}
Note: {{doLoginIfNeeded()}} is just a helper method that enters user name and password and hits the login button if the login form popped-up (in case there's no active session) following the initial {{browser.get()}} request in the test.
Exception:
{noformat}
org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint$ServerResponseTimeoutException
at org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint.awaitResponses(SynchronizationPoint.java:155)
at org.jboss.arquillian.warp.impl.client.execution.DefaultExecutionSynchronizer.waitForResponse(DefaultExecutionSynchronizer.java:60)
at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.awaitResponse(WarpExecutionObserver.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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.execution.DefaultWarpExecutor.awaitServerExecution(DefaultWarpExecutor.java:95)
at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpExecutor.execute(DefaultWarpExecutor.java:65)
at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.executeWarp(WarpExecutionObserver.java:45)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
{noformat}
was:
When web pages are protected by a security-constraint (web.xml) that requires authentication, Warp JSF runs into a {{SynchronizationPoint$ServerResponseTimeoutException}} while executing server-side tests using {{inspect()}}, like the second one below. Standard FORM authentication (via {{j_security_check}}) and Web Driver's {{htmlunit}} browser are used in this case.
More observations:
* Client-side tests work just fine (first test below)
* Disabling the security-constraint (no authentication) allows the server-side test to finish successfully
{noformat}
@Test
@RunAsClient
public void testOnClient() {
browser.get(deploymentUrl + "index.xhtml");
doLoginIfNeeded(browser);
// this works just fine!
Assert.assertEquals("INDEX", browser.getTitle());
}
@Test
@RunAsClient
public void testOnServer() {
Warp.initiate(new Activity() {
@Override
public void perform() {
browser.get(deploymentUrl + "index.xhtml");
doLoginIfNeeded(browser);
// this works just fine!
Assert.assertEquals("INDEX", browser.getTitle());
}
})
.group()
.observe(request().uri().contains("index.xhtml"))
.inspect(new Inspection() {
private static final long serialVersionUID = 1L;
@ArquillianResource
private FacesContext facesContext;
@AfterPhase(RENDER_RESPONSE)
@SuppressWarnings("unused")
public void testNavigation() {
// timeout exception before we reach this
Assert.assertTrue(facesContext.getViewRoot().getViewId().contains("index.xhtml"));
}
})
.execute();
}
{noformat}
Note: {{doLoginIfNeeded()}} is just a helper method that enters user name and password and hits the login button if the login form popped-up (in case there's no active session) following the initial {{browser.get()}} request in the test.
Exception:
{noformat}
org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint$ServerResponseTimeoutException
at org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint.awaitResponses(SynchronizationPoint.java:155)
at org.jboss.arquillian.warp.impl.client.execution.DefaultExecutionSynchronizer.waitForResponse(DefaultExecutionSynchronizer.java:60)
at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.awaitResponse(WarpExecutionObserver.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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.execution.DefaultWarpExecutor.awaitServerExecution(DefaultWarpExecutor.java:95)
at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpExecutor.execute(DefaultWarpExecutor.java:65)
at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.executeWarp(WarpExecutionObserver.java:45)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
{noformat}
> Warp: support server-side testing of web pages that require authentication
> --------------------------------------------------------------------------
>
> Key: ARQ-1366
> URL: https://issues.jboss.org/browse/ARQ-1366
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha2
> Reporter: Oliver Bock
> Labels: authentication, exception, warp
>
> When web pages are protected by a security-constraint (web.xml) that requires authentication, Warp JSF runs into a {{SynchronizationPoint$ServerResponseTimeoutException}} while executing server-side tests using {{inspect()}}, like the second one below. Standard FORM authentication (via {{j_security_check}}) and Web Driver's {{htmlunit}} browser are used in this case.
> More observations:
> * Client-side tests work just fine (first test below)
> * Disabling the security-constraint (no authentication) allows the server-side test to finish successfully
> {noformat}
> @Test
> @RunAsClient
> public void testOnClient() {
> browser.get(deploymentUrl + "index.xhtml");
> doLoginIfNeeded(browser);
> // this works just fine!
> Assert.assertEquals("INDEX", browser.getTitle());
> }
> @Test
> @RunAsClient
> public void testOnServer() {
> Warp.initiate(new Activity() {
> @Override
> public void perform() {
> browser.get(deploymentUrl + "index.xhtml");
> doLoginIfNeeded(browser);
> // this works just fine!
> Assert.assertEquals("INDEX", browser.getTitle());
> }
> })
> .group()
> .observe(request().uri().contains("index.xhtml"))
> .inspect(new Inspection() {
> private static final long serialVersionUID = 1L;
> @ArquillianResource
> private FacesContext facesContext;
> @AfterPhase(RENDER_RESPONSE)
> @SuppressWarnings("unused")
> public void testNavigation() {
> // timeout exception before we reach this
> Assert.assertTrue(facesContext.getViewRoot().getViewId().contains("index.xhtml"));
> }
> })
> .execute();
> }
> {noformat}
> Note: {{doLoginIfNeeded()}} is just a helper method that enters user name and password and hits the login button if the login form popped-up (in case there's no active session) following the initial {{browser.get()}} request in the test.
> Exception:
> {noformat}
> org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint$ServerResponseTimeoutException
> at org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint.awaitResponses(SynchronizationPoint.java:155)
> at org.jboss.arquillian.warp.impl.client.execution.DefaultExecutionSynchronizer.waitForResponse(DefaultExecutionSynchronizer.java:60)
> at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.awaitResponse(WarpExecutionObserver.java:64)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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.execution.DefaultWarpExecutor.awaitServerExecution(DefaultWarpExecutor.java:95)
> at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpExecutor.execute(DefaultWarpExecutor.java:65)
> at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.executeWarp(WarpExecutionObserver.java:45)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> {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, 1 month
[JBoss JIRA] (ARQ-1366) Warp: support server-side testing of web pages that require authentication
by Oliver Bock (JIRA)
[ https://issues.jboss.org/browse/ARQ-1366?page=com.atlassian.jira.plugin.s... ]
Oliver Bock updated ARQ-1366:
-----------------------------
Description:
When web pages are protected by a security-constraint (web.xml) that requires authentication, Warp JSF runs into a {{SynchronizationPoint$ServerResponseTimeoutException}} while executing server-side tests using {{inspect()}}, like the second one below. Standard FORM authentication (via {{j_security_check}}) and Web Driver's {{htmlunit}} browser are used in this case.
More observations:
* Client-side tests work just fine (first test below)
* Disabling the security-constraint (no authentication) allows the server-side test to finish successfully
{noformat}
@Test
@RunAsClient
public void testOnClient() {
browser.get(deploymentUrl + "index.xhtml");
doLoginIfNeeded(browser);
// this works just fine!
Assert.assertEquals("INDEX", browser.getTitle());
}
@Test
@RunAsClient
public void testOnServer() {
Warp.initiate(new Activity() {
@Override
public void perform() {
browser.get(deploymentUrl + "index.xhtml");
doLoginIfNeeded(browser);
// this works just fine!
Assert.assertEquals("INDEX", browser.getTitle());
}
})
.group()
.observe(request().uri().contains("index.xhtml"))
.inspect(new Inspection() {
private static final long serialVersionUID = 1L;
@ArquillianResource
private FacesContext facesContext;
@AfterPhase(RENDER_RESPONSE)
@SuppressWarnings("unused")
public void testNavigation() {
// timeout exception before we reach this
Assert.assertTrue(facesContext.getViewRoot().getViewId().contains("index.xhtml"));
}
})
.execute();
}
{noformat}
Note: {{doLoginIfNeeded()}} is just a helper method that enters user name and password and hits the login button if the login form popped-up (in case there's no active session) following the initial {{browser.get()}} request in the test.
Exception:
{noformat}
org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint$ServerResponseTimeoutException
at org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint.awaitResponses(SynchronizationPoint.java:155)
at org.jboss.arquillian.warp.impl.client.execution.DefaultExecutionSynchronizer.waitForResponse(DefaultExecutionSynchronizer.java:60)
at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.awaitResponse(WarpExecutionObserver.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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.execution.DefaultWarpExecutor.awaitServerExecution(DefaultWarpExecutor.java:95)
at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpExecutor.execute(DefaultWarpExecutor.java:65)
at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.executeWarp(WarpExecutionObserver.java:45)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
{noformat}
was:
When web pages are protected by a security-constraint (web.xml) that requires authentication, Warp JSF runs into a {{SynchronizationPoint$ServerResponseTimeoutException}} while executing server-side tests using inspect(), like the second one below. Standard FORM authentication (via j_security_check) and Web Driver's "htmlunit" browser are used in this case.
More observations:
* Client-side tests work just fine (first test below)
* Disabling the security-constraint (no authentication) allows the server-side test to finish successfully
{noformat}
@Test
@RunAsClient
public void testOnClient() {
browser.get(deploymentUrl + "index.xhtml");
doLoginIfNeeded(browser);
// this works just fine!
Assert.assertEquals("INDEX", browser.getTitle());
}
@Test
@RunAsClient
public void testOnServer() {
Warp.initiate(new Activity() {
@Override
public void perform() {
browser.get(deploymentUrl + "index.xhtml");
doLoginIfNeeded(browser);
// this works just fine!
Assert.assertEquals("INDEX", browser.getTitle());
}
})
.group()
.observe(request().uri().contains("index.xhtml"))
.inspect(new Inspection() {
private static final long serialVersionUID = 1L;
@ArquillianResource
private FacesContext facesContext;
@AfterPhase(RENDER_RESPONSE)
@SuppressWarnings("unused")
public void testNavigation() {
// timeout exception before we reach this
Assert.assertTrue(facesContext.getViewRoot().getViewId().contains("index.xhtml"));
}
})
.execute();
}
{noformat}
Note: {{doLoginIfNeeded()}} is just a helper method that enters user name and password and hits the login button if the login form popped-up (in case there's no active session) following the initial {{browser.get()}} request in the test.
Exception:
{noformat}
org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint$ServerResponseTimeoutException
at org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint.awaitResponses(SynchronizationPoint.java:155)
at org.jboss.arquillian.warp.impl.client.execution.DefaultExecutionSynchronizer.waitForResponse(DefaultExecutionSynchronizer.java:60)
at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.awaitResponse(WarpExecutionObserver.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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.execution.DefaultWarpExecutor.awaitServerExecution(DefaultWarpExecutor.java:95)
at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpExecutor.execute(DefaultWarpExecutor.java:65)
at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.executeWarp(WarpExecutionObserver.java:45)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
{noformat}
> Warp: support server-side testing of web pages that require authentication
> --------------------------------------------------------------------------
>
> Key: ARQ-1366
> URL: https://issues.jboss.org/browse/ARQ-1366
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha2
> Reporter: Oliver Bock
> Labels: authentication, exception, warp
>
> When web pages are protected by a security-constraint (web.xml) that requires authentication, Warp JSF runs into a {{SynchronizationPoint$ServerResponseTimeoutException}} while executing server-side tests using {{inspect()}}, like the second one below. Standard FORM authentication (via {{j_security_check}}) and Web Driver's {{htmlunit}} browser are used in this case.
> More observations:
> * Client-side tests work just fine (first test below)
> * Disabling the security-constraint (no authentication) allows the server-side test to finish successfully
> {noformat}
> @Test
> @RunAsClient
> public void testOnClient() {
> browser.get(deploymentUrl + "index.xhtml");
> doLoginIfNeeded(browser);
> // this works just fine!
> Assert.assertEquals("INDEX", browser.getTitle());
> }
> @Test
> @RunAsClient
> public void testOnServer() {
> Warp.initiate(new Activity() {
> @Override
> public void perform() {
> browser.get(deploymentUrl + "index.xhtml");
> doLoginIfNeeded(browser);
> // this works just fine!
> Assert.assertEquals("INDEX", browser.getTitle());
> }
> })
> .group()
> .observe(request().uri().contains("index.xhtml"))
> .inspect(new Inspection() {
> private static final long serialVersionUID = 1L;
> @ArquillianResource
> private FacesContext facesContext;
> @AfterPhase(RENDER_RESPONSE)
> @SuppressWarnings("unused")
> public void testNavigation() {
> // timeout exception before we reach this
> Assert.assertTrue(facesContext.getViewRoot().getViewId().contains("index.xhtml"));
> }
> })
> .execute();
> }
> {noformat}
> Note: {{doLoginIfNeeded()}} is just a helper method that enters user name and password and hits the login button if the login form popped-up (in case there's no active session) following the initial {{browser.get()}} request in the test.
> Exception:
> {noformat}
> org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint$ServerResponseTimeoutException
> at org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint.awaitResponses(SynchronizationPoint.java:155)
> at org.jboss.arquillian.warp.impl.client.execution.DefaultExecutionSynchronizer.waitForResponse(DefaultExecutionSynchronizer.java:60)
> at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.awaitResponse(WarpExecutionObserver.java:64)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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.execution.DefaultWarpExecutor.awaitServerExecution(DefaultWarpExecutor.java:95)
> at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpExecutor.execute(DefaultWarpExecutor.java:65)
> at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.executeWarp(WarpExecutionObserver.java:45)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> {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, 1 month
[JBoss JIRA] (ARQ-1366) Warp: support server-side testing of web pages that require authentication
by Oliver Bock (JIRA)
Oliver Bock created ARQ-1366:
--------------------------------
Summary: Warp: support server-side testing of web pages that require authentication
Key: ARQ-1366
URL: https://issues.jboss.org/browse/ARQ-1366
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Warp
Affects Versions: warp_1.0.0.Alpha2
Reporter: Oliver Bock
When web pages are protected by a security-constraint (web.xml) that requires authentication, Warp JSF runs into a {{SynchronizationPoint$ServerResponseTimeoutException}} while executing server-side tests using inspect(), like the second one below. Standard FORM authentication (via j_security_check) and Web Driver's "htmlunit" browser are used in this case.
More observations:
* Client-side tests work just fine (first test below)
* Disabling the security-constraint (no authentication) allows the server-side test to finish successfully
{noformat}
@Test
@RunAsClient
public void testOnClient() {
browser.get(deploymentUrl + "index.xhtml");
doLoginIfNeeded(browser);
// this works just fine!
Assert.assertEquals("INDEX", browser.getTitle());
}
@Test
@RunAsClient
public void testOnServer() {
Warp.initiate(new Activity() {
@Override
public void perform() {
browser.get(deploymentUrl + "index.xhtml");
doLoginIfNeeded(browser);
// this works just fine!
Assert.assertEquals("INDEX", browser.getTitle());
}
})
.group()
.observe(request().uri().contains("index.xhtml"))
.inspect(new Inspection() {
private static final long serialVersionUID = 1L;
@ArquillianResource
private FacesContext facesContext;
@AfterPhase(RENDER_RESPONSE)
@SuppressWarnings("unused")
public void testNavigation() {
// timeout exception before we reach this
Assert.assertTrue(facesContext.getViewRoot().getViewId().contains("index.xhtml"));
}
})
.execute();
}
{noformat}
Note: {{doLoginIfNeeded()}} is just a helper method that enters user name and password and hits the login button if the login form popped-up (in case there's no active session) following the initial {{browser.get()}} request in the test.
Exception:
{noformat}
org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint$ServerResponseTimeoutException
at org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint.awaitResponses(SynchronizationPoint.java:155)
at org.jboss.arquillian.warp.impl.client.execution.DefaultExecutionSynchronizer.waitForResponse(DefaultExecutionSynchronizer.java:60)
at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.awaitResponse(WarpExecutionObserver.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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.execution.DefaultWarpExecutor.awaitServerExecution(DefaultWarpExecutor.java:95)
at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpExecutor.execute(DefaultWarpExecutor.java:65)
at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.executeWarp(WarpExecutionObserver.java:45)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
{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, 1 month
[JBoss JIRA] (ARQGRA-256) Graphene RemoteWebDriver doesn't support augmentation properly
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-256?page=com.atlassian.jira.plugin... ]
Lukáš Fryč reassigned ARQGRA-256:
---------------------------------
Assignee: Lukáš Fryč
> Graphene RemoteWebDriver doesn't support augmentation properly
> --------------------------------------------------------------
>
> Key: ARQGRA-256
> URL: https://issues.jboss.org/browse/ARQGRA-256
> Project: Arquillian Graphene
> Issue Type: Bug
> Components: core
> Affects Versions: 2.0.0.Alpha3
> Environment: Graphene 2.0.0.Alpha3-SNAPSHOT
> Reporter: Ron Šmeral
> Assignee: Lukáš Fryč
> Priority: Critical
>
> When using a remote WebDriver, trying to take a screenshot as described in [WebDriver documentation|http://seleniumhq.org/docs/04_webdriver_advanced.jsp#taking...]:
> {code:java}
> @Drone
> WebDriver driver;
> ...
> WebDriver augmentedDriver = new Augmenter().augment(driver);
> byte[] screenshot = ((TakesScreenshot) augmentedDriver).getScreenshotAs(OutputType.BYTES);
> {code}
> results in the following exeception:
> {noformat}
> Caused by: java.lang.ClassFormatError: Duplicate method name&signature in class file org/openqa/selenium/remote/RemoteWebDriver$$EnhancerCGLIB$$58fd8af5$$EnhancerByCGLIB$$558c2b50
> {noformat}
> If the augmentation is omitted, the {{TakesScreenshot}} interface can't be found:
> {noformat}
> java.lang.ClassCastException: org.openqa.selenium.remote.RemoteWebDriver$$EnhancerCGLIB$$eda133bb cannot be cast to org.openqa.selenium.TakesScreenshot
> {noformat}
> It seems that the CGLib-enhanced {{RemoteWebDriver}} instance contains the methods of capability providers ({{AddTakesScreenshot}}) but doesn't declare that it implements their corresponding interfaces ({{TakesScreenshot}}).
> Note that taking screenshots works without the augmentation when using a non-remote WebDriver. (When using augmentation it throws the _Duplicate method name&signature_ exception).
--
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 month
[JBoss JIRA] (ARQGRA-256) Graphene RemoteWebDriver doesn't support augmentation properly
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-256?page=com.atlassian.jira.plugin... ]
Lukáš Fryč commented on ARQGRA-256:
-----------------------------------
Great, thanks for verification, Ron.
> Graphene RemoteWebDriver doesn't support augmentation properly
> --------------------------------------------------------------
>
> Key: ARQGRA-256
> URL: https://issues.jboss.org/browse/ARQGRA-256
> Project: Arquillian Graphene
> Issue Type: Bug
> Components: core
> Affects Versions: 2.0.0.Alpha3
> Environment: Graphene 2.0.0.Alpha3-SNAPSHOT
> Reporter: Ron Šmeral
> Priority: Critical
>
> When using a remote WebDriver, trying to take a screenshot as described in [WebDriver documentation|http://seleniumhq.org/docs/04_webdriver_advanced.jsp#taking...]:
> {code:java}
> @Drone
> WebDriver driver;
> ...
> WebDriver augmentedDriver = new Augmenter().augment(driver);
> byte[] screenshot = ((TakesScreenshot) augmentedDriver).getScreenshotAs(OutputType.BYTES);
> {code}
> results in the following exeception:
> {noformat}
> Caused by: java.lang.ClassFormatError: Duplicate method name&signature in class file org/openqa/selenium/remote/RemoteWebDriver$$EnhancerCGLIB$$58fd8af5$$EnhancerByCGLIB$$558c2b50
> {noformat}
> If the augmentation is omitted, the {{TakesScreenshot}} interface can't be found:
> {noformat}
> java.lang.ClassCastException: org.openqa.selenium.remote.RemoteWebDriver$$EnhancerCGLIB$$eda133bb cannot be cast to org.openqa.selenium.TakesScreenshot
> {noformat}
> It seems that the CGLib-enhanced {{RemoteWebDriver}} instance contains the methods of capability providers ({{AddTakesScreenshot}}) but doesn't declare that it implements their corresponding interfaces ({{TakesScreenshot}}).
> Note that taking screenshots works without the augmentation when using a non-remote WebDriver. (When using augmentation it throws the _Duplicate method name&signature_ exception).
--
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 month
[JBoss JIRA] (ARQGRA-256) Graphene RemoteWebDriver doesn't support augmentation properly
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-256?page=com.atlassian.jira.plugin... ]
Lukáš Fryč resolved ARQGRA-256.
-------------------------------
Resolution: Rejected
Fixed in Drone - ARQ-1351
> Graphene RemoteWebDriver doesn't support augmentation properly
> --------------------------------------------------------------
>
> Key: ARQGRA-256
> URL: https://issues.jboss.org/browse/ARQGRA-256
> Project: Arquillian Graphene
> Issue Type: Bug
> Components: core
> Affects Versions: 2.0.0.Alpha3
> Environment: Graphene 2.0.0.Alpha3-SNAPSHOT
> Reporter: Ron Šmeral
> Priority: Critical
>
> When using a remote WebDriver, trying to take a screenshot as described in [WebDriver documentation|http://seleniumhq.org/docs/04_webdriver_advanced.jsp#taking...]:
> {code:java}
> @Drone
> WebDriver driver;
> ...
> WebDriver augmentedDriver = new Augmenter().augment(driver);
> byte[] screenshot = ((TakesScreenshot) augmentedDriver).getScreenshotAs(OutputType.BYTES);
> {code}
> results in the following exeception:
> {noformat}
> Caused by: java.lang.ClassFormatError: Duplicate method name&signature in class file org/openqa/selenium/remote/RemoteWebDriver$$EnhancerCGLIB$$58fd8af5$$EnhancerByCGLIB$$558c2b50
> {noformat}
> If the augmentation is omitted, the {{TakesScreenshot}} interface can't be found:
> {noformat}
> java.lang.ClassCastException: org.openqa.selenium.remote.RemoteWebDriver$$EnhancerCGLIB$$eda133bb cannot be cast to org.openqa.selenium.TakesScreenshot
> {noformat}
> It seems that the CGLib-enhanced {{RemoteWebDriver}} instance contains the methods of capability providers ({{AddTakesScreenshot}}) but doesn't declare that it implements their corresponding interfaces ({{TakesScreenshot}}).
> Note that taking screenshots works without the augmentation when using a non-remote WebDriver. (When using augmentation it throws the _Duplicate method name&signature_ exception).
--
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 month
[JBoss JIRA] (ARQGRA-290) testAttributeIsPresent fails on Chrome and PhantomJS
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-290?page=com.atlassian.jira.plugin... ]
Lukáš Fryč commented on ARQGRA-290:
-----------------------------------
Just to clarify - what WebDriver follows is HTML convention which says that {{<x y="y" />}} is equivalent to {{<x y />}}.
For us, the condition is present should state: attribute is non-empty (not-null, not-empty).
> testAttributeIsPresent fails on Chrome and PhantomJS
> ----------------------------------------------------
>
> Key: ARQGRA-290
> URL: https://issues.jboss.org/browse/ARQGRA-290
> Project: Arquillian Graphene
> Issue Type: Bug
> Reporter: Lukáš Fryč
> Assignee: Juraj Húska
> Priority: Critical
> Fix For: 2.0.0.Alpha4
>
>
> Test cases:
> {code}
> LocatorAttributeTest.testAttributeIsPresent
> LocatorAttributeTest.testAttributeIsPresentDirectly
> WebElementAttributeTest.testAttributeIsPresent
> WebElementAttributeTest.testAttributeIsPresentDirectly
> ConditionsTestCase.testAttributeIsPresent
> {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
11 years, 1 month
[JBoss JIRA] (ARQ-1365) Warp: CommandEventBus doesn't support (port) redirects
by Oliver Bock (JIRA)
[ https://issues.jboss.org/browse/ARQ-1365?page=com.atlassian.jira.plugin.s... ]
Oliver Bock updated ARQ-1365:
-----------------------------
Description:
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}
was:
I've configured JBosss AS 7 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}
> 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
> Labels: warp
>
> 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, 1 month