December 2013 - arquillian-issues

[JBoss JIRA] (ARQ-1593) Missing Desired Capabilities for PhantomJS

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1593?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1593: ----------------------------- Fix Version/s: drone_1.2.1.Final > Missing Desired Capabilities for PhantomJS > ------------------------------------------ > > Key: ARQ-1593 > URL: https://issues.jboss.org/browse/ARQ-1593 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Final > Reporter: Karel Piwko > Priority: Critical > Fix For: drone_1.2.1.Final > > > *When*: > I use phantomjs as a remote driver. > *Then*: > I expect everything will work, given that remote server is aware of phantomjs binary location. > *Current Behavior*: > PhantomJS does not have capabilities set, which leads to remote server itself choosing browser capabilities itself, returning a different browser in reusing is enabled. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1584) Remove duplication from Droidium modules

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1584?page=com.atlassian.jira.plugin.s... ] Karel Piwko reopened ARQ-1584: ------------------------------ As for depchains, this is not how it should be done. *arquillian-droidium-native* is still depchain, because user needs to specify <type>pom</type. Now it is more confusing then previously. We should stick with following rule: dependency of packaging jar -> no depchain in name dependency of type pom -> always depchain in name Depchain are generally used to make dependency specifications simpler - that is to couple a set of independent components together within a single dependency. My suggestion was, as is hardly a screnario when end user will depend on native-spi and native-api when *using* Droidium, it would make more sense to have: native-impl renamed to arquillian-droidium-native, being of type jar and that would be what end user will import into their projects. > Remove duplication from Droidium modules > ---------------------------------------- > > Key: ARQ-1584 > URL: https://issues.jboss.org/browse/ARQ-1584 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > Currently, a lot of modules are not necessary and could be removed altogether to make structure simpler > For instance, build per each native, container, web might be moved into a single build module, some depchain could be removed - depchain make more sense if there is a sense in including only a part of extension, which is not valid for native, web - it's all-or-nothing. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1594) InitializationParameter does not check for non-serializable fields

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1594: -------------------------------- Summary: InitializationParameter does not check for non-serializable fields Key: ARQ-1594 URL: https://issues.jboss.org/browse/ARQ-1594 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Karel Piwko *When*: I mark browser as remoteReusable. *Then*: I expect that it will work no matter what configuration is specified in arquillian.xml configuration. *Current behavior*: When storing initialization parameter, it tries to serialize all capabilities. If any of them is non-serializable, like loggingPrefs, Drone refuses to store the session leading to the fact that a new session is created for each browser request. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1593) Missing Desired Capabilities for PhantomJS

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1593: -------------------------------- Summary: Missing Desired Capabilities for PhantomJS Key: ARQ-1593 URL: https://issues.jboss.org/browse/ARQ-1593 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.2.0.Final Reporter: Karel Piwko Priority: Critical *When*: I use phantomjs as a remote driver. *Then*: I expect everything will work, given that remote server is aware of phantomjs binary location. *Current Behavior*: PhantomJS does not have capabilities set, which leads to remote server itself choosing browser capabilities itself, returning a different browser in reusing is enabled. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1592) Warp: Wrong command bus uri for multiple context roots

by Tilmann Kuhn (JIRA)

[ https://issues.jboss.org/browse/ARQ-1592?page=com.atlassian.jira.plugin.s... ] Tilmann Kuhn edited comment on ARQ-1592 at 12/2/13 12:18 PM: ------------------------------------------------------------- I guess the code to determine the correct URI must already be in there somewhere because test interaction using the servlet protocol works correctly. was (Author: tilm4nn): I guess the code to determine the correct URI must already be in there somewhere because Drone/Graphene get the URI right for their injections and page-navigations. > Warp: Wrong command bus uri for multiple context roots > ------------------------------------------------------ > > Key: ARQ-1592 > URL: https://issues.jboss.org/browse/ARQ-1592 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Environment: JBoss EAP 6.0.1 > Reporter: Tilmann Kuhn > > When using warp with an EAR containing multiple WARs (only one marked as testable in the deployment) that have different context roots (e.g. "/foo" and "/bar") then local part of URI for the command event bus is determined as "/" in method CommandBusOnClient.locateCommandEventBusUri. Subsequent calls to the bus fail with HTTP 404 which is unhandled in CommandBusOnClient.execute and thus lead to > java.lang.NullPointerException > at org.jboss.arquillian.warp.impl.client.commandBus.CommandBusOnClient.executeRemotely(CommandBusOnClient.java:163) > at org.jboss.arquillian.warp.impl.client.commandBus.CommandServiceOnClient.execute(CommandServiceOnClient.java:38) > at org.jboss.arquillian.warp.impl.client.commandBus.RemoteSuiteLifecyclePropagation.sendAfter(RemoteSuiteLifecyclePropagation.java:61) > ... -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1592) Warp: Wrong command bus uri for multiple context roots

by Tilmann Kuhn (JIRA)

[ https://issues.jboss.org/browse/ARQ-1592?page=com.atlassian.jira.plugin.s... ] Tilmann Kuhn commented on ARQ-1592: ----------------------------------- I guess the code to determine the correct URI must already be in there somewhere because Drone/Graphene get the URI right for their injections and page-navigations. > Warp: Wrong command bus uri for multiple context roots > ------------------------------------------------------ > > Key: ARQ-1592 > URL: https://issues.jboss.org/browse/ARQ-1592 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Environment: JBoss EAP 6.0.1 > Reporter: Tilmann Kuhn > > When using warp with an EAR containing multiple WARs (only one marked as testable in the deployment) that have different context roots (e.g. "/foo" and "/bar") then local part of URI for the command event bus is determined as "/" in method CommandBusOnClient.locateCommandEventBusUri. Subsequent calls to the bus fail with HTTP 404 which is unhandled in CommandBusOnClient.execute and thus lead to > java.lang.NullPointerException > at org.jboss.arquillian.warp.impl.client.commandBus.CommandBusOnClient.executeRemotely(CommandBusOnClient.java:163) > at org.jboss.arquillian.warp.impl.client.commandBus.CommandServiceOnClient.execute(CommandServiceOnClient.java:38) > at org.jboss.arquillian.warp.impl.client.commandBus.RemoteSuiteLifecyclePropagation.sendAfter(RemoteSuiteLifecyclePropagation.java:61) > ... -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1592) Warp: Wrong command bus uri for multiple context roots

by Tilmann Kuhn (JIRA)

Tilmann Kuhn created ARQ-1592: --------------------------------- Summary: Warp: Wrong command bus uri for multiple context roots Key: ARQ-1592 URL: https://issues.jboss.org/browse/ARQ-1592 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Warp Affects Versions: warp_1.0.0.Alpha5 Environment: JBoss EAP 6.0.1 Reporter: Tilmann Kuhn When using warp with an EAR containing multiple WARs (only one marked as testable in the deployment) that have different context roots (e.g. "/foo" and "/bar") then local part of URI for the command event bus is determined as "/" in method CommandBusOnClient.locateCommandEventBusUri. Subsequent calls to the bus fail with HTTP 404 which is unhandled in CommandBusOnClient.execute and thus lead to java.lang.NullPointerException at org.jboss.arquillian.warp.impl.client.commandBus.CommandBusOnClient.executeRemotely(CommandBusOnClient.java:163) at org.jboss.arquillian.warp.impl.client.commandBus.CommandServiceOnClient.execute(CommandServiceOnClient.java:38) at org.jboss.arquillian.warp.impl.client.commandBus.RemoteSuiteLifecyclePropagation.sendAfter(RemoteSuiteLifecyclePropagation.java:61) ... -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1591) Add activity to activity mapper when it does not start with a dot and it is not FQDN

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1591?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic resolved ARQ-1591. ------------------------------------ Fix Version/s: 1.0.0.Alpha3 Resolution: Done Cudos goes to [~aemmanou]! > Add activity to activity mapper when it does not start with a dot and it is not FQDN > ------------------------------------------------------------------------------------ > > Key: ARQ-1591 > URL: https://issues.jboss.org/browse/ARQ-1591 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: 1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: 1.0.0.Alpha3 > > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1591) Add activity to activity mapper when it does not start with a dot and it is not FQDN

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1591?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic reassigned ARQ-1591: -------------------------------------- Assignee: Stefan Miklosovic > Add activity to activity mapper when it does not start with a dot and it is not FQDN > ------------------------------------------------------------------------------------ > > Key: ARQ-1591 > URL: https://issues.jboss.org/browse/ARQ-1591 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: 1.0.0.Alpha2 > 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1591) Add activity to activity mapper when it does not start with a dot and it is not FQDN

by Stefan Miklosovic (JIRA)

Stefan Miklosovic created ARQ-1591: -------------------------------------- Summary: Add activity to activity mapper when it does not start with a dot and it is not FQDN Key: ARQ-1591 URL: https://issues.jboss.org/browse/ARQ-1591 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: 1.0.0.Alpha2 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

10 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues December 2013