From jira-events at lists.jboss.org Mon Dec 2 04:01:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Mon, 2 Dec 2013 04:01:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1589) Update jboss-parent In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1589: -------------------------------- Summary: Update jboss-parent Key: ARQ-1589 URL: https://issues.jboss.org/browse/ARQ-1589 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.2.0.Final Reporter: Karel Piwko Update Arquillian Drone to latest jboss-parent. At the same time, remove compiler plugin config, as this is already a part of parent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Dec 2 05:17:07 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 2 Dec 2013 05:17:07 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1590) Update JBoss parent to the latest one In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1590: -------------------------------------- Summary: Update JBoss parent to the latest one Key: ARQ-1590 URL: https://issues.jboss.org/browse/ARQ-1590 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: 1.0.0.Alpha2 Reporter: Stefan Miklosovic Bump jboss-parent from version 11 to version 12. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Dec 2 05:21:05 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 2 Dec 2013 05:21:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1590) Update JBoss parent to the latest one In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1590. ------------------------------------ Resolution: Done > Update JBoss parent to the latest one > ------------------------------------- > > Key: ARQ-1590 > URL: https://issues.jboss.org/browse/ARQ-1590 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: 1.0.0.Alpha2 > Reporter: Stefan Miklosovic > > Bump jboss-parent from version 11 to version 12. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Dec 2 05:21:05 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 2 Dec 2013 05:21:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1590) Update JBoss parent to the latest one In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1590: ----------------------------------- Fix Version/s: droidium_1.0.0.Alpha3 > Update JBoss parent to the latest one > ------------------------------------- > > Key: ARQ-1590 > URL: https://issues.jboss.org/browse/ARQ-1590 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: 1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > Bump jboss-parent from version 11 to version 12. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Dec 2 05:36:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 2 Dec 2013 05:36:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-413) @InFrame incompatible with GrapheneElement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-413: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/93 > @InFrame incompatible with GrapheneElement > ------------------------------------------ > > Key: ARQGRA-413 > URL: https://issues.jboss.org/browse/ARQGRA-413 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Jan Dosoudil > Assignee: Juraj H?ska > > {code:title=Exception} > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.graphene.enricher.ReflectionHelper$3.run(ReflectionHelper.java:214) > at org.jboss.arquillian.graphene.enricher.ReflectionHelper$3.run(ReflectionHelper.java:208) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.arquillian.graphene.enricher.ReflectionHelper.getFieldsWithAnnotation(ReflectionHelper.java:208) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrichFurtherSpecificAnnotation(InFrameEnricher.java:101) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrichRecursivelyGrapheneProxyInstances(InFrameEnricher.java:93) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.registerInFrameInterceptor(InFrameEnricher.java:86) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrichFurtherSpecificAnnotation(InFrameEnricher.java:107) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrichRecursivelyGrapheneProxyInstances(InFrameEnricher.java:93) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.registerInFrameInterceptor(InFrameEnricher.java:86) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrichFurtherSpecificAnnotation(InFrameEnricher.java:107) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrichRecursivelyGrapheneProxyInstances(InFrameEnricher.java:93) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.registerInFrameInterceptor(InFrameEnricher.java:86) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrich(InFrameEnricher.java:61) > ... 68 more > {code} > {code} > @RunWith(Arquillian.class) > @WarpTest > @RunAsClient > public class Test { > @FindBy(id="x") > @InFrame(nameOrId="y") > private GrapheneElement el; > .... > } > {code} > InFrameEnricher declares DO_NOT_ENRICH_FURTHER Set which is used to ignore some interfaces but doesn't ignore descendants - ignores WebElement but not GrapheneElement. > ReflectionHelper doesn't handle Interfaces well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Dec 2 05:42:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 2 Dec 2013 05:42:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-413) @InFrame incompatible with GrapheneElement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927780#comment-12927780 ] Juraj H?ska commented on ARQGRA-413: ------------------------------------ Thank you [~dosoudilj] for very good analysis! Lukas, I have sent a pull request to resolve this issue. Please see also the PR comments. > @InFrame incompatible with GrapheneElement > ------------------------------------------ > > Key: ARQGRA-413 > URL: https://issues.jboss.org/browse/ARQGRA-413 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Jan Dosoudil > Assignee: Juraj H?ska > > {code:title=Exception} > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.graphene.enricher.ReflectionHelper$3.run(ReflectionHelper.java:214) > at org.jboss.arquillian.graphene.enricher.ReflectionHelper$3.run(ReflectionHelper.java:208) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.arquillian.graphene.enricher.ReflectionHelper.getFieldsWithAnnotation(ReflectionHelper.java:208) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrichFurtherSpecificAnnotation(InFrameEnricher.java:101) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrichRecursivelyGrapheneProxyInstances(InFrameEnricher.java:93) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.registerInFrameInterceptor(InFrameEnricher.java:86) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrichFurtherSpecificAnnotation(InFrameEnricher.java:107) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrichRecursivelyGrapheneProxyInstances(InFrameEnricher.java:93) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.registerInFrameInterceptor(InFrameEnricher.java:86) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrichFurtherSpecificAnnotation(InFrameEnricher.java:107) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrichRecursivelyGrapheneProxyInstances(InFrameEnricher.java:93) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.registerInFrameInterceptor(InFrameEnricher.java:86) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrich(InFrameEnricher.java:61) > ... 68 more > {code} > {code} > @RunWith(Arquillian.class) > @WarpTest > @RunAsClient > public class Test { > @FindBy(id="x") > @InFrame(nameOrId="y") > private GrapheneElement el; > .... > } > {code} > InFrameEnricher declares DO_NOT_ENRICH_FURTHER Set which is used to ignore some interfaces but doesn't ignore descendants - ignores WebElement but not GrapheneElement. > ReflectionHelper doesn't handle Interfaces well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Dec 2 08:32:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Dec 2013 08:32:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-413) @InFrame incompatible with GrapheneElement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-413: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 2.0.1.Final Resolution: Done > @InFrame incompatible with GrapheneElement > ------------------------------------------ > > Key: ARQGRA-413 > URL: https://issues.jboss.org/browse/ARQGRA-413 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Jan Dosoudil > Assignee: Juraj H?ska > Fix For: 2.0.1.Final > > > {code:title=Exception} > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.graphene.enricher.ReflectionHelper$3.run(ReflectionHelper.java:214) > at org.jboss.arquillian.graphene.enricher.ReflectionHelper$3.run(ReflectionHelper.java:208) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.arquillian.graphene.enricher.ReflectionHelper.getFieldsWithAnnotation(ReflectionHelper.java:208) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrichFurtherSpecificAnnotation(InFrameEnricher.java:101) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrichRecursivelyGrapheneProxyInstances(InFrameEnricher.java:93) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.registerInFrameInterceptor(InFrameEnricher.java:86) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrichFurtherSpecificAnnotation(InFrameEnricher.java:107) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrichRecursivelyGrapheneProxyInstances(InFrameEnricher.java:93) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.registerInFrameInterceptor(InFrameEnricher.java:86) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrichFurtherSpecificAnnotation(InFrameEnricher.java:107) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrichRecursivelyGrapheneProxyInstances(InFrameEnricher.java:93) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.registerInFrameInterceptor(InFrameEnricher.java:86) > at org.jboss.arquillian.graphene.enricher.InFrameEnricher.enrich(InFrameEnricher.java:61) > ... 68 more > {code} > {code} > @RunWith(Arquillian.class) > @WarpTest > @RunAsClient > public class Test { > @FindBy(id="x") > @InFrame(nameOrId="y") > private GrapheneElement el; > .... > } > {code} > InFrameEnricher declares DO_NOT_ENRICH_FURTHER Set which is used to ignore some interfaces but doesn't ignore descendants - ignores WebElement but not GrapheneElement. > ReflectionHelper doesn't handle Interfaces well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Dec 2 11:18:06 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 2 Dec 2013 11:18:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1591) Add activity to activity mapper when it does not start with a dot and it is not FQDN In-Reply-To: References: Message-ID: 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 From jira-events at lists.jboss.org Mon Dec 2 11:43:05 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 2 Dec 2013 11:43:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1591) Add activity to activity mapper when it does not start with a dot and it is not FQDN In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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 From jira-events at lists.jboss.org Mon Dec 2 11:45:06 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 2 Dec 2013 11:45:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1591) Add activity to activity mapper when it does not start with a dot and it is not FQDN In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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 From jira-events at lists.jboss.org Mon Dec 2 12:15:06 2013 From: jira-events at lists.jboss.org (Tilmann Kuhn (JIRA)) Date: Mon, 2 Dec 2013 12:15:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1592) Warp: Wrong command bus uri for multiple context roots In-Reply-To: References: Message-ID: 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 From jira-events at lists.jboss.org Mon Dec 2 12:17:05 2013 From: jira-events at lists.jboss.org (Tilmann Kuhn (JIRA)) Date: Mon, 2 Dec 2013 12:17:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1592) Warp: Wrong command bus uri for multiple context roots In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927948#comment-12927948 ] 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 From jira-events at lists.jboss.org Mon Dec 2 12:19:06 2013 From: jira-events at lists.jboss.org (Tilmann Kuhn (JIRA)) Date: Mon, 2 Dec 2013 12:19:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1592) Warp: Wrong command bus uri for multiple context roots In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927948#comment-12927948 ] 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 From jira-events at lists.jboss.org Tue Dec 3 03:46:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 3 Dec 2013 03:46:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1593) Missing Desired Capabilities for PhantomJS In-Reply-To: References: Message-ID: 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 From jira-events at lists.jboss.org Tue Dec 3 03:49:05 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 3 Dec 2013 03:49:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1594) InitializationParameter does not check for non-serializable fields In-Reply-To: References: Message-ID: 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 From jira-events at lists.jboss.org Tue Dec 3 03:57:05 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 3 Dec 2013 03:57:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1584) Remove duplication from Droidium modules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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 pom 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 From jira-events at lists.jboss.org Tue Dec 3 04:28:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 3 Dec 2013 04:28:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1594) InitializationParameter does not check for non-serializable fields In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1594: ----------------------------- Fix Version/s: drone_1.2.1.Final > 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 > Fix For: drone_1.2.1.Final > > > *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 From jira-events at lists.jboss.org Tue Dec 3 04:28:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 3 Dec 2013 04:28:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1593) Missing Desired Capabilities for PhantomJS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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 From jira-events at lists.jboss.org Tue Dec 3 04:28:07 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 3 Dec 2013 04:28:07 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-951) Drone: Setup Matrix jobs for browser support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-951: ---------------------------- Fix Version/s: drone_1.2.1.Final (was: drone_1.3.next) > Drone: Setup Matrix jobs for browser support > -------------------------------------------- > > Key: ARQ-951 > URL: https://issues.jboss.org/browse/ARQ-951 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Luk?? Fry? > Fix For: drone_1.2.1.Final > > Original Estimate: 2 days > Remaining Estimate: 2 days > > We should know that Drone supports all the listed browsers with all the features like: > * instantiation > * destruction > * reusability > on following browsers: > * HtmlUnit > * Firefox > * Chrome > * Internet Explorer > * Opera > * Android > * IPhone > This will make sure we are able to base our tests on @Drone in QA Lab and verify the high-level functionality like reusability works for all the browsers. > ---- > The same needs to be addressed in scope of Graphene, see references: > ARQGRA-59 > support for configurating arquillian.xml during runtime for matrix browser compability jobs > ARQGRA-76 > Setup matrix jobs for browser support > ---- > The problem with this approach is that we need to filter what we actually want to test. > I have identified following types of tetsts in Graphene suite: > * able to run in any continuous-integration > ** unit tests > ** arquillian core integration tests > ** ftests able to run with htmlunit > * running only in specific environment > ** browser-specific > We need to modify {{arquillian.xml}} in order to select appropriate browser for given run. > Also, unit-tests shouldn't be run as part of ftests, since it is redundant. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 04:34:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 3 Dec 2013 04:34:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1594) InitializationParameter does not check for non-serializable fields In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928110#comment-12928110 ] Karel Piwko commented on ARQ-1594: ---------------------------------- Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/4ac0e8f4cb7e230767d67524fa406ccb06d074cc > 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 > Fix For: drone_1.2.1.Final > > > *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 From jira-events at lists.jboss.org Tue Dec 3 04:34:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 3 Dec 2013 04:34:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1594) InitializationParameter does not check for non-serializable fields In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1594. ------------------------------ Assignee: Karel Piwko Resolution: Done > 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 > Assignee: Karel Piwko > Fix For: drone_1.2.1.Final > > > *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 From jira-events at lists.jboss.org Tue Dec 3 04:34:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 3 Dec 2013 04:34:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1593) Missing Desired Capabilities for PhantomJS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1593. ------------------------------ Assignee: Karel Piwko Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/feb327603635076a56d26ae2f2ff5a4b765b144b > 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 > Assignee: 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 From jira-events at lists.jboss.org Tue Dec 3 04:34:07 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 3 Dec 2013 04:34:07 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-951) Drone: Setup Matrix jobs for browser support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-951. ----------------------------- Assignee: Karel Piwko Resolution: Done Testsuite was rewritten to run against a single browser https://github.com/arquillian/arquillian-extension-drone/commit/44f16d1be875acb6542aacd0699e83d5786db29b Public matrix job is not yet created. > Drone: Setup Matrix jobs for browser support > -------------------------------------------- > > Key: ARQ-951 > URL: https://issues.jboss.org/browse/ARQ-951 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Luk?? Fry? > Assignee: Karel Piwko > Fix For: drone_1.2.1.Final > > Original Estimate: 2 days > Remaining Estimate: 2 days > > We should know that Drone supports all the listed browsers with all the features like: > * instantiation > * destruction > * reusability > on following browsers: > * HtmlUnit > * Firefox > * Chrome > * Internet Explorer > * Opera > * Android > * IPhone > This will make sure we are able to base our tests on @Drone in QA Lab and verify the high-level functionality like reusability works for all the browsers. > ---- > The same needs to be addressed in scope of Graphene, see references: > ARQGRA-59 > support for configurating arquillian.xml during runtime for matrix browser compability jobs > ARQGRA-76 > Setup matrix jobs for browser support > ---- > The problem with this approach is that we need to filter what we actually want to test. > I have identified following types of tetsts in Graphene suite: > * able to run in any continuous-integration > ** unit tests > ** arquillian core integration tests > ** ftests able to run with htmlunit > * running only in specific environment > ** browser-specific > We need to modify {{arquillian.xml}} in order to select appropriate browser for given run. > Also, unit-tests shouldn't be run as part of ftests, since it is redundant. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 04:36:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 3 Dec 2013 04:36:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1574) Update Selenium to 2.37.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1574: ----------------------------- Fix Version/s: drone_1.2.1.Final (was: drone_1.3.next) > Update Selenium to 2.37.1 > ------------------------- > > Key: ARQ-1574 > URL: https://issues.jboss.org/browse/ARQ-1574 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Final > Reporter: Karel Piwko > Fix For: drone_1.2.1.Final > > > Update Selenium to latest, 2.37.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 04:36:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 3 Dec 2013 04:36:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1537) Support for Safari browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1537: ----------------------------- Fix Version/s: drone_1.2.1.Final (was: drone_1.3.next) > Support for Safari browser > -------------------------- > > Key: ARQ-1537 > URL: https://issues.jboss.org/browse/ARQ-1537 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.CR1 > Environment: Mac OS X > Reporter: Sona Jamborova > Assignee: Jiri Locker > Fix For: drone_1.2.1.Final > > > I found out that SafariDriver is a part of selenium server from version 2.30 (our version is 2.33). I try to use "safari" for property "browserCapabilities" in arquillian.xml, but I get an exception: > java.lang.IllegalStateException: Unable to initialize WebDriver instance. Please specify a valid browserCapabilities instead of safari. Available options are: firefox, android, htmlUnit, chrome, opera, phantonsjs, iphone, internetExplorer. > Can you add support for Safari? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 04:36:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 3 Dec 2013 04:36:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1575) Fix Eclipse/JBDS missing console configuration warning In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1575: ----------------------------- Fix Version/s: drone_1.2.1.Final (was: drone_1.3.next) > Fix Eclipse/JBDS missing console configuration warning > ------------------------------------------------------ > > Key: ARQ-1575 > URL: https://issues.jboss.org/browse/ARQ-1575 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Minor > Fix For: drone_1.2.1.Final > > > Both webdriver and selenium modules produce following warning when imported into Eclipse/JBDS. > ```Console configuration "*" does not exist. ``` -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 04:36:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 3 Dec 2013 04:36:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1543) Unexpected ISE "Unexpected callable present in Drone Context, should be already instantiated at this moment." In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1543: ----------------------------- Fix Version/s: drone_1.2.1.Final (was: drone_1.3.next) > Unexpected ISE "Unexpected callable present in Drone Context, should be already instantiated at this moment." > ------------------------------------------------------------------------------------------------------------- > > Key: ARQ-1543 > URL: https://issues.jboss.org/browse/ARQ-1543 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Final > Reporter: Julien Viet > Assignee: Karel Piwko > Fix For: drone_1.2.1.Final > > > Happening when two Drone WebDriver are injected in the tested class: > java.lang.IllegalStateException: Unexpected callable present in Drone Context, should be already instantiated at this moment. > at org.jboss.arquillian.drone.impl.InstanceOrCallableInstanceImpl.asInstance(InstanceOrCallableInstanceImpl.java:57) > at org.jboss.arquillian.drone.webdriver.augmentation.AugmentingEnhancer.canEnhance(AugmentingEnhancer.java:75) > at org.jboss.arquillian.drone.impl.DroneEnhancer.deenhanceDrone(DroneEnhancer.java:112) > 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.drone.impl.DroneDestructor.destroyClassScopedDrone(DroneDestructor.java:83) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at 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.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87) > at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > 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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 04:42:05 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 3 Dec 2013 04:42:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1595) Update Arquillian Core to 1.1.2.Final In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1595: -------------------------------- Summary: Update Arquillian Core to 1.1.2.Final Key: ARQ-1595 URL: https://issues.jboss.org/browse/ARQ-1595 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.2.0.Final Reporter: Karel Piwko Update to latest Arquillian Core version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 04:48:05 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 3 Dec 2013 04:48:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1595) Update Arquillian Core to 1.1.2.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1595. ------------------------------ Assignee: Karel Piwko Fix Version/s: drone_1.2.1.Final Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/defdbd8e69bfee868cbc2422e56a65582731d0f4 > Update Arquillian Core to 1.1.2.Final > ------------------------------------- > > Key: ARQ-1595 > URL: https://issues.jboss.org/browse/ARQ-1595 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.1.Final > > > Update to latest Arquillian Core version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 04:50:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 3 Dec 2013 04:50:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1589) Update jboss-parent In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1589. ------------------------------ Assignee: Karel Piwko Fix Version/s: drone_1.2.1.Final Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/7ca333af53ccf0c6974bcd34f202a0b63708dd4c. At the same time, remove custom compiler plugin configuration. > Update jboss-parent > ------------------- > > Key: ARQ-1589 > URL: https://issues.jboss.org/browse/ARQ-1589 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.1.Final > > > Update Arquillian Drone to latest jboss-parent. At the same time, remove compiler plugin config, as this is already a part of parent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 04:50:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 3 Dec 2013 04:50:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1574) Update Selenium to 2.37.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reassigned ARQ-1574: -------------------------------- Assignee: Karel Piwko > Update Selenium to 2.37.1 > ------------------------- > > Key: ARQ-1574 > URL: https://issues.jboss.org/browse/ARQ-1574 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.1.Final > > > Update Selenium to latest, 2.37.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 06:39:06 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 06:39:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1584) Remove duplication from Droidium modules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1584. ------------------------------------ Resolution: Done done as suggested, we dropped additional two modules > 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 From jira-events at lists.jboss.org Tue Dec 3 10:27:06 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:27:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1584) Remove duplication from Droidium modules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1584. ---------------------------------- > 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 From jira-events at lists.jboss.org Tue Dec 3 10:27:06 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:27:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1591) Add activity to activity mapper when it does not start with a dot and it is not FQDN In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1591. ---------------------------------- > 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 From jira-events at lists.jboss.org Tue Dec 3 10:27:06 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:27:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1590) Update JBoss parent to the latest one In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1590: ----------------------------------- Affects Version/s: droidium_1.0.0.Alpha2 (was: 1.0.0.Alpha2) > Update JBoss parent to the latest one > ------------------------------------- > > Key: ARQ-1590 > URL: https://issues.jboss.org/browse/ARQ-1590 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > Bump jboss-parent from version 11 to version 12. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 10:27:06 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:27:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1590) Update JBoss parent to the latest one In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1590. ---------------------------------- > Update JBoss parent to the latest one > ------------------------------------- > > Key: ARQ-1590 > URL: https://issues.jboss.org/browse/ARQ-1590 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > Bump jboss-parent from version 11 to version 12. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 10:27:07 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:27:07 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1587) Droidium has to fail when there is already started emulator on the same ports In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1587: ----------------------------------- Affects Version/s: droidium_1.0.0.Alpha2 (was: 1.0.0.Alpha2) > Droidium has to fail when there is already started emulator on the same ports > ----------------------------------------------------------------------------- > > Key: ARQ-1587 > URL: https://issues.jboss.org/browse/ARQ-1587 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Fix For: 1.0.0.Alpha3 > > > Given: > Already started emulator on some console and adb port. > When: > I specify in arquillian.xml that I want to start emulator on such port which matches the one which is used by already started emulator. > Then: > Droidium fails to start it and provides a reason why. > Use case: > I have already started emulator and I want to start another one and with explicitly specified ports from configuration. These ports are already used by the first emulator. Droidium has to fail. There has to be some free port checking utility. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 10:27:07 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:27:07 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1587) Droidium has to fail when there is already started emulator on the same ports In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1587. ---------------------------------- > Droidium has to fail when there is already started emulator on the same ports > ----------------------------------------------------------------------------- > > Key: ARQ-1587 > URL: https://issues.jboss.org/browse/ARQ-1587 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > Given: > Already started emulator on some console and adb port. > When: > I specify in arquillian.xml that I want to start emulator on such port which matches the one which is used by already started emulator. > Then: > Droidium fails to start it and provides a reason why. > Use case: > I have already started emulator and I want to start another one and with explicitly specified ports from configuration. These ports are already used by the first emulator. Droidium has to fail. There has to be some free port checking utility. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 10:27:07 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:27:07 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1587) Droidium has to fail when there is already started emulator on the same ports In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1587: ----------------------------------- Fix Version/s: droidium_1.0.0.Alpha3 (was: 1.0.0.Alpha3) > Droidium has to fail when there is already started emulator on the same ports > ----------------------------------------------------------------------------- > > Key: ARQ-1587 > URL: https://issues.jboss.org/browse/ARQ-1587 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > Given: > Already started emulator on some console and adb port. > When: > I specify in arquillian.xml that I want to start emulator on such port which matches the one which is used by already started emulator. > Then: > Droidium fails to start it and provides a reason why. > Use case: > I have already started emulator and I want to start another one and with explicitly specified ports from configuration. These ports are already used by the first emulator. Droidium has to fail. There has to be some free port checking utility. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 10:29:06 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:29:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1580) Provide better AVD logging information In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1580. ---------------------------------- > Provide better AVD logging information > -------------------------------------- > > Key: ARQ-1580 > URL: https://issues.jboss.org/browse/ARQ-1580 > 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 > > > In case there is an AVD match, provide a debug output for it, such as > {code} > Name: random-avd > Path: /home/kpiwko/.android/avd/random-avd.avd > Target: Android 4.2.2 (API level 17) > ABI: x86 > Skin: 480x800 > {code} > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 10:29:06 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:29:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1577) Do not start Android container when there is not android browser in webdriver extension specified In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1577. ---------------------------------- > Do not start Android container when there is not android browser in webdriver extension specified > ------------------------------------------------------------------------------------------------- > > Key: ARQ-1577 > URL: https://issues.jboss.org/browse/ARQ-1577 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > This is related to ARQ-1509 but it is Droidium specific. > When I do have both Android and JBoss adapter classes on class path and when I want to test on regular desktop browser only (meaning browser property in webdriver extension configuration is not set to "android"), there is no need to start Android container so it should not be started. > The solution is to listen to [DroidiumExtensionConfigured|https://github.com/arquillian/arquillian-droidium/blob/master/droidium-container/arquillian-droidium-container-spi/src/main/java/org/arquillian/droidium/container/spi/event/DroidiumExtensionConfigured.java] event. It is fired when some Droidium extension is fired. Extensions are configured before containers are started so that is the right time to remove container def from ContainerRegistry so that Android container will not be started afterwards. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 10:29:06 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:29:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1567) Explain validation errors in more depth In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1567. ---------------------------------- > Explain validation errors in more depth > --------------------------------------- > > Key: ARQ-1567 > URL: https://issues.jboss.org/browse/ARQ-1567 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > In many cases, it is not sufficient to provide a user just with stack trace when something goes wrong, for example, from this one: > {code} > java.lang.IllegalStateException: Directory to check against readability is null object or empty string. > at org.arquillian.droidium.container.configuration.Validate.notNullOrEmpty(Validate.java:98) > at org.arquillian.droidium.container.configuration.Validate.isReadableDirectory(Validate.java:147) > at org.arquillian.droidium.container.configuration.AndroidSDK.(AndroidSDK.java:189) > at org.arquillian.droidium.container.AndroidDeployableContainer.setup(AndroidDeployableContainer.java:153) > {code} > It basically says that user does not have specified JAVA_HOME but he can not know that without looking into sources which is *totally* not desired. > Review all crucial configuration properties and its setters / getters and be sure that when it fails user knows whats going on. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 10:29:06 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:29:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1571) Remove API 10 from default platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1571: ----------------------------------- Fix Version/s: droidium_1.0.0.Alpha3 > Remove API 10 from default platform > ----------------------------------- > > Key: ARQ-1571 > URL: https://issues.jboss.org/browse/ARQ-1571 > 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 > > > Related to fix ARQ-1568, it is no longer necessary to check for API 10 presence. Default behavior could simply be to find out newest (highest) API level if no level is specified to create the AVD. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 10:29:06 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:29:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1571) Remove API 10 from default platform In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1571. ---------------------------------- > Remove API 10 from default platform > ----------------------------------- > > Key: ARQ-1571 > URL: https://issues.jboss.org/browse/ARQ-1571 > 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 > > > Related to fix ARQ-1568, it is no longer necessary to check for API 10 presence. Default behavior could simply be to find out newest (highest) API level if no level is specified to create the AVD. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 10:29:06 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:29:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1547) Improve the parsing of activities from AndroidManifest.xml of AUT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1547. ---------------------------------- > Improve the parsing of activities from AndroidManifest.xml of AUT > ----------------------------------------------------------------- > > Key: ARQ-1547 > URL: https://issues.jboss.org/browse/ARQ-1547 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > Current parsing of activities from AndroidManifest.xml during activity scanning is not sufficient. There are cases when parser gets lost like package contains "activity" string but parser relies on the appearance of that string somewhere else which ends up with IndexOutOfBoundException. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 10:29:06 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:29:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1533) Uninstall packages from device before test when they are already installed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1533. ---------------------------------- > Uninstall packages from device before test when they are already installed > -------------------------------------------------------------------------- > > Key: ARQ-1533 > URL: https://issues.jboss.org/browse/ARQ-1533 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > Given: Android device prior to test. > When: I run test with packages to be installed which are already in Android device. > I expect: old packages will be uninstalled and packages from current test run will be installed > This situation can happen if something really horrible happens and whole test fails in the middle so packages are not uninstalled (Selendroid server and ordinary apks as well). When I run tests for the second time, I want that packages will be removed and installed once again to get them fresh. > Example: We could use different rebuilt Selendroid server which has the same package name but it is rebuilt for another application. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 10:31:05 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:31:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1568) Droidium fails if emulator is about to start and there is not API level 10 and apiLevel is not in config In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1568. ---------------------------------- > Droidium fails if emulator is about to start and there is not API level 10 and apiLevel is not in config > -------------------------------------------------------------------------------------------------------- > > Key: ARQ-1568 > URL: https://issues.jboss.org/browse/ARQ-1568 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > Given: > 1. Already existing emulator with API level != 10 available > 2. Emulator is not started prior to tests > 3. API level 10 is not installed locally on developers machine > 4. apiLevel configuration option is not set in arquillian.xml > When: > I want to start emulator with the environment above > Then: > Droidium does not fail. > The reason why it fails is that in case AVD of such name in avdName property does not exist, Droidium tries to create AVD dynamically and it is deleted after tests. Default API level is 10 so when apiLevel is not specified, it attempts to create emulator with that API level, but it might not be present on the system - so it fails. > The workaround could be to filter all available API level and choose the lowest one as the default one and not API level 10 which is set statically. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 10:31:05 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:31:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1570) Provide better parsing of ABI in connection with API level for Droidium In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1570. ---------------------------------- > Provide better parsing of ABI in connection with API level for Droidium > ----------------------------------------------------------------------- > > Key: ARQ-1570 > URL: https://issues.jboss.org/browse/ARQ-1570 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > Right now, there is not any tracking between available API levels and their respective ABI present in the system. > For example, when some AVD is not present in the system, Droidium tries to create it. While creating, it uses API level and when there exists ABI in configuration, it creates it with that ABI level. > For every API level present in the system, there should be information as which system images for that particular API level can be used while creating of AVD takes place. > Because of speed, default ABI will be choosen as x86 for some particular API level of users choice when he has not specified it explicitly. It is needed to filter available ABIs for some API level dynamically upon AVD creation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 10:31:06 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:31:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1582) Honor ANDROID_SDK_HOME, deprecate generatedAvdPath In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1582. ---------------------------------- > Honor ANDROID_SDK_HOME, deprecate generatedAvdPath > -------------------------------------------------- > > Key: ARQ-1582 > URL: https://issues.jboss.org/browse/ARQ-1582 > 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 > Priority: Critical > Fix For: droidium_1.0.0.Alpha3 > > > ANDROID_SDK_HOME represents a top level directory that is used to store metadata of AVDs. By default, this directory equals $HOME. > However, various plugins and tools - such as Jenkins Android Plugin, allow to change ANDROID_SDK_HOME to better isolate jobs. > Droidium should be able to: > * pass androidSdkHome in arquillian.xml with default = user.home > * honor this directoryand create generated AVDs there - this will limit write access to single location - e.g. pattern would be ${androidSdkHome}/.android/${avdName}.avd > Then, *generatedAvdPath* can be dropped altogether - reasoning is that Android UI does not allow that neither and it does not make much sense to split metadata and AVD itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 10:31:06 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:31:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1583) Emulator does not figure out process had died In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1583. ---------------------------------- > Emulator does not figure out process had died > --------------------------------------------- > > Key: ARQ-1583 > URL: https://issues.jboss.org/browse/ARQ-1583 > 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: Karel Piwko > Priority: Critical > Fix For: droidium_1.0.0.Alpha3 > > > *When*: > I let Droidium start emulator. > *Given*: > Emulator command fails, for instance when DISPLAY is not set. > *Then*: > Droidium waits up to emulator start time, then fails. > *Expected*: > Droidium will figure out command had failed - emulator actually outputs *SDL init failure, reason is: No available video device* and let user know what happened wrong. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 10:31:06 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:31:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1509) Arquillian Droidium Multiple Container does not work correctly when used standalone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1509. ---------------------------------- > Arquillian Droidium Multiple Container does not work correctly when used standalone > ----------------------------------------------------------------------------------- > > Key: ARQ-1509 > URL: https://issues.jboss.org/browse/ARQ-1509 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha1 > Reporter: Karel Piwko > Priority: Critical > Fix For: droidium_1.0.0.Alpha3 > > > Supposing you want to use web based testing with Droidium. > In such case, you have a pretty specific configuration in arquillian.xml, as you need to enable multiple containers. > However, if you don't want to run Android - you are for instance testing with Firefox, so no Android container is needed, then you need to create a separate in order to do that. > Otherwise, MultipleContainer Extension will let Arquillian create container def for each in the group, leading to attempt to create JBoss AS - or whatever is you web container - using Android container configuration. > This will obvisously fail, for instance with > {code} > org.jboss.arquillian.container.spi.ConfigurationException: jbossHome 'null' must exist > at org.jboss.arquillian.container.spi.client.deployment.Validate.configurationDirectoryExists(Validate.java:139) > {code} > So, if you put only multicontainer extension jar into , behavior is broken. If you don't put anything there, you already have tailed arq.xml to be used with multiple container. If you indeed put Android container there, it is started even if it would actually never be used due to fact you asked for Firefox Browser. > This represents a serious usability issues, hence marked as Critical. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 10:31:06 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:31:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1585) Droidium does not figure out AVD is broken In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1585. ---------------------------------- > Droidium does not figure out AVD is broken > ------------------------------------------ > > Key: ARQ-1585 > URL: https://issues.jboss.org/browse/ARQ-1585 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Priority: Blocker > Fix For: droidium_1.0.0.Alpha3 > > > Current AVD name parsing is broken, it won't figure out that AVD is actually broken - for instance metadata point to AVD images that are no longer on filesystem. Even in such situations Drodium starts emulator, which is deemed to fail and Droidium waits up to all timeout to fail the test. > Ideally, Droidium should handle such situation and figure out that metadata of broken device should be deleted if user requested that AVD by name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 10:35:08 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:35:08 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1588) Release Arquillian Droidium 1.0.0.Alpha3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1588: -------------------------------------- Assignee: Stefan Miklosovic > Release Arquillian Droidium 1.0.0.Alpha3 > ---------------------------------------- > > Key: ARQ-1588 > URL: https://issues.jboss.org/browse/ARQ-1588 > Project: Arquillian > Issue Type: Release > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 10:35:08 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 3 Dec 2013 10:35:08 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1588) Release Arquillian Droidium 1.0.0.Alpha3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1588. ------------------------------------ Resolution: Done > Release Arquillian Droidium 1.0.0.Alpha3 > ---------------------------------------- > > Key: ARQ-1588 > URL: https://issues.jboss.org/browse/ARQ-1588 > Project: Arquillian > Issue Type: Release > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 11:01:07 2013 From: jira-events at lists.jboss.org (Tilmann Kuhn (JIRA)) Date: Tue, 3 Dec 2013 11:01:07 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1561) Warp proxy tries to rewrite binary files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928232#comment-12928232 ] Tilmann Kuhn commented on ARQ-1561: ----------------------------------- I can confirm that the proxy corrupts png and jpg files. Without @WarpTest the images are trensferred correctly. Since my tests depend on the images being available to the client (simulating cicks on coordinates on them) this does not work at the moment. > Warp proxy tries to rewrite binary files > ---------------------------------------- > > Key: ARQ-1561 > URL: https://issues.jboss.org/browse/ARQ-1561 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha5 > Reporter: Jan Dosoudil > Priority: Critical > Fix For: warp_1.0.0.Alpha6 > > Attachments: empty.png, empty2.png > > > It's related to ARQ-1552 - rewrite calls new String(byte[]) on response byte[] which may fail on binary files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 3 11:01:07 2013 From: jira-events at lists.jboss.org (Tilmann Kuhn (JIRA)) Date: Tue, 3 Dec 2013 11:01:07 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1561) Warp proxy tries to rewrite binary files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928232#comment-12928232 ] Tilmann Kuhn edited comment on ARQ-1561 at 12/3/13 11:00 AM: ------------------------------------------------------------- I can confirm that the proxy corrupts png and jpg files. Without @WarpTest the images are transferred correctly. Since my tests depend on the images being available to the client (simulating cicks on coordinates on them) this does not work at the moment. was (Author: tilm4nn): I can confirm that the proxy corrupts png and jpg files. Without @WarpTest the images are trensferred correctly. Since my tests depend on the images being available to the client (simulating cicks on coordinates on them) this does not work at the moment. > Warp proxy tries to rewrite binary files > ---------------------------------------- > > Key: ARQ-1561 > URL: https://issues.jboss.org/browse/ARQ-1561 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha5 > Reporter: Jan Dosoudil > Priority: Critical > Fix For: warp_1.0.0.Alpha6 > > Attachments: empty.png, empty2.png > > > It's related to ARQ-1552 - rewrite calls new String(byte[]) on response byte[] which may fail on binary files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 03:41:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 03:41:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1594) InitializationParameter does not check for non-serializable fields In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1594. ---------------------------- > 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 > Assignee: Karel Piwko > Fix For: drone_1.2.1.Final > > > *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 From jira-events at lists.jboss.org Wed Dec 4 03:41:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 03:41:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1589) Update jboss-parent In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1589. ---------------------------- > Update jboss-parent > ------------------- > > Key: ARQ-1589 > URL: https://issues.jboss.org/browse/ARQ-1589 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.1.Final > > > Update Arquillian Drone to latest jboss-parent. At the same time, remove compiler plugin config, as this is already a part of parent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 03:41:07 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 03:41:07 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1574) Update Selenium to 2.37.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1574. ---------------------------- > Update Selenium to 2.37.1 > ------------------------- > > Key: ARQ-1574 > URL: https://issues.jboss.org/browse/ARQ-1574 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.1.Final > > > Update Selenium to latest, 2.37.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 03:41:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 03:41:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1543) Unexpected ISE "Unexpected callable present in Drone Context, should be already instantiated at this moment." In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1543. ---------------------------- > Unexpected ISE "Unexpected callable present in Drone Context, should be already instantiated at this moment." > ------------------------------------------------------------------------------------------------------------- > > Key: ARQ-1543 > URL: https://issues.jboss.org/browse/ARQ-1543 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Final > Reporter: Julien Viet > Assignee: Karel Piwko > Fix For: drone_1.2.1.Final > > > Happening when two Drone WebDriver are injected in the tested class: > java.lang.IllegalStateException: Unexpected callable present in Drone Context, should be already instantiated at this moment. > at org.jboss.arquillian.drone.impl.InstanceOrCallableInstanceImpl.asInstance(InstanceOrCallableInstanceImpl.java:57) > at org.jboss.arquillian.drone.webdriver.augmentation.AugmentingEnhancer.canEnhance(AugmentingEnhancer.java:75) > at org.jboss.arquillian.drone.impl.DroneEnhancer.deenhanceDrone(DroneEnhancer.java:112) > 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.drone.impl.DroneDestructor.destroyClassScopedDrone(DroneDestructor.java:83) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at 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.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87) > at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > 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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 03:41:07 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 03:41:07 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1575) Fix Eclipse/JBDS missing console configuration warning In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1575. ---------------------------- > Fix Eclipse/JBDS missing console configuration warning > ------------------------------------------------------ > > Key: ARQ-1575 > URL: https://issues.jboss.org/browse/ARQ-1575 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Minor > Fix For: drone_1.2.1.Final > > > Both webdriver and selenium modules produce following warning when imported into Eclipse/JBDS. > ```Console configuration "*" does not exist. ``` -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 03:41:07 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 03:41:07 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1595) Update Arquillian Core to 1.1.2.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1595. ---------------------------- > Update Arquillian Core to 1.1.2.Final > ------------------------------------- > > Key: ARQ-1595 > URL: https://issues.jboss.org/browse/ARQ-1595 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.1.Final > > > Update to latest Arquillian Core version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 03:41:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 03:41:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1593) Missing Desired Capabilities for PhantomJS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1593. ---------------------------- > 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 > Assignee: 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 From jira-events at lists.jboss.org Wed Dec 4 03:41:08 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 03:41:08 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-951) Drone: Setup Matrix jobs for browser support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-951. --------------------------- > Drone: Setup Matrix jobs for browser support > -------------------------------------------- > > Key: ARQ-951 > URL: https://issues.jboss.org/browse/ARQ-951 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Luk?? Fry? > Assignee: Karel Piwko > Fix For: drone_1.2.1.Final > > Original Estimate: 2 days > Remaining Estimate: 2 days > > We should know that Drone supports all the listed browsers with all the features like: > * instantiation > * destruction > * reusability > on following browsers: > * HtmlUnit > * Firefox > * Chrome > * Internet Explorer > * Opera > * Android > * IPhone > This will make sure we are able to base our tests on @Drone in QA Lab and verify the high-level functionality like reusability works for all the browsers. > ---- > The same needs to be addressed in scope of Graphene, see references: > ARQGRA-59 > support for configurating arquillian.xml during runtime for matrix browser compability jobs > ARQGRA-76 > Setup matrix jobs for browser support > ---- > The problem with this approach is that we need to filter what we actually want to test. > I have identified following types of tetsts in Graphene suite: > * able to run in any continuous-integration > ** unit tests > ** arquillian core integration tests > ** ftests able to run with htmlunit > * running only in specific environment > ** browser-specific > We need to modify {{arquillian.xml}} in order to select appropriate browser for given run. > Also, unit-tests shouldn't be run as part of ftests, since it is redundant. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 03:41:07 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 03:41:07 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1537) Support for Safari browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1537. ---------------------------- > Support for Safari browser > -------------------------- > > Key: ARQ-1537 > URL: https://issues.jboss.org/browse/ARQ-1537 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.CR1 > Environment: Mac OS X > Reporter: Sona Jamborova > Assignee: Jiri Locker > Fix For: drone_1.2.1.Final > > > I found out that SafariDriver is a part of selenium server from version 2.30 (our version is 2.33). I try to use "safari" for property "browserCapabilities" in arquillian.xml, but I get an exception: > java.lang.IllegalStateException: Unable to initialize WebDriver instance. Please specify a valid browserCapabilities instead of safari. Available options are: firefox, android, htmlUnit, chrome, opera, phantonsjs, iphone, internetExplorer. > Can you add support for Safari? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 03:53:05 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 03:53:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1588) Release Arquillian Droidium 1.0.0.Alpha3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1588: ----------------------------- Fix Version/s: droidium_1.0.0.Alpha3 > Release Arquillian Droidium 1.0.0.Alpha3 > ---------------------------------------- > > Key: ARQ-1588 > URL: https://issues.jboss.org/browse/ARQ-1588 > Project: Arquillian > Issue Type: Release > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_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 From jira-events at lists.jboss.org Wed Dec 4 03:53:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 03:53:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1588) Release Arquillian Droidium 1.0.0.Alpha3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1588. ---------------------------- > Release Arquillian Droidium 1.0.0.Alpha3 > ---------------------------------------- > > Key: ARQ-1588 > URL: https://issues.jboss.org/browse/ARQ-1588 > Project: Arquillian > Issue Type: Release > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_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 From jira-events at lists.jboss.org Wed Dec 4 04:16:08 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 04:16:08 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1585) Droidium does not figure out AVD is broken In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reopened ARQ-1585: ------------------------------ Assignee: Stefan Miklosovic Reopened to change asignee > Droidium does not figure out AVD is broken > ------------------------------------------ > > Key: ARQ-1585 > URL: https://issues.jboss.org/browse/ARQ-1585 > 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 > Priority: Blocker > Fix For: droidium_1.0.0.Alpha3 > > > Current AVD name parsing is broken, it won't figure out that AVD is actually broken - for instance metadata point to AVD images that are no longer on filesystem. Even in such situations Drodium starts emulator, which is deemed to fail and Droidium waits up to all timeout to fail the test. > Ideally, Droidium should handle such situation and figure out that metadata of broken device should be deleted if user requested that AVD by name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 04:16:08 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 04:16:08 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1585) Droidium does not figure out AVD is broken In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1585. ---------------------------- Resolution: Done > Droidium does not figure out AVD is broken > ------------------------------------------ > > Key: ARQ-1585 > URL: https://issues.jboss.org/browse/ARQ-1585 > 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 > Priority: Blocker > Fix For: droidium_1.0.0.Alpha3 > > > Current AVD name parsing is broken, it won't figure out that AVD is actually broken - for instance metadata point to AVD images that are no longer on filesystem. Even in such situations Drodium starts emulator, which is deemed to fail and Droidium waits up to all timeout to fail the test. > Ideally, Droidium should handle such situation and figure out that metadata of broken device should be deleted if user requested that AVD by name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 04:16:08 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 04:16:08 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1509) Arquillian Droidium Multiple Container does not work correctly when used standalone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reopened ARQ-1509: ------------------------------ Assignee: Stefan Miklosovic Reopened to change asignee > Arquillian Droidium Multiple Container does not work correctly when used standalone > ----------------------------------------------------------------------------------- > > Key: ARQ-1509 > URL: https://issues.jboss.org/browse/ARQ-1509 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Priority: Critical > Fix For: droidium_1.0.0.Alpha3 > > > Supposing you want to use web based testing with Droidium. > In such case, you have a pretty specific configuration in arquillian.xml, as you need to enable multiple containers. > However, if you don't want to run Android - you are for instance testing with Firefox, so no Android container is needed, then you need to create a separate in order to do that. > Otherwise, MultipleContainer Extension will let Arquillian create container def for each in the group, leading to attempt to create JBoss AS - or whatever is you web container - using Android container configuration. > This will obvisously fail, for instance with > {code} > org.jboss.arquillian.container.spi.ConfigurationException: jbossHome 'null' must exist > at org.jboss.arquillian.container.spi.client.deployment.Validate.configurationDirectoryExists(Validate.java:139) > {code} > So, if you put only multicontainer extension jar into , behavior is broken. If you don't put anything there, you already have tailed arq.xml to be used with multiple container. If you indeed put Android container there, it is started even if it would actually never be used due to fact you asked for Firefox Browser. > This represents a serious usability issues, hence marked as Critical. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 04:16:08 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 04:16:08 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1509) Arquillian Droidium Multiple Container does not work correctly when used standalone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1509. ---------------------------- Resolution: Done > Arquillian Droidium Multiple Container does not work correctly when used standalone > ----------------------------------------------------------------------------------- > > Key: ARQ-1509 > URL: https://issues.jboss.org/browse/ARQ-1509 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Priority: Critical > Fix For: droidium_1.0.0.Alpha3 > > > Supposing you want to use web based testing with Droidium. > In such case, you have a pretty specific configuration in arquillian.xml, as you need to enable multiple containers. > However, if you don't want to run Android - you are for instance testing with Firefox, so no Android container is needed, then you need to create a separate in order to do that. > Otherwise, MultipleContainer Extension will let Arquillian create container def for each in the group, leading to attempt to create JBoss AS - or whatever is you web container - using Android container configuration. > This will obvisously fail, for instance with > {code} > org.jboss.arquillian.container.spi.ConfigurationException: jbossHome 'null' must exist > at org.jboss.arquillian.container.spi.client.deployment.Validate.configurationDirectoryExists(Validate.java:139) > {code} > So, if you put only multicontainer extension jar into , behavior is broken. If you don't put anything there, you already have tailed arq.xml to be used with multiple container. If you indeed put Android container there, it is started even if it would actually never be used due to fact you asked for Firefox Browser. > This represents a serious usability issues, hence marked as Critical. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 04:16:08 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 04:16:08 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1567) Explain validation errors in more depth In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reopened ARQ-1567: ------------------------------ Reopened to change asignee > Explain validation errors in more depth > --------------------------------------- > > Key: ARQ-1567 > URL: https://issues.jboss.org/browse/ARQ-1567 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > In many cases, it is not sufficient to provide a user just with stack trace when something goes wrong, for example, from this one: > {code} > java.lang.IllegalStateException: Directory to check against readability is null object or empty string. > at org.arquillian.droidium.container.configuration.Validate.notNullOrEmpty(Validate.java:98) > at org.arquillian.droidium.container.configuration.Validate.isReadableDirectory(Validate.java:147) > at org.arquillian.droidium.container.configuration.AndroidSDK.(AndroidSDK.java:189) > at org.arquillian.droidium.container.AndroidDeployableContainer.setup(AndroidDeployableContainer.java:153) > {code} > It basically says that user does not have specified JAVA_HOME but he can not know that without looking into sources which is *totally* not desired. > Review all crucial configuration properties and its setters / getters and be sure that when it fails user knows whats going on. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 04:18:05 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 04:18:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1567) Explain validation errors in more depth In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1567. ---------------------------- Assignee: Stefan Miklosovic Resolution: Done > Explain validation errors in more depth > --------------------------------------- > > Key: ARQ-1567 > URL: https://issues.jboss.org/browse/ARQ-1567 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > In many cases, it is not sufficient to provide a user just with stack trace when something goes wrong, for example, from this one: > {code} > java.lang.IllegalStateException: Directory to check against readability is null object or empty string. > at org.arquillian.droidium.container.configuration.Validate.notNullOrEmpty(Validate.java:98) > at org.arquillian.droidium.container.configuration.Validate.isReadableDirectory(Validate.java:147) > at org.arquillian.droidium.container.configuration.AndroidSDK.(AndroidSDK.java:189) > at org.arquillian.droidium.container.AndroidDeployableContainer.setup(AndroidDeployableContainer.java:153) > {code} > It basically says that user does not have specified JAVA_HOME but he can not know that without looking into sources which is *totally* not desired. > Review all crucial configuration properties and its setters / getters and be sure that when it fails user knows whats going on. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 04:18:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 04:18:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1587) Droidium has to fail when there is already started emulator on the same ports In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1587. ---------------------------- Resolution: Done > Droidium has to fail when there is already started emulator on the same ports > ----------------------------------------------------------------------------- > > Key: ARQ-1587 > URL: https://issues.jboss.org/browse/ARQ-1587 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > Given: > Already started emulator on some console and adb port. > When: > I specify in arquillian.xml that I want to start emulator on such port which matches the one which is used by already started emulator. > Then: > Droidium fails to start it and provides a reason why. > Use case: > I have already started emulator and I want to start another one and with explicitly specified ports from configuration. These ports are already used by the first emulator. Droidium has to fail. There has to be some free port checking utility. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 04:18:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 04:18:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1590) Update JBoss parent to the latest one In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reopened ARQ-1590: ------------------------------ Assignee: Stefan Miklosovic Reopened to change asignee > Update JBoss parent to the latest one > ------------------------------------- > > Key: ARQ-1590 > URL: https://issues.jboss.org/browse/ARQ-1590 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > Bump jboss-parent from version 11 to version 12. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 04:18:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 04:18:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1587) Droidium has to fail when there is already started emulator on the same ports In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reopened ARQ-1587: ------------------------------ Assignee: Stefan Miklosovic Reopened to change asignee > Droidium has to fail when there is already started emulator on the same ports > ----------------------------------------------------------------------------- > > Key: ARQ-1587 > URL: https://issues.jboss.org/browse/ARQ-1587 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > Given: > Already started emulator on some console and adb port. > When: > I specify in arquillian.xml that I want to start emulator on such port which matches the one which is used by already started emulator. > Then: > Droidium fails to start it and provides a reason why. > Use case: > I have already started emulator and I want to start another one and with explicitly specified ports from configuration. These ports are already used by the first emulator. Droidium has to fail. There has to be some free port checking utility. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 04:22:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Wed, 4 Dec 2013 04:22:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1590) Update JBoss parent to the latest one In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1590. ---------------------------- Resolution: Done > Update JBoss parent to the latest one > ------------------------------------- > > Key: ARQ-1590 > URL: https://issues.jboss.org/browse/ARQ-1590 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha3 > > > Bump jboss-parent from version 11 to version 12. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 04:56:06 2013 From: jira-events at lists.jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 4 Dec 2013 04:56:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1596) GlassFish Remote/Managed force JAX-RS 1.0 In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1596: ---------------------------------- Summary: GlassFish Remote/Managed force JAX-RS 1.0 Key: ARQ-1596 URL: https://issues.jboss.org/browse/ARQ-1596 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: GlassFish Containers Affects Versions: glassfish_1.0.0.CR4 Reporter: Aslak Knutsen Priority: Critical The GlassFish Remote and Managed containers use Jersey 1.x to communicate with the Admin REST API. * Jersey changed package from com.sun to org.glassfish between 1.x and 2.x * Jersey core bundles the JAX-RS 1.0 apis This case some issues when you want to test JAX-RS 2.0 features on the client side using GlassFish 4. You can't exclude the Jersey libs exposed and replace them with Jersey 2.0 because the package names changed.. And you can't really get JAX-RS 2.0 on ClassPath because Jersey 1.0 bundles the 1.0 APIs.. We need to replace the communication with the Admin API with something that can't interfere with the Container / User classpath. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 18:29:07 2013 From: jira-events at lists.jboss.org (Bartosz Majsak (JIRA)) Date: Wed, 4 Dec 2013 18:29:07 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1597) Provide APE-BOM for easier dependency setup In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-1597: ----------------------------------- Summary: Provide APE-BOM for easier dependency setup Key: ARQ-1597 URL: https://issues.jboss.org/browse/ARQ-1597 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Persistence Reporter: Bartosz Majsak Assignee: Bartosz Majsak BOM will help importing all required deps for APE in the controlled, yet simple manner. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Dec 4 18:29:07 2013 From: jira-events at lists.jboss.org (Bartosz Majsak (JIRA)) Date: Wed, 4 Dec 2013 18:29:07 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1597) Provide APE-BOM for easier dependency setup In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1597: -------------------------------- Fix Version/s: persistence_1.0.0.next > Provide APE-BOM for easier dependency setup > ------------------------------------------- > > Key: ARQ-1597 > URL: https://issues.jboss.org/browse/ARQ-1597 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > BOM will help importing all required deps for APE in the controlled, yet simple manner. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Dec 5 03:55:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 03:55:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1598) Warp on WildFly: CDI fails to inject into inspection that is inner static class In-Reply-To: References: Message-ID: Luk?? Fry? created ARQ-1598: ------------------------------- Summary: Warp on WildFly: CDI fails to inject into inspection that is inner static class Key: ARQ-1598 URL: https://issues.jboss.org/browse/ARQ-1598 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Warp Affects Versions: warp_1.0.0.Alpha5 Environment: WildFly 8.0.0.Beta2-SNAPSHOT Reporter: Luk?? Fry? When class is inner static class: {code} public class MyTest { @Test public void test1() { Warp....inspect(new MyInspection()); Warp....inspect(new MyInspection()); // fails } @Test public void test2() { Warp....inspect(new MyInspection()); // fails } } {code} the first inspection pass, but all subsequent inspections fails in the scope of one deployment. ---- I think that is because the class is already loaded in classloader and its scanning might be cached by Weld. ---- A issue was originally reproduced and reported here: https://issues.jboss.org/browse/RF-13417 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Dec 5 03:57:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 03:57:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1598) Warp on WildFly: CDI fails to inject into inspection that is inner static class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1598: ---------------------------- Description: When class is inner static class: {code} public class MyTest { @Test public void test1() { Warp....inspect(new MyInspection()); Warp....inspect(new MyInspection()); // fails } @Test public void test2() { Warp....inspect(new MyInspection()); // fails } public static class MyInspection() { } } {code} the first inspection pass, but all subsequent inspections fails in the scope of one deployment. ---- I think that is because the class is already loaded in classloader and its scanning might be cached by Weld. ---- A issue was originally reproduced and reported here: https://issues.jboss.org/browse/RF-13417 was: When class is inner static class: {code} public class MyTest { @Test public void test1() { Warp....inspect(new MyInspection()); Warp....inspect(new MyInspection()); // fails } @Test public void test2() { Warp....inspect(new MyInspection()); // fails } } {code} the first inspection pass, but all subsequent inspections fails in the scope of one deployment. ---- I think that is because the class is already loaded in classloader and its scanning might be cached by Weld. ---- A issue was originally reproduced and reported here: https://issues.jboss.org/browse/RF-13417 > Warp on WildFly: CDI fails to inject into inspection that is inner static class > ------------------------------------------------------------------------------- > > Key: ARQ-1598 > URL: https://issues.jboss.org/browse/ARQ-1598 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Environment: WildFly 8.0.0.Beta2-SNAPSHOT > Reporter: Luk?? Fry? > > When class is inner static class: > {code} > public class MyTest { > @Test > public void test1() { > Warp....inspect(new MyInspection()); > Warp....inspect(new MyInspection()); // fails > } > @Test > public void test2() { > Warp....inspect(new MyInspection()); // fails > } > public static class MyInspection() { > } > } > {code} > the first inspection pass, but all subsequent inspections fails in the scope of one deployment. > ---- > I think that is because the class is already loaded in classloader and its scanning might be cached by Weld. > ---- > A issue was originally reproduced and reported here: > https://issues.jboss.org/browse/RF-13417 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Dec 5 03:59:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 03:59:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1598) Warp on WildFly: CDI fails to inject into inspection that is inner static class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928804#comment-12928804 ] Luk?? Fry? commented on ARQ-1598: --------------------------------- Workaround is using top-level classes. ---- We need to check whether this fails also with anonymous inner classes. If it's not the case, then we can simply disallow to process static inner classes (they should be packaged with deployment): https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Alpha5/impl/src/main/java/org/jboss/arquillian/warp/impl/shared/RequestPayload.java#L105 > Warp on WildFly: CDI fails to inject into inspection that is inner static class > ------------------------------------------------------------------------------- > > Key: ARQ-1598 > URL: https://issues.jboss.org/browse/ARQ-1598 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Environment: WildFly 8.0.0.Beta2-SNAPSHOT > Reporter: Luk?? Fry? > > When class is inner static class: > {code} > public class MyTest { > @Test > public void test1() { > Warp....inspect(new MyInspection()); > Warp....inspect(new MyInspection()); // fails > } > @Test > public void test2() { > Warp....inspect(new MyInspection()); // fails > } > public static class MyInspection() { > } > } > {code} > the first inspection pass, but all subsequent inspections fails in the scope of one deployment. > ---- > I think that is because the class is already loaded in classloader and its scanning might be cached by Weld. > ---- > A issue was originally reproduced and reported here: > https://issues.jboss.org/browse/RF-13417 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Dec 5 03:59:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 03:59:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1598) Warp on WildFly: CDI fails to inject into inspection that is inner static class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1598: ---------------------------- Fix Version/s: warp_1.0.0.Alpha6 > Warp on WildFly: CDI fails to inject into inspection that is inner static class > ------------------------------------------------------------------------------- > > Key: ARQ-1598 > URL: https://issues.jboss.org/browse/ARQ-1598 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Environment: WildFly 8.0.0.Beta2-SNAPSHOT > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Alpha6 > > > When class is inner static class: > {code} > public class MyTest { > @Test > public void test1() { > Warp....inspect(new MyInspection()); > Warp....inspect(new MyInspection()); // fails > } > @Test > public void test2() { > Warp....inspect(new MyInspection()); // fails > } > public static class MyInspection() { > } > } > {code} > the first inspection pass, but all subsequent inspections fails in the scope of one deployment. > ---- > I think that is because the class is already loaded in classloader and its scanning might be cached by Weld. > ---- > A issue was originally reproduced and reported here: > https://issues.jboss.org/browse/RF-13417 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Dec 5 04:01:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 04:01:07 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1598) Warp on WildFly: CDI fails to inject into inspection that is inner static class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1598: ---------------------------- Description: When class is inner static class: {code} public class MyTest { @Test public void test1() { Warp....inspect(new MyInspection()); Warp....inspect(new MyInspection()); // fails } @Test public void test2() { Warp....inspect(new MyInspection()); // fails } public static class MyInspection() { } } {code} the first inspection pass, but all subsequent inspections fails in the scope of one deployment. ---- I think that is because the class is already loaded in classloader and its scanning might be cached by Weld. ---- A issue was originally reproduced and reported here: https://issues.jboss.org/browse/RF-13417 ---- Exception and cause: {code} java.lang.RuntimeException: Could not inject members at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValue {code} {code} Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) at java.lang.reflect.Field.set(Field.java:741) at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) {code} was: When class is inner static class: {code} public class MyTest { @Test public void test1() { Warp....inspect(new MyInspection()); Warp....inspect(new MyInspection()); // fails } @Test public void test2() { Warp....inspect(new MyInspection()); // fails } public static class MyInspection() { } } {code} the first inspection pass, but all subsequent inspections fails in the scope of one deployment. ---- I think that is because the class is already loaded in classloader and its scanning might be cached by Weld. ---- A issue was originally reproduced and reported here: https://issues.jboss.org/browse/RF-13417 > Warp on WildFly: CDI fails to inject into inspection that is inner static class > ------------------------------------------------------------------------------- > > Key: ARQ-1598 > URL: https://issues.jboss.org/browse/ARQ-1598 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Environment: WildFly 8.0.0.Beta2-SNAPSHOT > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Alpha6 > > > When class is inner static class: > {code} > public class MyTest { > @Test > public void test1() { > Warp....inspect(new MyInspection()); > Warp....inspect(new MyInspection()); // fails > } > @Test > public void test2() { > Warp....inspect(new MyInspection()); // fails > } > public static class MyInspection() { > } > } > {code} > the first inspection pass, but all subsequent inspections fails in the scope of one deployment. > ---- > I think that is because the class is already loaded in classloader and its scanning might be cached by Weld. > ---- > A issue was originally reproduced and reported here: > https://issues.jboss.org/browse/RF-13417 > ---- > Exception and cause: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValue > {code} > {code} > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Dec 5 04:03:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 04:03:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1598) Warp on WildFly: CDI fails to inject into inspection that is inner static class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1598: ---------------------------- Git Pull Request: https://github.com/lfryc/arquillian-extension-warp/tree/ARQ-1598-warp-wildfly-could-not-inject-members > Warp on WildFly: CDI fails to inject into inspection that is inner static class > ------------------------------------------------------------------------------- > > Key: ARQ-1598 > URL: https://issues.jboss.org/browse/ARQ-1598 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Environment: WildFly 8.0.0.Beta2-SNAPSHOT > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Alpha6 > > > When class is inner static class: > {code} > public class MyTest { > @Test > public void test1() { > Warp....inspect(new MyInspection()); > Warp....inspect(new MyInspection()); // fails > } > @Test > public void test2() { > Warp....inspect(new MyInspection()); // fails > } > public static class MyInspection() { > } > } > {code} > the first inspection pass, but all subsequent inspections fails in the scope of one deployment. > ---- > I think that is because the class is already loaded in classloader and its scanning might be cached by Weld. > ---- > A issue was originally reproduced and reported here: > https://issues.jboss.org/browse/RF-13417 > ---- > Exception and cause: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValue > {code} > {code} > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Dec 5 04:05:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 04:05:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1598) Warp on WildFly: CDI fails to inject into inspection that is inner static class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928806#comment-12928806 ] Luk?? Fry? commented on ARQ-1598: --------------------------------- The reproduced commited to Warp ftests: https://github.com/lfryc/arquillian-extension-warp/tree/ARQ-1598-warp-wildfly-could-not-inject-members > Warp on WildFly: CDI fails to inject into inspection that is inner static class > ------------------------------------------------------------------------------- > > Key: ARQ-1598 > URL: https://issues.jboss.org/browse/ARQ-1598 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Environment: WildFly 8.0.0.Beta2-SNAPSHOT > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Alpha6 > > > When class is inner static class: > {code} > public class MyTest { > @Test > public void test1() { > Warp....inspect(new MyInspection()); > Warp....inspect(new MyInspection()); // fails > } > @Test > public void test2() { > Warp....inspect(new MyInspection()); // fails > } > public static class MyInspection() { > } > } > {code} > the first inspection pass, but all subsequent inspections fails in the scope of one deployment. > ---- > I think that is because the class is already loaded in classloader and its scanning might be cached by Weld. > ---- > A issue was originally reproduced and reported here: > https://issues.jboss.org/browse/RF-13417 > ---- > Exception and cause: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValue > {code} > {code} > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Dec 5 04:24:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 04:24:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1598) Warp on WildFly: CDI fails to inject into inspection that is inner static class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928815#comment-12928815 ] Luk?? Fry? commented on ARQ-1598: --------------------------------- It works fine for inner classes, probably because their names doesn't clash. ---- I have tried and the fact is that we need to "transform" static inner classes as well, because they bears a link to declaring class, which prevents classloading. ---- Another suggestion might be loading inner static classes just once on server-side. > Warp on WildFly: CDI fails to inject into inspection that is inner static class > ------------------------------------------------------------------------------- > > Key: ARQ-1598 > URL: https://issues.jboss.org/browse/ARQ-1598 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Environment: WildFly 8.0.0.Beta2-SNAPSHOT > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Alpha6 > > > When class is inner static class: > {code} > public class MyTest { > @Test > public void test1() { > Warp....inspect(new MyInspection()); > Warp....inspect(new MyInspection()); // fails > } > @Test > public void test2() { > Warp....inspect(new MyInspection()); // fails > } > public static class MyInspection() { > } > } > {code} > the first inspection pass, but all subsequent inspections fails in the scope of one deployment. > ---- > I think that is because the class is already loaded in classloader and its scanning might be cached by Weld. > ---- > A issue was originally reproduced and reported here: > https://issues.jboss.org/browse/RF-13417 > ---- > Exception and cause: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValue > {code} > {code} > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Dec 5 04:24:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 04:24:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1598) Warp on WildFly: CDI fails to inject into inspection that is inner static class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928815#comment-12928815 ] Luk?? Fry? edited comment on ARQ-1598 at 12/5/13 4:23 AM: ---------------------------------------------------------- It works fine for inner classes, probably because their names doesn't clash. ---- I have tried and the fact is that we need to "transform" static inner classes as well, because they bears a link to declaring class, which prevents classloading. ---- Another suggestion might be loading inner static classes just once on server-side - keeping a deployment-scoped class store for classes that was already loaded. was (Author: lfryc): It works fine for inner classes, probably because their names doesn't clash. ---- I have tried and the fact is that we need to "transform" static inner classes as well, because they bears a link to declaring class, which prevents classloading. ---- Another suggestion might be loading inner static classes just once on server-side. > Warp on WildFly: CDI fails to inject into inspection that is inner static class > ------------------------------------------------------------------------------- > > Key: ARQ-1598 > URL: https://issues.jboss.org/browse/ARQ-1598 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Environment: WildFly 8.0.0.Beta2-SNAPSHOT > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Alpha6 > > > When class is inner static class: > {code} > public class MyTest { > @Test > public void test1() { > Warp....inspect(new MyInspection()); > Warp....inspect(new MyInspection()); // fails > } > @Test > public void test2() { > Warp....inspect(new MyInspection()); // fails > } > public static class MyInspection() { > } > } > {code} > the first inspection pass, but all subsequent inspections fails in the scope of one deployment. > ---- > I think that is because the class is already loaded in classloader and its scanning might be cached by Weld. > ---- > A issue was originally reproduced and reported here: > https://issues.jboss.org/browse/RF-13417 > ---- > Exception and cause: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValue > {code} > {code} > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Dec 5 05:25:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 05:25:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1598) Warp on WildFly: CDI fails to inject into inspection that is inner static class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928852#comment-12928852 ] Luk?? Fry? commented on ARQ-1598: --------------------------------- Note: the same issue happens when we use twice the same anonymous class: {code} public class MyTest { @Test public void test1() { runWarp(); } @Test public void test2() { runWarp(); // fails } private void runWarp() { Warp....inspect(new Inspection() { private static final long serialVersionUID = 1L; }); } } {code} The suggested solution should work here (caching classes), but it came to my mind that we could also take completely another approach: do deployment-build-time extraction of member classes (that extends Inspection?) from declaring class (which we are avoiding to load by this whole "transformation process"). In such a way, we would not need to load classes during requests, they would be loaded just once per deployment, thus we wouldn't need caching. > Warp on WildFly: CDI fails to inject into inspection that is inner static class > ------------------------------------------------------------------------------- > > Key: ARQ-1598 > URL: https://issues.jboss.org/browse/ARQ-1598 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Environment: WildFly 8.0.0.Beta2-SNAPSHOT > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Alpha6 > > > When class is inner static class: > {code} > public class MyTest { > @Test > public void test1() { > Warp....inspect(new MyInspection()); > Warp....inspect(new MyInspection()); // fails > } > @Test > public void test2() { > Warp....inspect(new MyInspection()); // fails > } > public static class MyInspection() { > } > } > {code} > the first inspection pass, but all subsequent inspections fails in the scope of one deployment. > ---- > I think that is because the class is already loaded in classloader and its scanning might be cached by Weld. > ---- > A issue was originally reproduced and reported here: > https://issues.jboss.org/browse/RF-13417 > ---- > Exception and cause: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValue > {code} > {code} > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Dec 6 07:12:05 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 6 Dec 2013 07:12:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1599) Droidium should be able to manage permissions of app for testing purposes In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1599: -------------------------------------- Summary: Droidium should be able to manage permissions of app for testing purposes Key: ARQ-1599 URL: https://issues.jboss.org/browse/ARQ-1599 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: 1.0.0.Beta1 Reporter: Stefan Miklosovic Application under test has to have permissions specified in its AndroidManifest.xml which enable it to be used with Selendroid. If developer does not add them there, he is not able to test it. >From usability point of view, it is needed that even APK has not some permissions, Droidium will modify application in runtime and dynamically adds them there so developer does not have to touch APK at all. This also solves the problem with testing APKs when we do not have sources to Android application so we can not add them there manually - exluding all such apps from testing process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Dec 6 07:14:05 2013 From: jira-events at lists.jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 6 Dec 2013 07:14:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1599) Droidium should be able to manage permissions of app for testing purposes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1599: -------------------------------------- Assignee: Stefan Miklosovic > Droidium should be able to manage permissions of app for testing purposes > ------------------------------------------------------------------------- > > Key: ARQ-1599 > URL: https://issues.jboss.org/browse/ARQ-1599 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: 1.0.0.Beta1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > Application under test has to have permissions specified in its AndroidManifest.xml which enable it to be used with Selendroid. If developer does not add them there, he is not able to test it. > From usability point of view, it is needed that even APK has not some permissions, Droidium will modify application in runtime and dynamically adds them there so developer does not have to touch APK at all. > This also solves the problem with testing APKs when we do not have sources to Android application so we can not add them there manually - exluding all such apps from testing process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Dec 6 07:18:05 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Fri, 6 Dec 2013 07:18:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1599) Droidium should be able to manage permissions of app for testing purposes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929154#comment-12929154 ] Karel Piwko commented on ARQ-1599: ---------------------------------- I think this is a work for ApkBuilder project, as it was proposed in the past. > Droidium should be able to manage permissions of app for testing purposes > ------------------------------------------------------------------------- > > Key: ARQ-1599 > URL: https://issues.jboss.org/browse/ARQ-1599 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: 1.0.0.Beta1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > Application under test has to have permissions specified in its AndroidManifest.xml which enable it to be used with Selendroid. If developer does not add them there, he is not able to test it. > From usability point of view, it is needed that even APK has not some permissions, Droidium will modify application in runtime and dynamically adds them there so developer does not have to touch APK at all. > This also solves the problem with testing APKs when we do not have sources to Android application so we can not add them there manually - exluding all such apps from testing process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Dec 9 06:48:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Mon, 9 Dec 2013 06:48:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1600) ProcessExecutor might get stuck on Windows In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1600: -------------------------------- Summary: ProcessExecutor might get stuck on Windows Key: ARQ-1600 URL: https://issues.jboss.org/browse/ARQ-1600 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Karel Piwko Priority: Blocker Current execution of external process on Windows might lead to following issues, causing process deadlock: 1/ Process stdin is not closed if no longer needed 2/ Process stdout and stderr never reach EOF This behavior is observed when a .bat file file is executed on Windows. This behavior is caused by missing file descriptors to underlying process spawned by bat file. Implementation note: There are two ways how to resolve the issue. * read output stream and consider them finished if specific message is encountered * unwrap bat execution and execute directly underlying command -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Dec 9 06:48:07 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Mon, 9 Dec 2013 06:48:07 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1600) ProcessExecutor might get stuck on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1600: ----------------------------- Component/s: Extension - Droidium > ProcessExecutor might get stuck on Windows > ------------------------------------------- > > Key: ARQ-1600 > URL: https://issues.jboss.org/browse/ARQ-1600 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Priority: Blocker > > Current execution of external process on Windows might lead to following issues, causing process deadlock: > 1/ Process stdin is not closed if no longer needed > 2/ Process stdout and stderr never reach EOF > This behavior is observed when a .bat file file is executed on Windows. This behavior is caused by missing file descriptors to underlying process spawned by bat file. > Implementation note: There are two ways how to resolve the issue. > * read output stream and consider them finished if specific message is encountered > * unwrap bat execution and execute directly underlying command -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Dec 9 06:48:07 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Mon, 9 Dec 2013 06:48:07 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1600) ProcessExecutor might get stuck on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1600: ----------------------------- Affects Version/s: droidium_1.0.0.Alpha3 > ProcessExecutor might get stuck on Windows > ------------------------------------------- > > Key: ARQ-1600 > URL: https://issues.jboss.org/browse/ARQ-1600 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Priority: Blocker > > Current execution of external process on Windows might lead to following issues, causing process deadlock: > 1/ Process stdin is not closed if no longer needed > 2/ Process stdout and stderr never reach EOF > This behavior is observed when a .bat file file is executed on Windows. This behavior is caused by missing file descriptors to underlying process spawned by bat file. > Implementation note: There are two ways how to resolve the issue. > * read output stream and consider them finished if specific message is encountered > * unwrap bat execution and execute directly underlying command -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Dec 9 06:50:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Mon, 9 Dec 2013 06:50:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1601) adb is not found on Windows In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1601: -------------------------------- Summary: adb is not found on Windows Key: ARQ-1601 URL: https://issues.jboss.org/browse/ARQ-1601 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha3 Reporter: Karel Piwko Priority: Critical Current logic for searching tool location does not work correctly on windows. For instance, setup is not able to find adb if arquillian.xml file contains androidHome with backslashes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 10 04:05:05 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 10 Dec 2013 04:05:05 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1602) Emulator process returns immediately on Windows In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1602: -------------------------------- Summary: Emulator process returns immediately on Windows Key: ARQ-1602 URL: https://issues.jboss.org/browse/ARQ-1602 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha3 Reporter: Karel Piwko Priority: Critical Changes introduced in ARQ-1583 are not compatible with Windows, where emulator.exe spawns another process itself and returns immediately. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 10 04:26:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 10 Dec 2013 04:26:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1603) tmpDir specification should allow to be without trailing slash In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1603: -------------------------------- Summary: tmpDir specification should allow to be without trailing slash Key: ARQ-1603 URL: https://issues.jboss.org/browse/ARQ-1603 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha3 Reporter: Karel Piwko *Given*: I define tmpDir like "C:\temp" or /tmp *Then*: Droidium creates a temp directory like C:\temp-1223-1454-1245-12545 *Expect*: I expect directory to be rather C:\temp\1223-1454-1245-12545 Current behavior is problematic as it requires user to be slash aware as otherwise he might want to create a directory in tree hierarchy where elevated permissions are needed. Implemenation note: new File(File parent, String childPath) would be the best way how to handle this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 10 06:37:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 10 Dec 2013 06:37:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1602) Emulator process returns immediately on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1602: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-droidium/pull/9 > Emulator process returns immediately on Windows > ----------------------------------------------- > > Key: ARQ-1602 > URL: https://issues.jboss.org/browse/ARQ-1602 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Priority: Critical > > Changes introduced in ARQ-1583 are not compatible with Windows, where emulator.exe spawns another process itself and returns immediately. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 10 06:37:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 10 Dec 2013 06:37:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1600) ProcessExecutor might get stuck on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1600: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-droidium/pull/9 > ProcessExecutor might get stuck on Windows > ------------------------------------------- > > Key: ARQ-1600 > URL: https://issues.jboss.org/browse/ARQ-1600 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Priority: Blocker > > Current execution of external process on Windows might lead to following issues, causing process deadlock: > 1/ Process stdin is not closed if no longer needed > 2/ Process stdout and stderr never reach EOF > This behavior is observed when a .bat file file is executed on Windows. This behavior is caused by missing file descriptors to underlying process spawned by bat file. > Implementation note: There are two ways how to resolve the issue. > * read output stream and consider them finished if specific message is encountered > * unwrap bat execution and execute directly underlying command -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Dec 10 06:37:06 2013 From: jira-events at lists.jboss.org (Karel Piwko (JIRA)) Date: Tue, 10 Dec 2013 06:37:06 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1601) adb is not found on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1601: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-droidium/pull/9 > adb is not found on Windows > --------------------------- > > Key: ARQ-1601 > URL: https://issues.jboss.org/browse/ARQ-1601 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Priority: Critical > > Current logic for searching tool location does not work correctly on windows. > For instance, setup is not able to find adb if arquillian.xml file contains androidHome with backslashes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Dec 11 07:40:36 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 11 Dec 2013 07:40:36 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1553) Warp: Diverge Proxy as independent extension to allow reuse by other extensions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1553: ---------------------------- Fix Version/s: warp_1.0_tracking > Warp: Diverge Proxy as independent extension to allow reuse by other extensions > ------------------------------------------------------------------------------- > > Key: ARQ-1553 > URL: https://issues.jboss.org/browse/ARQ-1553 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Fix For: warp_1.0_tracking > > > Some extensions might reuse proxy between client and server to modify request/response or attach arbitrary data/payload. > Some candidates to be part of this extension: > * HTTP proxy - LittleProxy integration > * OperationalContexts (might be rather part of core) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Dec 11 07:42:33 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 11 Dec 2013 07:42:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1592) Warp: Wrong command bus uri for multiple context roots In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1592: ---------------------------- Description: 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 {code} 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) ... {code} was: 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) ... > 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 > {code} > 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) > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Dec 11 07:44:32 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 11 Dec 2013 07:44:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1592) Warp: Wrong command bus uri for multiple context roots In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930211#comment-12930211 ] Luk?? Fry? commented on ARQ-1592: --------------------------------- Tilmann, could you eventually create a reproducer? It should be ideally in a Warp functional test suite? > 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 > {code} > 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) > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Dec 11 07:44:33 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 11 Dec 2013 07:44:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1592) Warp: Wrong command bus uri for multiple context roots In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1592: ---------------------------- Fix Version/s: warp_1.0_tracking > 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 > Fix For: warp_1.0_tracking > > > 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 > {code} > 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) > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Dec 11 07:44:33 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 11 Dec 2013 07:44:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1564) TestClass not inserted into ClassPool In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1564: ---------------------------- Description: TransformedInspection.transfom() tries to access and rename the Testclass from the ClassPool but the Testclass was never inserted into the ClassPool. {code} TestClass: @RunWith(Arquillian.class) @WarpTest @RunAsClient public class StudentTest { private static final String webDir = "web/"; @Deployment public static WebArchive createDeployment() { return ShrinkWrap.create(WebArchive.class, "student.war").addClass(Student.class) .addAsWebResource(new File(webDir, "index.xhtml")) .addAsWebInfResource(new File(webDir, "WEB-INF/beans.xml")) .addAsWebInfResource(new File(webDir, "WEB-INF/web.xml")) .addAsWebInfResource(new File(webDir, "WEB-INF/faces-config.xml")); } @Drone private WebDriver browser; @ArquillianResource private URL deploymentUrl; @Test public void test() { new ClassPool().insertClassPath(new ClassClassPath(this.getClass())); Warp .initiate(new Activity() { public void perform() { browser.navigate().to(deploymentUrl + "index.jsf"); } }) .inspect(new Inspection() { private static final long serialVersionUID = 1L; @AfterPhase(RENDER_RESPONSE) public void initial_state_havent_changed_yet() { assertEquals("John", "John"); } } ); } } {code} {code} Stacktrace: org.jboss.arquillian.warp.exception.ClientWarpExecutionException: enriching request failed; caused by: javassist.NotFoundException: StudentTest$1 at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpRequestEnrichmentService.enrichRequest(DefaultHttpRequestEnrichmentService.java:133) at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.enrichRequest(EnrichmentObserver.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryEnrichRequest(EnrichmentObserver.java:75) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.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.DefaultHttpRequestEnrichmentFilter.filter(DefaultHttpRequestEnrichmentFilter.java:50) at org.jboss.arquillian.warp.impl.client.proxy.DefaultProxyService$2.performInContext(DefaultProxyService.java:99) at org.jboss.arquillian.warp.impl.client.proxy.DefaultProxyService$2.performInContext(DefaultProxyService.java:96) at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.performInContext(Contextualizer.java:54) at org.jboss.arquillian.warp.impl.client.proxy.DefaultProxyService$3.filter(DefaultProxyService.java:108) at org.littleshoot.proxy.ProxyHttpRequestEncoder.encode(ProxyHttpRequestEncoder.java:75) at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.doEncode(OneToOneEncoder.java:66) at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:59) at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784) at org.jboss.netty.channel.SimpleChannelHandler.writeRequested(SimpleChannelHandler.java:292) at org.jboss.netty.channel.SimpleChannelHandler.handleDownstream(SimpleChannelHandler.java:254) at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582) at org.jboss.netty.channel.Channels.write(Channels.java:704) at org.jboss.netty.channel.Channels.write(Channels.java:671) at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:248) at org.littleshoot.proxy.HttpRequestHandler$1OnConnect.onConnect(HttpRequestHandler.java:407) at org.littleshoot.proxy.HttpRequestHandler$1LocalChannelFutureListener.operationComplete(HttpRequestHandler.java:488) at org.jboss.netty.channel.DefaultChannelFuture.notifyListener(DefaultChannelFuture.java:427) at org.jboss.netty.channel.DefaultChannelFuture.addListener(DefaultChannelFuture.java:145) at org.littleshoot.proxy.HttpRequestHandler.processRequest(HttpRequestHandler.java:539) at org.littleshoot.proxy.HttpRequestHandler.messageReceived(HttpRequestHandler.java:276) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) at org.jboss.netty.channel.SimpleChannelHandler.messageReceived(SimpleChannelHandler.java:142) at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88) at org.jboss.netty.handler.timeout.IdleStateAwareChannelHandler.handleUpstream(IdleStateAwareChannelHandler.java:36) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) at org.jboss.netty.handler.timeout.IdleStateHandler.messageReceived(IdleStateHandler.java:294) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:459) at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:536) at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:435) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107) at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.RuntimeException: Could not transform and replicate class class java.util.Arrays$ArrayList: Unable to transform inspection StudentTest$1: StudentTest$1 at org.jboss.arquillian.warp.impl.shared.RequestPayload.writeExternal(RequestPayload.java:113) at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1443) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1414) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) at org.jboss.arquillian.warp.impl.utils.SerializationUtils.serializeToBytes(SerializationUtils.java:38) at org.jboss.arquillian.warp.impl.utils.SerializationUtils.serializeToBase64(SerializationUtils.java:59) at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpRequestEnrichmentService.enrichRequest(DefaultHttpRequestEnrichmentService.java:125) ... 76 more Caused by: org.jboss.arquillian.warp.impl.client.transformation.InspectionTransformationException: Unable to transform inspection StudentTest$1: StudentTest$1 at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.transform(TransformedInspection.java:90) at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.(TransformedInspection.java:57) at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.(TransformedInspection.java:49) at org.jboss.arquillian.warp.impl.shared.RequestPayload.writeExternal(RequestPayload.java:107) ... 83 more Caused by: javassist.NotFoundException: StudentTest$1 at javassist.ClassPool.getAndRename(ClassPool.java:387) at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.transform(TransformedInspection.java:65) ... 86 more {code} was: TransformedInspection.transfom() tries to access and rename the Testclass from the ClassPool but the Testclass was never inserted into the ClassPool. TestClass: @RunWith(Arquillian.class) @WarpTest @RunAsClient public class StudentTest { private static final String webDir = "web/"; @Deployment public static WebArchive createDeployment() { return ShrinkWrap.create(WebArchive.class, "student.war").addClass(Student.class) .addAsWebResource(new File(webDir, "index.xhtml")) .addAsWebInfResource(new File(webDir, "WEB-INF/beans.xml")) .addAsWebInfResource(new File(webDir, "WEB-INF/web.xml")) .addAsWebInfResource(new File(webDir, "WEB-INF/faces-config.xml")); } @Drone private WebDriver browser; @ArquillianResource private URL deploymentUrl; @Test public void test() { new ClassPool().insertClassPath(new ClassClassPath(this.getClass())); Warp .initiate(new Activity() { public void perform() { browser.navigate().to(deploymentUrl + "index.jsf"); } }) .inspect(new Inspection() { private static final long serialVersionUID = 1L; @AfterPhase(RENDER_RESPONSE) public void initial_state_havent_changed_yet() { assertEquals("John", "John"); } } ); } } Stacktrace: org.jboss.arquillian.warp.exception.ClientWarpExecutionException: enriching request failed; caused by: javassist.NotFoundException: StudentTest$1 at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpRequestEnrichmentService.enrichRequest(DefaultHttpRequestEnrichmentService.java:133) at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.enrichRequest(EnrichmentObserver.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryEnrichRequest(EnrichmentObserver.java:75) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.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.DefaultHttpRequestEnrichmentFilter.filter(DefaultHttpRequestEnrichmentFilter.java:50) at org.jboss.arquillian.warp.impl.client.proxy.DefaultProxyService$2.performInContext(DefaultProxyService.java:99) at org.jboss.arquillian.warp.impl.client.proxy.DefaultProxyService$2.performInContext(DefaultProxyService.java:96) at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.performInContext(Contextualizer.java:54) at org.jboss.arquillian.warp.impl.client.proxy.DefaultProxyService$3.filter(DefaultProxyService.java:108) at org.littleshoot.proxy.ProxyHttpRequestEncoder.encode(ProxyHttpRequestEncoder.java:75) at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.doEncode(OneToOneEncoder.java:66) at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:59) at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784) at org.jboss.netty.channel.SimpleChannelHandler.writeRequested(SimpleChannelHandler.java:292) at org.jboss.netty.channel.SimpleChannelHandler.handleDownstream(SimpleChannelHandler.java:254) at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582) at org.jboss.netty.channel.Channels.write(Channels.java:704) at org.jboss.netty.channel.Channels.write(Channels.java:671) at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:248) at org.littleshoot.proxy.HttpRequestHandler$1OnConnect.onConnect(HttpRequestHandler.java:407) at org.littleshoot.proxy.HttpRequestHandler$1LocalChannelFutureListener.operationComplete(HttpRequestHandler.java:488) at org.jboss.netty.channel.DefaultChannelFuture.notifyListener(DefaultChannelFuture.java:427) at org.jboss.netty.channel.DefaultChannelFuture.addListener(DefaultChannelFuture.java:145) at org.littleshoot.proxy.HttpRequestHandler.processRequest(HttpRequestHandler.java:539) at org.littleshoot.proxy.HttpRequestHandler.messageReceived(HttpRequestHandler.java:276) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) at org.jboss.netty.channel.SimpleChannelHandler.messageReceived(SimpleChannelHandler.java:142) at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88) at org.jboss.netty.handler.timeout.IdleStateAwareChannelHandler.handleUpstream(IdleStateAwareChannelHandler.java:36) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) at org.jboss.netty.handler.timeout.IdleStateHandler.messageReceived(IdleStateHandler.java:294) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:459) at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:536) at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:435) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107) at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.RuntimeException: Could not transform and replicate class class java.util.Arrays$ArrayList: Unable to transform inspection StudentTest$1: StudentTest$1 at org.jboss.arquillian.warp.impl.shared.RequestPayload.writeExternal(RequestPayload.java:113) at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1443) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1414) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) at org.jboss.arquillian.warp.impl.utils.SerializationUtils.serializeToBytes(SerializationUtils.java:38) at org.jboss.arquillian.warp.impl.utils.SerializationUtils.serializeToBase64(SerializationUtils.java:59) at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpRequestEnrichmentService.enrichRequest(DefaultHttpRequestEnrichmentService.java:125) ... 76 more Caused by: org.jboss.arquillian.warp.impl.client.transformation.InspectionTransformationException: Unable to transform inspection StudentTest$1: StudentTest$1 at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.transform(TransformedInspection.java:90) at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.(TransformedInspection.java:57) at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.(TransformedInspection.java:49) at org.jboss.arquillian.warp.impl.shared.RequestPayload.writeExternal(RequestPayload.java:107) ... 83 more Caused by: javassist.NotFoundException: StudentTest$1 at javassist.ClassPool.getAndRename(ClassPool.java:387) at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.transform(TransformedInspection.java:65) ... 86 more > TestClass not inserted into ClassPool > ------------------------------------- > > Key: ARQ-1564 > URL: https://issues.jboss.org/browse/ARQ-1564 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha5 > Environment: Windows 8 64 Bit SunJDK 1.7 > Reporter: Lukas Eichler > > TransformedInspection.transfom() tries to access and rename the Testclass from the ClassPool but the Testclass was never inserted into the ClassPool. > {code} > TestClass: > @RunWith(Arquillian.class) > @WarpTest > @RunAsClient > public class StudentTest { > private static final String webDir = "web/"; > @Deployment > public static WebArchive createDeployment() { > return ShrinkWrap.create(WebArchive.class, "student.war").addClass(Student.class) > .addAsWebResource(new File(webDir, "index.xhtml")) > .addAsWebInfResource(new File(webDir, "WEB-INF/beans.xml")) > .addAsWebInfResource(new File(webDir, "WEB-INF/web.xml")) > .addAsWebInfResource(new File(webDir, "WEB-INF/faces-config.xml")); > } > @Drone > private WebDriver browser; > @ArquillianResource > private URL deploymentUrl; > @Test > public void test() { > new ClassPool().insertClassPath(new ClassClassPath(this.getClass())); > Warp > .initiate(new Activity() { > public void perform() { > browser.navigate().to(deploymentUrl + "index.jsf"); > } > }) > .inspect(new Inspection() { > private static final long serialVersionUID = 1L; > @AfterPhase(RENDER_RESPONSE) > public void initial_state_havent_changed_yet() { > assertEquals("John", "John"); > } > } > ); > } > } > {code} > {code} > Stacktrace: > org.jboss.arquillian.warp.exception.ClientWarpExecutionException: enriching request failed; caused by: > javassist.NotFoundException: StudentTest$1 > at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpRequestEnrichmentService.enrichRequest(DefaultHttpRequestEnrichmentService.java:133) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.enrichRequest(EnrichmentObserver.java:85) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryEnrichRequest(EnrichmentObserver.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.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.DefaultHttpRequestEnrichmentFilter.filter(DefaultHttpRequestEnrichmentFilter.java:50) > at org.jboss.arquillian.warp.impl.client.proxy.DefaultProxyService$2.performInContext(DefaultProxyService.java:99) > at org.jboss.arquillian.warp.impl.client.proxy.DefaultProxyService$2.performInContext(DefaultProxyService.java:96) > at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.performInContext(Contextualizer.java:54) > at org.jboss.arquillian.warp.impl.client.proxy.DefaultProxyService$3.filter(DefaultProxyService.java:108) > at org.littleshoot.proxy.ProxyHttpRequestEncoder.encode(ProxyHttpRequestEncoder.java:75) > at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.doEncode(OneToOneEncoder.java:66) > at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:59) > at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) > at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784) > at org.jboss.netty.channel.SimpleChannelHandler.writeRequested(SimpleChannelHandler.java:292) > at org.jboss.netty.channel.SimpleChannelHandler.handleDownstream(SimpleChannelHandler.java:254) > at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) > at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582) > at org.jboss.netty.channel.Channels.write(Channels.java:704) > at org.jboss.netty.channel.Channels.write(Channels.java:671) > at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:248) > at org.littleshoot.proxy.HttpRequestHandler$1OnConnect.onConnect(HttpRequestHandler.java:407) > at org.littleshoot.proxy.HttpRequestHandler$1LocalChannelFutureListener.operationComplete(HttpRequestHandler.java:488) > at org.jboss.netty.channel.DefaultChannelFuture.notifyListener(DefaultChannelFuture.java:427) > at org.jboss.netty.channel.DefaultChannelFuture.addListener(DefaultChannelFuture.java:145) > at org.littleshoot.proxy.HttpRequestHandler.processRequest(HttpRequestHandler.java:539) > at org.littleshoot.proxy.HttpRequestHandler.messageReceived(HttpRequestHandler.java:276) > at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) > at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) > at org.jboss.netty.channel.SimpleChannelHandler.messageReceived(SimpleChannelHandler.java:142) > at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88) > at org.jboss.netty.handler.timeout.IdleStateAwareChannelHandler.handleUpstream(IdleStateAwareChannelHandler.java:36) > at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) > at org.jboss.netty.handler.timeout.IdleStateHandler.messageReceived(IdleStateHandler.java:294) > at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) > at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) > at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:459) > at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:536) > at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:435) > at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) > at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) > at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) > at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107) > at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) > at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88) > at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) > at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) > at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:722) > Caused by: java.lang.RuntimeException: Could not transform and replicate class class java.util.Arrays$ArrayList: > Unable to transform inspection StudentTest$1: > StudentTest$1 > at org.jboss.arquillian.warp.impl.shared.RequestPayload.writeExternal(RequestPayload.java:113) > at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1443) > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1414) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) > at org.jboss.arquillian.warp.impl.utils.SerializationUtils.serializeToBytes(SerializationUtils.java:38) > at org.jboss.arquillian.warp.impl.utils.SerializationUtils.serializeToBase64(SerializationUtils.java:59) > at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpRequestEnrichmentService.enrichRequest(DefaultHttpRequestEnrichmentService.java:125) > ... 76 more > Caused by: org.jboss.arquillian.warp.impl.client.transformation.InspectionTransformationException: Unable to transform inspection StudentTest$1: > StudentTest$1 > at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.transform(TransformedInspection.java:90) > at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.(TransformedInspection.java:57) > at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.(TransformedInspection.java:49) > at org.jboss.arquillian.warp.impl.shared.RequestPayload.writeExternal(RequestPayload.java:107) > ... 83 more > Caused by: javassist.NotFoundException: StudentTest$1 > at javassist.ClassPool.getAndRename(ClassPool.java:387) > at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.transform(TransformedInspection.java:65) > ... 86 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Dec 11 07:46:33 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 11 Dec 2013 07:46:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1564) TestClass not inserted into ClassPool In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930215#comment-12930215 ] Luk?? Fry? commented on ARQ-1564: --------------------------------- Lukas, what are you trying to achieve on this line: {code} new ClassPool().insertClassPath(new ClassClassPath(this.getClass())); {code} I wonder whether that line breaks a test or does it enable it? > TestClass not inserted into ClassPool > ------------------------------------- > > Key: ARQ-1564 > URL: https://issues.jboss.org/browse/ARQ-1564 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha5 > Environment: Windows 8 64 Bit SunJDK 1.7 > Reporter: Lukas Eichler > > TransformedInspection.transfom() tries to access and rename the Testclass from the ClassPool but the Testclass was never inserted into the ClassPool. > {code} > TestClass: > @RunWith(Arquillian.class) > @WarpTest > @RunAsClient > public class StudentTest { > private static final String webDir = "web/"; > @Deployment > public static WebArchive createDeployment() { > return ShrinkWrap.create(WebArchive.class, "student.war").addClass(Student.class) > .addAsWebResource(new File(webDir, "index.xhtml")) > .addAsWebInfResource(new File(webDir, "WEB-INF/beans.xml")) > .addAsWebInfResource(new File(webDir, "WEB-INF/web.xml")) > .addAsWebInfResource(new File(webDir, "WEB-INF/faces-config.xml")); > } > @Drone > private WebDriver browser; > @ArquillianResource > private URL deploymentUrl; > @Test > public void test() { > new ClassPool().insertClassPath(new ClassClassPath(this.getClass())); > Warp > .initiate(new Activity() { > public void perform() { > browser.navigate().to(deploymentUrl + "index.jsf"); > } > }) > .inspect(new Inspection() { > private static final long serialVersionUID = 1L; > @AfterPhase(RENDER_RESPONSE) > public void initial_state_havent_changed_yet() { > assertEquals("John", "John"); > } > } > ); > } > } > {code} > {code} > Stacktrace: > org.jboss.arquillian.warp.exception.ClientWarpExecutionException: enriching request failed; caused by: > javassist.NotFoundException: StudentTest$1 > at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpRequestEnrichmentService.enrichRequest(DefaultHttpRequestEnrichmentService.java:133) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.enrichRequest(EnrichmentObserver.java:85) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryEnrichRequest(EnrichmentObserver.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.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.DefaultHttpRequestEnrichmentFilter.filter(DefaultHttpRequestEnrichmentFilter.java:50) > at org.jboss.arquillian.warp.impl.client.proxy.DefaultProxyService$2.performInContext(DefaultProxyService.java:99) > at org.jboss.arquillian.warp.impl.client.proxy.DefaultProxyService$2.performInContext(DefaultProxyService.java:96) > at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.performInContext(Contextualizer.java:54) > at org.jboss.arquillian.warp.impl.client.proxy.DefaultProxyService$3.filter(DefaultProxyService.java:108) > at org.littleshoot.proxy.ProxyHttpRequestEncoder.encode(ProxyHttpRequestEncoder.java:75) > at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.doEncode(OneToOneEncoder.java:66) > at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:59) > at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) > at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784) > at org.jboss.netty.channel.SimpleChannelHandler.writeRequested(SimpleChannelHandler.java:292) > at org.jboss.netty.channel.SimpleChannelHandler.handleDownstream(SimpleChannelHandler.java:254) > at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) > at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582) > at org.jboss.netty.channel.Channels.write(Channels.java:704) > at org.jboss.netty.channel.Channels.write(Channels.java:671) > at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:248) > at org.littleshoot.proxy.HttpRequestHandler$1OnConnect.onConnect(HttpRequestHandler.java:407) > at org.littleshoot.proxy.HttpRequestHandler$1LocalChannelFutureListener.operationComplete(HttpRequestHandler.java:488) > at org.jboss.netty.channel.DefaultChannelFuture.notifyListener(DefaultChannelFuture.java:427) > at org.jboss.netty.channel.DefaultChannelFuture.addListener(DefaultChannelFuture.java:145) > at org.littleshoot.proxy.HttpRequestHandler.processRequest(HttpRequestHandler.java:539) > at org.littleshoot.proxy.HttpRequestHandler.messageReceived(HttpRequestHandler.java:276) > at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) > at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) > at org.jboss.netty.channel.SimpleChannelHandler.messageReceived(SimpleChannelHandler.java:142) > at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88) > at org.jboss.netty.handler.timeout.IdleStateAwareChannelHandler.handleUpstream(IdleStateAwareChannelHandler.java:36) > at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) > at org.jboss.netty.handler.timeout.IdleStateHandler.messageReceived(IdleStateHandler.java:294) > at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) > at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) > at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:459) > at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:536) > at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:435) > at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) > at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) > at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) > at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107) > at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) > at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88) > at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) > at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) > at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:722) > Caused by: java.lang.RuntimeException: Could not transform and replicate class class java.util.Arrays$ArrayList: > Unable to transform inspection StudentTest$1: > StudentTest$1 > at org.jboss.arquillian.warp.impl.shared.RequestPayload.writeExternal(RequestPayload.java:113) > at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1443) > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1414) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) > at org.jboss.arquillian.warp.impl.utils.SerializationUtils.serializeToBytes(SerializationUtils.java:38) > at org.jboss.arquillian.warp.impl.utils.SerializationUtils.serializeToBase64(SerializationUtils.java:59) > at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpRequestEnrichmentService.enrichRequest(DefaultHttpRequestEnrichmentService.java:125) > ... 76 more > Caused by: org.jboss.arquillian.warp.impl.client.transformation.InspectionTransformationException: Unable to transform inspection StudentTest$1: > StudentTest$1 > at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.transform(TransformedInspection.java:90) > at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.(TransformedInspection.java:57) > at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.(TransformedInspection.java:49) > at org.jboss.arquillian.warp.impl.shared.RequestPayload.writeExternal(RequestPayload.java:107) > ... 83 more > Caused by: javassist.NotFoundException: StudentTest$1 > at javassist.ClassPool.getAndRename(ClassPool.java:387) > at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.transform(TransformedInspection.java:65) > ... 86 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Dec 11 07:46:33 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 11 Dec 2013 07:46:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1564) TestClass not inserted into ClassPool In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1564: ---------------------------- Fix Version/s: warp_1.0_tracking > TestClass not inserted into ClassPool > ------------------------------------- > > Key: ARQ-1564 > URL: https://issues.jboss.org/browse/ARQ-1564 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha5 > Environment: Windows 8 64 Bit SunJDK 1.7 > Reporter: Lukas Eichler > Fix For: warp_1.0_tracking > > > TransformedInspection.transfom() tries to access and rename the Testclass from the ClassPool but the Testclass was never inserted into the ClassPool. > {code} > TestClass: > @RunWith(Arquillian.class) > @WarpTest > @RunAsClient > public class StudentTest { > private static final String webDir = "web/"; > @Deployment > public static WebArchive createDeployment() { > return ShrinkWrap.create(WebArchive.class, "student.war").addClass(Student.class) > .addAsWebResource(new File(webDir, "index.xhtml")) > .addAsWebInfResource(new File(webDir, "WEB-INF/beans.xml")) > .addAsWebInfResource(new File(webDir, "WEB-INF/web.xml")) > .addAsWebInfResource(new File(webDir, "WEB-INF/faces-config.xml")); > } > @Drone > private WebDriver browser; > @ArquillianResource > private URL deploymentUrl; > @Test > public void test() { > new ClassPool().insertClassPath(new ClassClassPath(this.getClass())); > Warp > .initiate(new Activity() { > public void perform() { > browser.navigate().to(deploymentUrl + "index.jsf"); > } > }) > .inspect(new Inspection() { > private static final long serialVersionUID = 1L; > @AfterPhase(RENDER_RESPONSE) > public void initial_state_havent_changed_yet() { > assertEquals("John", "John"); > } > } > ); > } > } > {code} > {code} > Stacktrace: > org.jboss.arquillian.warp.exception.ClientWarpExecutionException: enriching request failed; caused by: > javassist.NotFoundException: StudentTest$1 > at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpRequestEnrichmentService.enrichRequest(DefaultHttpRequestEnrichmentService.java:133) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.enrichRequest(EnrichmentObserver.java:85) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryEnrichRequest(EnrichmentObserver.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.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.DefaultHttpRequestEnrichmentFilter.filter(DefaultHttpRequestEnrichmentFilter.java:50) > at org.jboss.arquillian.warp.impl.client.proxy.DefaultProxyService$2.performInContext(DefaultProxyService.java:99) > at org.jboss.arquillian.warp.impl.client.proxy.DefaultProxyService$2.performInContext(DefaultProxyService.java:96) > at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.performInContext(Contextualizer.java:54) > at org.jboss.arquillian.warp.impl.client.proxy.DefaultProxyService$3.filter(DefaultProxyService.java:108) > at org.littleshoot.proxy.ProxyHttpRequestEncoder.encode(ProxyHttpRequestEncoder.java:75) > at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.doEncode(OneToOneEncoder.java:66) > at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:59) > at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) > at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784) > at org.jboss.netty.channel.SimpleChannelHandler.writeRequested(SimpleChannelHandler.java:292) > at org.jboss.netty.channel.SimpleChannelHandler.handleDownstream(SimpleChannelHandler.java:254) > at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) > at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582) > at org.jboss.netty.channel.Channels.write(Channels.java:704) > at org.jboss.netty.channel.Channels.write(Channels.java:671) > at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:248) > at org.littleshoot.proxy.HttpRequestHandler$1OnConnect.onConnect(HttpRequestHandler.java:407) > at org.littleshoot.proxy.HttpRequestHandler$1LocalChannelFutureListener.operationComplete(HttpRequestHandler.java:488) > at org.jboss.netty.channel.DefaultChannelFuture.notifyListener(DefaultChannelFuture.java:427) > at org.jboss.netty.channel.DefaultChannelFuture.addListener(DefaultChannelFuture.java:145) > at org.littleshoot.proxy.HttpRequestHandler.processRequest(HttpRequestHandler.java:539) > at org.littleshoot.proxy.HttpRequestHandler.messageReceived(HttpRequestHandler.java:276) > at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) > at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) > at org.jboss.netty.channel.SimpleChannelHandler.messageReceived(SimpleChannelHandler.java:142) > at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88) > at org.jboss.netty.handler.timeout.IdleStateAwareChannelHandler.handleUpstream(IdleStateAwareChannelHandler.java:36) > at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) > at org.jboss.netty.handler.timeout.IdleStateHandler.messageReceived(IdleStateHandler.java:294) > at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) > at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) > at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:459) > at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:536) > at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:435) > at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) > at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) > at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) > at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107) > at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) > at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88) > at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) > at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) > at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:722) > Caused by: java.lang.RuntimeException: Could not transform and replicate class class java.util.Arrays$ArrayList: > Unable to transform inspection StudentTest$1: > StudentTest$1 > at org.jboss.arquillian.warp.impl.shared.RequestPayload.writeExternal(RequestPayload.java:113) > at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1443) > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1414) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) > at org.jboss.arquillian.warp.impl.utils.SerializationUtils.serializeToBytes(SerializationUtils.java:38) > at org.jboss.arquillian.warp.impl.utils.SerializationUtils.serializeToBase64(SerializationUtils.java:59) > at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpRequestEnrichmentService.enrichRequest(DefaultHttpRequestEnrichmentService.java:125) > ... 76 more > Caused by: org.jboss.arquillian.warp.impl.client.transformation.InspectionTransformationException: Unable to transform inspection StudentTest$1: > StudentTest$1 > at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.transform(TransformedInspection.java:90) > at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.(TransformedInspection.java:57) > at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.(TransformedInspection.java:49) > at org.jboss.arquillian.warp.impl.shared.RequestPayload.writeExternal(RequestPayload.java:107) > ... 83 more > Caused by: javassist.NotFoundException: StudentTest$1 > at javassist.ClassPool.getAndRename(ClassPool.java:387) > at org.jboss.arquillian.warp.impl.client.transformation.TransformedInspection.transform(TransformedInspection.java:65) > ... 86 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Dec 11 09:00:39 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 11 Dec 2013 09:00:39 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1242) Warp: test exception thrown during Proxy processing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1242: ---------------------------- Description: We should test what happens when Proxy fails, and make sure the errors are handled properly. > Warp: test exception thrown during Proxy processing > --------------------------------------------------- > > Key: ARQ-1242 > URL: https://issues.jboss.org/browse/ARQ-1242 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: warp_1.0.0.Beta1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > We should test what happens when Proxy fails, > and make sure the errors are handled properly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Dec 11 09:00:39 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 11 Dec 2013 09:00:39 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1242) Warp: test exception thrown during Proxy processing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930348#comment-12930348 ] Luk?? Fry? commented on ARQ-1242: --------------------------------- I think issues on proxy might cause tests to freeze. > Warp: test exception thrown during Proxy processing > --------------------------------------------------- > > Key: ARQ-1242 > URL: https://issues.jboss.org/browse/ARQ-1242 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: warp_1.0.0.Beta1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > We should test what happens when Proxy fails, > and make sure the errors are handled properly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Dec 11 09:00:39 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 11 Dec 2013 09:00:39 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1242) Warp: test exception thrown during Proxy processing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1242: ---------------------------- Fix Version/s: warp_1.0.0.Alpha6 (was: warp_1.0.0.Beta1) > Warp: test exception thrown during Proxy processing > --------------------------------------------------- > > Key: ARQ-1242 > URL: https://issues.jboss.org/browse/ARQ-1242 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: warp_1.0.0.Alpha6 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > We should test what happens when Proxy fails, > and make sure the errors are handled properly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Dec 11 09:32:35 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 11 Dec 2013 09:32:35 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1498) Warp: get frozen when testing RichFaces FileUpload In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1498: ---------------------------- Fix Version/s: warp_1.0.0.Alpha6 (was: warp_1.0.0.Beta1) > Warp: get frozen when testing RichFaces FileUpload > -------------------------------------------------- > > Key: ARQ-1498 > URL: https://issues.jboss.org/browse/ARQ-1498 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha4 > Reporter: Luk?? Fry? > Priority: Critical > Fix For: warp_1.0.0.Alpha6 > > > Upstream issue: RF-13217 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Dec 11 10:54:33 2013 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 11 Dec 2013 10:54:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1321) Support for HTTPS in URLs injected with @ArquillianResource In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930428#comment-12930428 ] Karel Piwko commented on ARQ-1321: ---------------------------------- Maybe @OverProtocol could be reused? Like @ArquillianResource @OverProtocol("https"/enum) URL url; IIf http/https is not a protocol (@Protocol) but we want to name it *scheme*, maybe @UriScheme(string/enum/whatever) or @Scheme(string/enum/whatever)? This goes in hand with concept of qualifier, plus will support other schemes, like *and-activity://* for Selendroid native app testing. It would be a responsibility of container to be able to provide URI with given scheme. > Support for HTTPS in URLs injected with @ArquillianResource > ----------------------------------------------------------- > > Key: ARQ-1321 > URL: https://issues.jboss.org/browse/ARQ-1321 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Samuel Santos > Assignee: Samuel Santos > > When injecting an URL like the following: > {code:java} > @ArquillianResource URL url; > {code} > HTTP protocol will always be used. This happens because "http" is hard-coded in {{URLResourceProvider}}. > Vineet Reynolds suggested that we can create the type {{SecureUrl}} and a {{SecureUrlResourceProvider}} to allow us to use HTTPS: > {code:java} > @ArquillianResource SecureUrl url; > {code} > Any comment? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Dec 11 17:16:35 2013 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Wed, 11 Dec 2013 17:16:35 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1606) Support deploymentExportPath to export Exploded In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1606: ---------------------------------- Summary: Support deploymentExportPath to export Exploded Key: ARQ-1606 URL: https://issues.jboss.org/browse/ARQ-1606 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.1.2.Final Reporter: Aslak Knutsen Currently deploymentExportPath will export a Zipped file, but the reason for exporting it is to see the content. Allow to export as exploded. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Dec 11 18:42:32 2013 From: issues at jboss.org (Samuel Santos (JIRA)) Date: Wed, 11 Dec 2013 18:42:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1321) Support for HTTPS in URLs injected with @ArquillianResource In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930565#comment-12930565 ] Samuel Santos commented on ARQ-1321: ------------------------------------ Hi [~kpiwko], I had the opportunity to discuss this topic with [~aslak] at Devoxx and we came up to the same conclusion. My preference goes with @UriScheme(SchemeName.HTTPS) . I can update the PR at GitHub to reflect this. [~aslak], WDYT? > Support for HTTPS in URLs injected with @ArquillianResource > ----------------------------------------------------------- > > Key: ARQ-1321 > URL: https://issues.jboss.org/browse/ARQ-1321 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Samuel Santos > Assignee: Samuel Santos > > When injecting an URL like the following: > {code:java} > @ArquillianResource URL url; > {code} > HTTP protocol will always be used. This happens because "http" is hard-coded in {{URLResourceProvider}}. > Vineet Reynolds suggested that we can create the type {{SecureUrl}} and a {{SecureUrlResourceProvider}} to allow us to use HTTPS: > {code:java} > @ArquillianResource SecureUrl url; > {code} > Any comment? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Dec 12 10:00:36 2013 From: issues at jboss.org (Fred Bricon (JIRA)) Date: Thu, 12 Dec 2013 10:00:36 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1607) Please avoid using arquillian.launch files, it makes Eclipse generate error logs In-Reply-To: References: Message-ID: Fred Bricon created ARQ-1607: -------------------------------- Summary: Please avoid using arquillian.launch files, it makes Eclipse generate error logs Key: ARQ-1607 URL: https://issues.jboss.org/browse/ARQ-1607 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: Eclipse Reporter: Fred Bricon Priority: Minor When imported in Eclipse, projects containing arquillian.launch files make Eclipse barf as it expects a valid Eclipse Launch configuration xml file. It's just an error in the .metadata/.log, but the sight of such ugly stacktraces could be frightening/annoying for some {noformat} !MESSAGE org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Contenu non autoris? dans le prologue. occurred while reading launch configuration file: D:\tmp\arquillian-examples\arquillian-persistence-tutorial\target\test-classes\arquillian.launch. !STACK 0 org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Contenu non autoris? dans le prologue. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:441) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1388) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:998) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:607) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:489) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:835) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:237) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:300) at org.eclipse.debug.internal.core.LaunchManager.createInfoFromXML(LaunchManager.java:929) at org.eclipse.debug.internal.core.LaunchManager.getInfo(LaunchManager.java:1353) at org.eclipse.debug.internal.core.LaunchConfiguration.getInfo(LaunchConfiguration.java:453) at org.eclipse.debug.internal.core.LaunchConfiguration.getType(LaunchConfiguration.java:617) at org.eclipse.debug.internal.core.LaunchManager.isValid(LaunchManager.java:2081) at org.eclipse.debug.internal.core.LaunchManager.launchConfigurationAdded(LaunchManager.java:2104) at org.eclipse.debug.internal.core.LaunchManager$LaunchManagerVisitor.visit(LaunchManager.java:382) {noformat} >From IRC {quote} (15:46:37) fbricon: hey aslak, I'm looking at a some maven projects containing some arquillian.launch files (15:47:18) fbricon: eclipse treats these as Launch configuration files and complains they're malformed xml (15:47:38) fbricon: do the files need to be .launch? 15:47:58) aslak: fbricon hehe yea.. noticed that as well.. (15:48:22) aslak: it ended up being called arquillian.launch because that's the name of the -D property that does the same (15:48:50) aslak: fbricon could you file an issue on this.. I'll add support for arquillian.launch.properties or arquillian-launch or similar {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Dec 12 10:52:33 2013 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 12 Dec 2013 10:52:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1603) tmpDir specification should allow to be without trailing slash In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930822#comment-12930822 ] Stefan Miklosovic commented on ARQ-1603: ---------------------------------------- https://github.com/arquillian/arquillian-droidium/commit/8913b9930edb18c3e8b71a7a68d6d0f605560437 > tmpDir specification should allow to be without trailing slash > -------------------------------------------------------------- > > Key: ARQ-1603 > URL: https://issues.jboss.org/browse/ARQ-1603 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > > *Given*: > I define tmpDir like "C:\temp" or /tmp > *Then*: > Droidium creates a temp directory like C:\temp-1223-1454-1245-12545 > *Expect*: > I expect directory to be rather C:\temp\1223-1454-1245-12545 > Current behavior is problematic as it requires user to be slash aware as otherwise he might want to create a directory in tree hierarchy where elevated permissions are needed. > Implemenation note: > new File(File parent, String childPath) would be the best way how to handle this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Dec 16 08:22:32 2013 From: issues at jboss.org (Robert Panzer (JIRA)) Date: Mon, 16 Dec 2013 08:22:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1608) Invoke extensions related to AnnotationDeploymentScenarioGenerator in order of deployments In-Reply-To: References: Message-ID: Robert Panzer created ARQ-1608: ---------------------------------- Summary: Invoke extensions related to AnnotationDeploymentScenarioGenerator in order of deployments Key: ARQ-1608 URL: https://issues.jboss.org/browse/ARQ-1608 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.1.2.Final Environment: Win7, Java 6 Reporter: Robert Panzer Currently there is no order in which for example ProtocolArchiveProcessors are called in case a test class provides multiple deployments. It would be nice if the extension related to the AnnotationDeploymentScenarioGenerator were called in the same order. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Dec 16 08:38:33 2013 From: issues at jboss.org (Robert Panzer (JIRA)) Date: Mon, 16 Dec 2013 08:38:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1608) Invoke extensions related to AnnotationDeploymentScenarioGenerator in order of deployments In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931817#comment-12931817 ] Robert Panzer commented on ARQ-1608: ------------------------------------ Just filed a PR: https://github.com/arquillian/arquillian-core/pull/58 > Invoke extensions related to AnnotationDeploymentScenarioGenerator in order of deployments > ------------------------------------------------------------------------------------------ > > Key: ARQ-1608 > URL: https://issues.jboss.org/browse/ARQ-1608 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.2.Final > Environment: Win7, Java 6 > Reporter: Robert Panzer > > Currently there is no order in which for example ProtocolArchiveProcessors are called in case a test class provides multiple deployments. > It would be nice if the extension related to the AnnotationDeploymentScenarioGenerator were called in the same order. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Dec 17 03:26:33 2013 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 17 Dec 2013 03:26:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1600) ProcessExecutor might get stuck on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1600: ----------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Karel Piwko Fix Version/s: droidium_1.0.0.Alpha4 Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-droidium/commit/5dc4d2b21a4466e932a4d2adf70082a37b56dbb9 > ProcessExecutor might get stuck on Windows > ------------------------------------------- > > Key: ARQ-1600 > URL: https://issues.jboss.org/browse/ARQ-1600 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Blocker > Fix For: droidium_1.0.0.Alpha4 > > > Current execution of external process on Windows might lead to following issues, causing process deadlock: > 1/ Process stdin is not closed if no longer needed > 2/ Process stdout and stderr never reach EOF > This behavior is observed when a .bat file file is executed on Windows. This behavior is caused by missing file descriptors to underlying process spawned by bat file. > Implementation note: There are two ways how to resolve the issue. > * read output stream and consider them finished if specific message is encountered > * unwrap bat execution and execute directly underlying command -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Dec 17 03:26:33 2013 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 17 Dec 2013 03:26:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1602) Emulator process returns immediately on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1602: ----------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Karel Piwko Fix Version/s: droidium_1.0.0.Alpha4 Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-droidium/commit/ef05e42417241c9aedb49fa93e5826cba619e84c > Emulator process returns immediately on Windows > ----------------------------------------------- > > Key: ARQ-1602 > URL: https://issues.jboss.org/browse/ARQ-1602 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Critical > Fix For: droidium_1.0.0.Alpha4 > > > Changes introduced in ARQ-1583 are not compatible with Windows, where emulator.exe spawns another process itself and returns immediately. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Dec 17 03:26:33 2013 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 17 Dec 2013 03:26:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1601) adb is not found on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1601: ----------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Karel Piwko Fix Version/s: droidium_1.0.0.Alpha4 Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-droidium/commit/d1494c0b3b8edb4e37ec397088fe34a623530dbf > adb is not found on Windows > --------------------------- > > Key: ARQ-1601 > URL: https://issues.jboss.org/browse/ARQ-1601 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Critical > Fix For: droidium_1.0.0.Alpha4 > > > Current logic for searching tool location does not work correctly on windows. > For instance, setup is not able to find adb if arquillian.xml file contains androidHome with backslashes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Dec 17 03:28:32 2013 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 17 Dec 2013 03:28:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1603) tmpDir specification should allow to be without trailing slash In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1603. ------------------------------ Assignee: Stefan Miklosovic Fix Version/s: droidium_1.0.0.Alpha4 Resolution: Done > tmpDir specification should allow to be without trailing slash > -------------------------------------------------------------- > > Key: ARQ-1603 > URL: https://issues.jboss.org/browse/ARQ-1603 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha3 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha4 > > > *Given*: > I define tmpDir like "C:\temp" or /tmp > *Then*: > Droidium creates a temp directory like C:\temp-1223-1454-1245-12545 > *Expect*: > I expect directory to be rather C:\temp\1223-1454-1245-12545 > Current behavior is problematic as it requires user to be slash aware as otherwise he might want to create a directory in tree hierarchy where elevated permissions are needed. > Implemenation note: > new File(File parent, String childPath) would be the best way how to handle this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Dec 18 09:43:32 2013 From: issues at jboss.org (Jan Dosoudil (JIRA)) Date: Wed, 18 Dec 2013 09:43:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-416) @InFrame duplicitly switches to iframe with fragment method In-Reply-To: References: Message-ID: Jan Dosoudil created ARQGRA-416: ----------------------------------- Summary: @InFrame duplicitly switches to iframe with fragment method Key: ARQGRA-416 URL: https://issues.jboss.org/browse/ARQGRA-416 Project: Arquillian Graphene Issue Type: Bug Affects Versions: 2.0.0.Final Reporter: Jan Dosoudil {code} public class Fragment { @FindBy(id="button") private WebElement button; public void clickButton() { button.click(); } public WebElement getButton() { return button; } } {code} {code} @RunWith(Arquillian.class) @RunAsClient public class Test { //... @FindBy(id="content") @InFrame(nameOrId="frame") private Fragment Fragment; @Test public void testWebElement() { fragment.getButton().click(); //PASS } @Test public void testMethod() { fragment.clickButton(); //FAIL } } {code} Exception is: org.openqa.selenium.NoSuchFrameException: Unable to locate frame: frame -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Dec 18 10:37:33 2013 From: issues at jboss.org (=?UTF-8?Q?Oliver_Ki=C5=A1=C5=A1_=28JIRA=29?=) Date: Wed, 18 Dec 2013 10:37:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1609) Allow setting IE driver path in arquillian.xml configuration In-Reply-To: References: Message-ID: Oliver Ki?? created ARQ-1609: -------------------------------- Summary: 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 From issues at jboss.org Wed Dec 18 10:39:32 2013 From: issues at jboss.org (=?UTF-8?Q?Oliver_Ki=C5=A1=C5=A1_=28JIRA=29?=) Date: Wed, 18 Dec 2013 10:39:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1609) Allow setting IE driver path in arquillian.xml configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Ki?? updated ARQ-1609: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-drone/pull/31 > 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 From issues at jboss.org Thu Dec 19 11:18:32 2013 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 19 Dec 2013 11:18:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1609) Allow setting IE driver path in arquillian.xml configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932681#comment-12932681 ] Karel Piwko commented on ARQ-1609: ---------------------------------- Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/7ccc545108b5b6b538582295530261827e7b2fe3 > 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 From issues at jboss.org Thu Dec 19 11:20:33 2013 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 19 Dec 2013 11:20:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1609) Allow setting IE driver path in arquillian.xml configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko 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 From issues at jboss.org Thu Dec 19 11:20:39 2013 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 19 Dec 2013 11:20:39 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1609) Allow setting IE driver path in arquillian.xml configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932684#comment-12932684 ] 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 From issues at jboss.org Thu Dec 19 11:22:33 2013 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 19 Dec 2013 11:22:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1610) Update Selenium to 2.39.0 In-Reply-To: References: Message-ID: 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 From issues at jboss.org Fri Dec 20 04:18:35 2013 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Fri, 20 Dec 2013 04:18:35 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1610) Update Selenium to 2.39.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko 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/60b3428a354048692b35d0a18ea1afb5908a760b > 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 From issues at jboss.org Fri Dec 20 17:11:32 2013 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 20 Dec 2013 17:11:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933006#comment-12933006 ] 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 From issues at jboss.org Sun Dec 22 08:35:32 2013 From: issues at jboss.org (Bernard Labno (JIRA)) Date: Sun, 22 Dec 2013 08:35:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1082) Allow to provide external data sources on the SPI level. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933051#comment-12933051 ] 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 From issues at jboss.org Mon Dec 30 08:51:33 2013 From: issues at jboss.org (Michel Graciano (JIRA)) Date: Mon, 30 Dec 2013 08:51:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1444) Oracle does not support query delimiter inside statements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933275#comment-12933275 ] 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 From issues at jboss.org Mon Dec 30 08:53:32 2013 From: issues at jboss.org (Michel Graciano (JIRA)) Date: Mon, 30 Dec 2013 08:53:32 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1444) Oracle does not support query delimiter inside statements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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 From issues at jboss.org Mon Dec 30 11:01:33 2013 From: issues at jboss.org (=?UTF-8?Q?Andr=C3=A9_Pinheiro_=28JIRA=29?=) Date: Mon, 30 Dec 2013 11:01:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1611) Arquillian doesn't handle Glassfish REST API redirect In-Reply-To: References: Message-ID: 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