From issues at jboss.org Thu May 1 01:27:56 2014 From: issues at jboss.org (William Crowell (JIRA)) Date: Thu, 1 May 2014 01:27:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1769) org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964870#comment-12964870 ] William Crowell commented on ARQ-1769: -------------------------------------- More information on this. I switched to Arquillian Core 1.1.4, Drone 2.0.0.Alpha1, Warp 1.0.0.Alpha6 and HtmlUnit 2.14 but I am still using Arquillian Test SPI 1.1.3.Final. It appears this issue is not present in Warp 1.0.0.Alpha6, but whenever an anonymous inner class of type org.jboss.arquillian.warp.Inspection is created then Warp never returns and throws a WarpSynchronizationException. Here's the trace: (E) ActivateManager (I) ManagerActivationObserver.activateApplicationContext (E) BeforeRequest (I) RequestContextHandler.createRequestContext (O) LifecycleTestClassExecutor.beforeRequest (O) LifecycleManagerObserver.initializeLifecycleManagerAndInspectionRegistry (E) LifecycleManagerImpl (E) InspectionRegistry (E) ProcessHttpRequest (O) HttpRequestProcessor.processHttpRequest (E) ResponsePayload (E) AfterRequest (I) RequestContextHandler.destroyRequestContext (I) LifecycleTestClassExecutor.afterRequest (E) PassivateManager (I) ManagerActivationObserver.deactivateApplicationContext 2014-05-01 01:18:32,971 ERROR [com.gargoylesoftware.htmlunit.javascript.StrictErrorReporter] - runtimeError: message=[An invalid or illegal selector was specified (selector: '[id='j_idt33:j_idt35_menu'] .ui-menuitem:not(.ui-state-disabled)' error: Invalid selector: *[id="j_idt33:j_idt35_menu"] *.ui-menuitem:not(*.ui-state-disabled)).] sourceName=[http://localhost:8080/test/spring/javax.faces.resource/jquery/jquery.js?ln=primefaces] line=[21] lineSource=[null] lineOffset=[0] (E) AwaitResponse (O) WarpExecutionObserver.awaitResponse (E) WarpSynchronizationException (E) WarpSynchronizationException (E) CleanEnrichment (O) WarpExecutionObserver.cleanEnrichment (E) TestResult > org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > -------------------------------------------------------------------------- > > Key: ARQ-1769 > URL: https://issues.jboss.org/browse/ARQ-1769 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: warp_1.0.0.Alpha7, 1.1.3.Final, 1.1.4.Final > Environment: Windows 7 Enterprise SP1 64-bit > Reporter: William Crowell > > I am using the following: > Arquillian Core: 1.1.4.Final (as well as 1.1.3.Final) > Arquillian Drone: 1.2.4.Final (I've tried Drone 2 as well) > Arquillian Warp: 1.0.0.Alpha7 (as well as 1.0.0.Beta1-SNAPSHOT) > Arquillian Transaction: 1.0.1.Final > Arquillian Tomcat 7 Embedded Container using Tomcat 7.0.27: 1.0.0.Final-SNAPSHOT > Spring: 3.2.4.RELEASE > Spring Web: 3.2.2.RELEASE > Spring Security: 3.1.4.RELEASE > Spring WebFlow: 2.4.0.RC1 > PrimeFaces 3.4.2 > JUnit: 4.8.2 > Mojarra 2.1.17 > I am receiving this exception: > java.lang.IllegalStateException: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:69) > ... > 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.LifecycleTestClassExecutor.afterRequest(LifecycleTestClassExecutor.java:78) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.request.RequestContextHandler.handleRequestContext(RequestContextHandler.java:93) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:151) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:120) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:93) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:183) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192) > at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160) > at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) > at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) > at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > ... > Caused by: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl.checkUnbound(LifecycleManagerStoreImpl.java:126) > at org.jboss.arquillian.warp.spi.LifecycleManager.checkUnbound(LifecycleManager.java:158) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:67) > ... 74 more -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 6 04:41:56 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 6 May 2014 04:41:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-435) Graphene wait does not find @Qualified browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965697#comment-12965697 ] Luk?? Fry? commented on ARQGRA-435: ----------------------------------- What we could do here is detect how many drivers are being injected and if only one is used in test case, then we can switch a default browser quailifier from {{Default.class}} to {{}} such as {{BugReport.class}}. This sacrifices clarity for friendliness. > Graphene wait does not find @Qualified browser > ---------------------------------------------- > > Key: ARQGRA-435 > URL: https://issues.jboss.org/browse/ARQGRA-435 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Karel Piwko > Assignee: Juraj H?ska > Priority: Critical > Fix For: 2.0.3.Final > > > It is not possible to wait when browser is qualifiered: > {code} > package com.acme.example.test; > import java.lang.annotation.Retention; > import java.lang.annotation.RetentionPolicy; > import java.net.URL; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.drone.api.annotation.Drone; > import org.jboss.arquillian.drone.api.annotation.Qualifier; > import org.jboss.arquillian.graphene.Graphene; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.arquillian.test.api.ArquillianResource; > import org.jboss.shrinkwrap.api.Archive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > import org.openqa.selenium.WebDriver; > import org.openqa.selenium.WebElement; > import org.openqa.selenium.support.FindBy; > @RunWith(Arquillian.class) > public class GrapheneBugDroneTest { > @Drone > @BugReport > WebDriver driver; > @Deployment(testable = false) > public static Archive deployHtml5DemoApp() { > return Deployments.createDeployment(); > } > @ArquillianResource > URL url; > @FindBy(id = "name") > WebElement nameField; > @Test > public void addUser() throws Exception { > driver.get(url.toString()); > Graphene.waitGui(driver).until().element(nameField).is().present(); > Assert.assertTrue(true); > } > @Qualifier > @Retention(RetentionPolicy.RUNTIME) > public static @interface BugReport { > } > } > {code} > Wait *Graphene.waitGui(driver).until().element(nameField).is().present();* > fails with > {code} > java.lang.IllegalStateException: There is no context available for qualifier org.jboss.arquillian.drone.api.annotation.Default. Available contexts are [interface com.acme.example.test.GrapheneBugDroneTest$BugReport]. > at org.jboss.arquillian.graphene.context.GrapheneContextImpl$LazyContext.getContext(GrapheneContextImpl.java:302) > at org.jboss.arquillian.graphene.context.GrapheneContextImpl$LazyContext.getConfiguration(GrapheneContextImpl.java:234) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.waitGui(DefaultGrapheneRuntime.java:104) > at org.jboss.arquillian.graphene.Graphene.waitGui(Graphene.java:216) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy28.isDisplayed(Unknown Source) > at org.jboss.arquillian.graphene.condition.element.ElementIsPresent.check(ElementIsPresent.java:44) > at org.jboss.arquillian.graphene.condition.element.ElementIsPresent.check(ElementIsPresent.java:31) > at org.jboss.arquillian.graphene.condition.element.AbstractElementBooleanCondition.apply(AbstractElementBooleanCondition.java:52) > at org.jboss.arquillian.graphene.condition.element.AbstractElementBooleanCondition.apply(AbstractElementBooleanCondition.java:33) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:102) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.commit(WebDriverWaitImpl.java:110) > at org.jboss.arquillian.graphene.wait.IsNotElementBuilderImpl.present(IsNotElementBuilderImpl.java:47) > at com.acme.example.test.GrapheneBugDroneTest.addUser(GrapheneBugDroneTest.java:42) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:273) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:266) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:229) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:243) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:188) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:202) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:150) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) > {code} > Arquillian configuration: > * Core 1.1.4.Final > * Graphene 2.0.2.Final > * Drone 2.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 6 04:43:56 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 6 May 2014 04:43:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-435) Graphene wait does not find @Qualified browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965697#comment-12965697 ] Luk?? Fry? edited comment on ARQGRA-435 at 5/6/14 4:42 AM: ----------------------------------------------------------- What we could do here is detect how many drivers are being injected and if only one is used in test case, then we can switch a default browser quailifier from {{Default.class}} to {{}} such as {{BugReport.class}}. This sacrifices clarity/consistency for friendliness. was (Author: lfryc): What we could do here is detect how many drivers are being injected and if only one is used in test case, then we can switch a default browser quailifier from {{Default.class}} to {{}} such as {{BugReport.class}}. This sacrifices clarity for friendliness. > Graphene wait does not find @Qualified browser > ---------------------------------------------- > > Key: ARQGRA-435 > URL: https://issues.jboss.org/browse/ARQGRA-435 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Karel Piwko > Assignee: Juraj H?ska > Priority: Critical > Fix For: 2.0.3.Final > > > It is not possible to wait when browser is qualifiered: > {code} > package com.acme.example.test; > import java.lang.annotation.Retention; > import java.lang.annotation.RetentionPolicy; > import java.net.URL; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.drone.api.annotation.Drone; > import org.jboss.arquillian.drone.api.annotation.Qualifier; > import org.jboss.arquillian.graphene.Graphene; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.arquillian.test.api.ArquillianResource; > import org.jboss.shrinkwrap.api.Archive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > import org.openqa.selenium.WebDriver; > import org.openqa.selenium.WebElement; > import org.openqa.selenium.support.FindBy; > @RunWith(Arquillian.class) > public class GrapheneBugDroneTest { > @Drone > @BugReport > WebDriver driver; > @Deployment(testable = false) > public static Archive deployHtml5DemoApp() { > return Deployments.createDeployment(); > } > @ArquillianResource > URL url; > @FindBy(id = "name") > WebElement nameField; > @Test > public void addUser() throws Exception { > driver.get(url.toString()); > Graphene.waitGui(driver).until().element(nameField).is().present(); > Assert.assertTrue(true); > } > @Qualifier > @Retention(RetentionPolicy.RUNTIME) > public static @interface BugReport { > } > } > {code} > Wait *Graphene.waitGui(driver).until().element(nameField).is().present();* > fails with > {code} > java.lang.IllegalStateException: There is no context available for qualifier org.jboss.arquillian.drone.api.annotation.Default. Available contexts are [interface com.acme.example.test.GrapheneBugDroneTest$BugReport]. > at org.jboss.arquillian.graphene.context.GrapheneContextImpl$LazyContext.getContext(GrapheneContextImpl.java:302) > at org.jboss.arquillian.graphene.context.GrapheneContextImpl$LazyContext.getConfiguration(GrapheneContextImpl.java:234) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.waitGui(DefaultGrapheneRuntime.java:104) > at org.jboss.arquillian.graphene.Graphene.waitGui(Graphene.java:216) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy28.isDisplayed(Unknown Source) > at org.jboss.arquillian.graphene.condition.element.ElementIsPresent.check(ElementIsPresent.java:44) > at org.jboss.arquillian.graphene.condition.element.ElementIsPresent.check(ElementIsPresent.java:31) > at org.jboss.arquillian.graphene.condition.element.AbstractElementBooleanCondition.apply(AbstractElementBooleanCondition.java:52) > at org.jboss.arquillian.graphene.condition.element.AbstractElementBooleanCondition.apply(AbstractElementBooleanCondition.java:33) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:102) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.commit(WebDriverWaitImpl.java:110) > at org.jboss.arquillian.graphene.wait.IsNotElementBuilderImpl.present(IsNotElementBuilderImpl.java:47) > at com.acme.example.test.GrapheneBugDroneTest.addUser(GrapheneBugDroneTest.java:42) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:273) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:266) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:229) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:243) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:188) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:202) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:150) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) > {code} > Arquillian configuration: > * Core 1.1.4.Final > * Graphene 2.0.2.Final > * Drone 2.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 6 04:45:57 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 6 May 2014 04:45:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-435) Graphene wait does not find @Qualified browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965697#comment-12965697 ] Luk?? Fry? edited comment on ARQGRA-435 at 5/6/14 4:44 AM: ----------------------------------------------------------- What we could do here is detect how many drivers are being injected and if only one is used in test case, then we can switch a default browser quailifier from {{Default.class}} to {{}} such as {{BugReport.class}}. This sacrifices clarity/consistency for friendliness. Note: this is just brain-storming, not a definite conclusion. :-) Wdyt [~smikloso], [~jhuska], [~kpiwko] ? was (Author: lfryc): What we could do here is detect how many drivers are being injected and if only one is used in test case, then we can switch a default browser quailifier from {{Default.class}} to {{}} such as {{BugReport.class}}. This sacrifices clarity/consistency for friendliness. > Graphene wait does not find @Qualified browser > ---------------------------------------------- > > Key: ARQGRA-435 > URL: https://issues.jboss.org/browse/ARQGRA-435 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Karel Piwko > Assignee: Juraj H?ska > Priority: Critical > Fix For: 2.0.3.Final > > > It is not possible to wait when browser is qualifiered: > {code} > package com.acme.example.test; > import java.lang.annotation.Retention; > import java.lang.annotation.RetentionPolicy; > import java.net.URL; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.drone.api.annotation.Drone; > import org.jboss.arquillian.drone.api.annotation.Qualifier; > import org.jboss.arquillian.graphene.Graphene; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.arquillian.test.api.ArquillianResource; > import org.jboss.shrinkwrap.api.Archive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > import org.openqa.selenium.WebDriver; > import org.openqa.selenium.WebElement; > import org.openqa.selenium.support.FindBy; > @RunWith(Arquillian.class) > public class GrapheneBugDroneTest { > @Drone > @BugReport > WebDriver driver; > @Deployment(testable = false) > public static Archive deployHtml5DemoApp() { > return Deployments.createDeployment(); > } > @ArquillianResource > URL url; > @FindBy(id = "name") > WebElement nameField; > @Test > public void addUser() throws Exception { > driver.get(url.toString()); > Graphene.waitGui(driver).until().element(nameField).is().present(); > Assert.assertTrue(true); > } > @Qualifier > @Retention(RetentionPolicy.RUNTIME) > public static @interface BugReport { > } > } > {code} > Wait *Graphene.waitGui(driver).until().element(nameField).is().present();* > fails with > {code} > java.lang.IllegalStateException: There is no context available for qualifier org.jboss.arquillian.drone.api.annotation.Default. Available contexts are [interface com.acme.example.test.GrapheneBugDroneTest$BugReport]. > at org.jboss.arquillian.graphene.context.GrapheneContextImpl$LazyContext.getContext(GrapheneContextImpl.java:302) > at org.jboss.arquillian.graphene.context.GrapheneContextImpl$LazyContext.getConfiguration(GrapheneContextImpl.java:234) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.waitGui(DefaultGrapheneRuntime.java:104) > at org.jboss.arquillian.graphene.Graphene.waitGui(Graphene.java:216) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy28.isDisplayed(Unknown Source) > at org.jboss.arquillian.graphene.condition.element.ElementIsPresent.check(ElementIsPresent.java:44) > at org.jboss.arquillian.graphene.condition.element.ElementIsPresent.check(ElementIsPresent.java:31) > at org.jboss.arquillian.graphene.condition.element.AbstractElementBooleanCondition.apply(AbstractElementBooleanCondition.java:52) > at org.jboss.arquillian.graphene.condition.element.AbstractElementBooleanCondition.apply(AbstractElementBooleanCondition.java:33) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:102) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.commit(WebDriverWaitImpl.java:110) > at org.jboss.arquillian.graphene.wait.IsNotElementBuilderImpl.present(IsNotElementBuilderImpl.java:47) > at com.acme.example.test.GrapheneBugDroneTest.addUser(GrapheneBugDroneTest.java:42) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:273) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:266) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:229) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:243) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:188) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:202) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:150) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) > {code} > Arquillian configuration: > * Core 1.1.4.Final > * Graphene 2.0.2.Final > * Drone 2.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 6 05:41:57 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 6 May 2014 05:41:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-436) @FindByJQuery reference from root does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-436: ------------------------------ Fix Version/s: 2.0-Tracking > @FindByJQuery reference from root does not work > ----------------------------------------------- > > Key: ARQGRA-436 > URL: https://issues.jboss.org/browse/ARQGRA-436 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Fix For: 2.0-Tracking > > > Referencing of the elements annotated with {{@FindByJQuery}} from the root does not work. > It is not working because we are searching for an element with the user submitted locator, e.g. {{html:div:visible}}. We should cut the {{html}}, {{body}} or {{head}} from the user defined selector. > It should be done on [this|https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/findby/ByJQueryImpl.java#L65] line. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 6 05:43:57 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 6 May 2014 05:43:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-436) @FindByJQuery reference from root does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965711#comment-12965711 ] Luk?? Fry? commented on ARQGRA-436: ----------------------------------- [~jhuska] I believe we already take this case into account: https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/findby/ByJQueryImpl.java#L92 Could you debug this case and see what's wrong? > @FindByJQuery reference from root does not work > ----------------------------------------------- > > Key: ARQGRA-436 > URL: https://issues.jboss.org/browse/ARQGRA-436 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Fix For: 2.0-Tracking > > > Referencing of the elements annotated with {{@FindByJQuery}} from the root does not work. > It is not working because we are searching for an element with the user submitted locator, e.g. {{html:div:visible}}. We should cut the {{html}}, {{body}} or {{head}} from the user defined selector. > It should be done on [this|https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/findby/ByJQueryImpl.java#L65] line. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 6 05:53:59 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 6 May 2014 05:53:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1432) Make Warp Airplane travel friendly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965716#comment-12965716 ] Luk?? Fry? commented on ARQ-1432: --------------------------------- Rafael, just trying to find a cause: is that possible that if you are running your tests, the browser the test uses has a company proxy configured? Then the browser may want to reach the company proxy first - it suppose to contact Warp's proxy as a target HTTP server (from browser's perspective), but it can't since it's running on localhost. I know that browsers shouldn't reach HTTP proxies for localhost requests. > Make Warp Airplane travel friendly > ---------------------------------- > > Key: ARQ-1432 > URL: https://issues.jboss.org/browse/ARQ-1432 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha3 > Reporter: Aslak Knutsen > Fix For: warp_1.0.0.Beta1 > > Attachments: test-output.txt > > > When not connected to a network Warp throws this exception: > {code} > java.net.SocketException: Unresolved address > at java.net.DatagramSocket.connect(DatagramSocket.java:477) > at org.littleshoot.proxy.NetworkUtils.getLocalHostViaUdp(NetworkUtils.java:55) > at org.littleshoot.proxy.NetworkUtils.getLocalHost(NetworkUtils.java:46) > at org.littleshoot.proxy.ProxyUtils.(ProxyUtils.java:67) > at org.littleshoot.proxy.LittleProxyConfig.(LittleProxyConfig.java:44) > at org.jboss.arquillian.warp.impl.client.proxy.DefaultProxyService.startProxy(DefaultProxyService.java:75) > at org.jboss.arquillian.warp.impl.client.proxy.DefaultProxyService.startProxy(DefaultProxyService.java:46) > at org.jboss.arquillian.warp.impl.client.proxy.ProxyObserver.startProxy(ProxyObserver.java:71) > 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.warp.impl.client.proxy.ProxyObserver.requireProxy(ProxyObserver.java:66) > 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.warp.impl.client.proxy.ProxyURLProvider.getProxyUrl(ProxyURLProvider.java:82) > at org.jboss.arquillian.warp.impl.client.proxy.ProxyURLProvider.lookup(ProxyURLProvider.java:71) > at org.jboss.arquillian.test.impl.enricher.resource.ArquillianResourceTestEnricher.lookup(ArquillianResourceTestEnricher.java:112) > at org.jboss.arquillian.test.impl.enricher.resource.ArquillianResourceTestEnricher.enrich(ArquillianResourceTestEnricher.java:57) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java: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.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) > 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.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > 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.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: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.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.before(EventTestRunnerAdaptor.java:95) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:222) > 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$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > 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:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 6 06:37:56 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 6 May 2014 06:37:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1645) persistence doesn't support multiple datasources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1645: -------------------------------- Fix Version/s: (was: persistence_1.0.0.next) > persistence doesn't support multiple datasources > ------------------------------------------------ > > Key: ARQ-1645 > URL: https://issues.jboss.org/browse/ARQ-1645 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Romain Manni-Bucau > Assignee: Bartosz Majsak > > It is common to use multiple datsources (in fact all apps I'm working with does it) and ATM dbunit extension doesn't support multiple datsource init/asserts (UsingDataSet and ExpectedDataSet). > Would be great to get a plural version of @DataSource and @XDataSet -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 6 06:39:56 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 6 May 2014 06:39:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1228) Column metadata (data type) discarded when creating dataset from JSON In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1228: -------------------------------- Fix Version/s: (was: persistence_1.0.0.next) > Column metadata (data type) discarded when creating dataset from JSON > --------------------------------------------------------------------- > > Key: ARQ-1228 > URL: https://issues.jboss.org/browse/ARQ-1228 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: 1.0.0.Alpha5 > Reporter: Cyrill R??ttimann > Assignee: Cyrill R??ttimann > > The original bug was that the sorting (orderBy) did not work for datasets imported via JSON. Analysis on this showed, that the DBunit-Metadata which includes the Datatype for a column was not populated with correct data, but with DataType.UNKOWN. DBUnit's SortedTable then assumes String as the datatype and for example primary keys will not be sorted correctly. > The solution whould be to not ignore the datatype information delivered by Jackson, but put them into the DBUnit-Column instance(es). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 6 07:09:56 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 6 May 2014 07:09:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-435) Graphene wait does not find @Qualified browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965748#comment-12965748 ] Stefan Miklosovic commented on ARQGRA-435: ------------------------------------------ [~lfryc] sounds reasonable > Graphene wait does not find @Qualified browser > ---------------------------------------------- > > Key: ARQGRA-435 > URL: https://issues.jboss.org/browse/ARQGRA-435 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Karel Piwko > Assignee: Juraj H?ska > Priority: Critical > Fix For: 2.0.3.Final > > > It is not possible to wait when browser is qualifiered: > {code} > package com.acme.example.test; > import java.lang.annotation.Retention; > import java.lang.annotation.RetentionPolicy; > import java.net.URL; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.drone.api.annotation.Drone; > import org.jboss.arquillian.drone.api.annotation.Qualifier; > import org.jboss.arquillian.graphene.Graphene; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.arquillian.test.api.ArquillianResource; > import org.jboss.shrinkwrap.api.Archive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > import org.openqa.selenium.WebDriver; > import org.openqa.selenium.WebElement; > import org.openqa.selenium.support.FindBy; > @RunWith(Arquillian.class) > public class GrapheneBugDroneTest { > @Drone > @BugReport > WebDriver driver; > @Deployment(testable = false) > public static Archive deployHtml5DemoApp() { > return Deployments.createDeployment(); > } > @ArquillianResource > URL url; > @FindBy(id = "name") > WebElement nameField; > @Test > public void addUser() throws Exception { > driver.get(url.toString()); > Graphene.waitGui(driver).until().element(nameField).is().present(); > Assert.assertTrue(true); > } > @Qualifier > @Retention(RetentionPolicy.RUNTIME) > public static @interface BugReport { > } > } > {code} > Wait *Graphene.waitGui(driver).until().element(nameField).is().present();* > fails with > {code} > java.lang.IllegalStateException: There is no context available for qualifier org.jboss.arquillian.drone.api.annotation.Default. Available contexts are [interface com.acme.example.test.GrapheneBugDroneTest$BugReport]. > at org.jboss.arquillian.graphene.context.GrapheneContextImpl$LazyContext.getContext(GrapheneContextImpl.java:302) > at org.jboss.arquillian.graphene.context.GrapheneContextImpl$LazyContext.getConfiguration(GrapheneContextImpl.java:234) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.waitGui(DefaultGrapheneRuntime.java:104) > at org.jboss.arquillian.graphene.Graphene.waitGui(Graphene.java:216) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy28.isDisplayed(Unknown Source) > at org.jboss.arquillian.graphene.condition.element.ElementIsPresent.check(ElementIsPresent.java:44) > at org.jboss.arquillian.graphene.condition.element.ElementIsPresent.check(ElementIsPresent.java:31) > at org.jboss.arquillian.graphene.condition.element.AbstractElementBooleanCondition.apply(AbstractElementBooleanCondition.java:52) > at org.jboss.arquillian.graphene.condition.element.AbstractElementBooleanCondition.apply(AbstractElementBooleanCondition.java:33) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:102) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.commit(WebDriverWaitImpl.java:110) > at org.jboss.arquillian.graphene.wait.IsNotElementBuilderImpl.present(IsNotElementBuilderImpl.java:47) > at com.acme.example.test.GrapheneBugDroneTest.addUser(GrapheneBugDroneTest.java:42) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:273) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:266) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:229) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:243) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:188) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:202) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:150) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) > {code} > Arquillian configuration: > * Core 1.1.4.Final > * Graphene 2.0.2.Final > * Drone 2.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 6 07:17:58 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 6 May 2014 07:17:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-438) Using multiple qualifiers for @Page In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQGRA-438: ---------------------------------------- Summary: Using multiple qualifiers for @Page Key: ARQGRA-438 URL: https://issues.jboss.org/browse/ARQGRA-438 Project: Arquillian Graphene Issue Type: Enhancement Components: core Affects Versions: 2.1-Tracking Reporter: Stefan Miklosovic Priority: Optional In case I have one application deployed to multiple devices (apks to Android) and I use @Page abstraction, I end up with this: {code} @Drone @Mobile AndroidDriver mobile; @Drone @Tablet AndroidDriver tablet; @Page @Mobile SomePage mobilePage; @Page @Tablet SomePage tabletPage; {code} Event that page is same I have to declare it twice. It could be done as {code} @Page @Mobile @Tablet SomePage page; {code} In this case, there has to be some distinction between webdrivers and it seems this could be done on deployment level when you use @OperatesOnDeployment annotaion on webdriver injection. In case you have some test method which uses the same @OperatesOnDeployment value, Graphene will inject "right" driver to handle that @Page bean. Example: {code} @Drone @Tablet @OperatesOnDeployment("android_1") AndroidDriver tablet; @Drone @Mobile @OperatesOnDeployment("android_2") AndroidDriver mobile; @Page @Tablet @Mobile SomePage somePage; @Test @OperatesOnDeployment("android_1") public void test() { somePage will be backed by @Tablet browser } {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 6 07:41:57 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 6 May 2014 07:41:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-432) guardAjax does not work with XHR2 requests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-432: ------------------------------ Fix Version/s: 2.0-Tracking > guardAjax does not work with XHR2 requests > ------------------------------------------ > > Key: ARQGRA-432 > URL: https://issues.jboss.org/browse/ARQGRA-432 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Juraj H?ska > Fix For: 2.0-Tracking > > > {{guardAjax}} does not work correctly with XHR2 requests. The request is guarded correctly, but the callback once it is completed is not called. > The problem seems to be with {{onload}} (since XHR2) vs. {{onreadystatechange}} (since XHR1) callbacks. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 6 07:43:56 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 6 May 2014 07:43:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-432) guardAjax does not work with XHR2 requests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-432: ------------------------------ Priority: Critical (was: Major) > guardAjax does not work with XHR2 requests > ------------------------------------------ > > Key: ARQGRA-432 > URL: https://issues.jboss.org/browse/ARQGRA-432 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Juraj H?ska > Priority: Critical > Fix For: 2.0-Tracking > > > {{guardAjax}} does not work correctly with XHR2 requests. The request is guarded correctly, but the callback once it is completed is not called. > The problem seems to be with {{onload}} (since XHR2) vs. {{onreadystatechange}} (since XHR1) callbacks. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 6 07:43:56 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 6 May 2014 07:43:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-431) Case insensitive matcher In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-431: ------------------------------ Fix Version/s: 2.0-Tracking > Case insensitive matcher > ------------------------ > > Key: ARQGRA-431 > URL: https://issues.jboss.org/browse/ARQGRA-431 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Karel Piwko > Fix For: 2.0-Tracking > > > It is not possible to match text/attribute in case insensitive way. > {code} > Graphene.waitModel().until().element(notify).text(). > {code} > * .contains(String) > * .equals(String) > it should have equalsIgnoreCase as well. A regex matcher would be handy here as well. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 6 07:43:56 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 6 May 2014 07:43:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1013) Embedded weld integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1013: -------------------------------- Fix Version/s: persistence_1.0.0.next > Embedded weld integration > ------------------------- > > Key: ARQ-1013 > URL: https://issues.jboss.org/browse/ARQ-1013 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Trevor Baker > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > Attachments: sample.zip, sample.zip > > > Better integration with embedded weld. Developers still need to manually wire in JNDI initial context, datasource, jta, and hibernate. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 6 07:45:56 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 6 May 2014 07:45:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-431) Case insensitive matcher In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965762#comment-12965762 ] Luk?? Fry? commented on ARQGRA-431: ----------------------------------- +1 adding .equalsIgnoreCase(String), .matches(regexp) Karel, could you look into adding this capabilities? > Case insensitive matcher > ------------------------ > > Key: ARQGRA-431 > URL: https://issues.jboss.org/browse/ARQGRA-431 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Karel Piwko > Fix For: 2.0-Tracking > > > It is not possible to match text/attribute in case insensitive way. > {code} > Graphene.waitModel().until().element(notify).text(). > {code} > * .contains(String) > * .equals(String) > it should have equalsIgnoreCase as well. A regex matcher would be handy here as well. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 6 12:05:57 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 6 May 2014 12:05:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-439) Infer WebDriver context for @FindBy injections when there is only one qualified browser In-Reply-To: References: Message-ID: Juraj H?ska created ARQGRA-439: ---------------------------------- Summary: Infer WebDriver context for @FindBy injections when there is only one qualified browser Key: ARQGRA-439 URL: https://issues.jboss.org/browse/ARQGRA-439 Project: Arquillian Graphene Issue Type: Feature Request Components: core, ftest Affects Versions: 2.0.2.Final Reporter: Juraj H?ska When one is using qualified {{WebDriver}} instances, he needs to annotate also his {{WebElement}}, ... to distinguish in which context those elements should be resolved. This has to be done also when there is only one (though qualified) browser injected. Suppose: {code} @RunWith(Arquillian.class) public class GrapheneBugDroneTest { @Drone @BugReport WebDriver driver; @Deployment(testable = false) public static Archive deployHtml5DemoApp() { return Deployments.createDeployment(); } @ArquillianResource URL url; @FindBy(id = "name") @BugReport WebElement nameField; @Test public void addUser() throws Exception { driver.get(url.toString()); Graphene.waitGui(driver).until().element(nameField).is().present(); Assert.assertTrue(true); } @Qualifier @Retention(RetentionPolicy.RUNTIME) public static @interface BugReport { } } {code} Graphene can interfere which {{WebDriver}} instance was injected and act accordingly. The idea is also described [here|https://issues.jboss.org/browse/ARQGRA-435?focusedCommentId=12965697&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12965697]. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 6 12:09:56 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 6 May 2014 12:09:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-435) Graphene wait does not find @Qualified browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska resolved ARQGRA-435. -------------------------------- Resolution: Rejected [~kpiwko] and me came to the same conclusion in an offline meeting. I have created feature request to track this ARQGRA-439. Rejecting this issue as it is not a bug. > Graphene wait does not find @Qualified browser > ---------------------------------------------- > > Key: ARQGRA-435 > URL: https://issues.jboss.org/browse/ARQGRA-435 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Karel Piwko > Assignee: Juraj H?ska > Priority: Critical > Fix For: 2.0.3.Final > > > It is not possible to wait when browser is qualifiered: > {code} > package com.acme.example.test; > import java.lang.annotation.Retention; > import java.lang.annotation.RetentionPolicy; > import java.net.URL; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.drone.api.annotation.Drone; > import org.jboss.arquillian.drone.api.annotation.Qualifier; > import org.jboss.arquillian.graphene.Graphene; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.arquillian.test.api.ArquillianResource; > import org.jboss.shrinkwrap.api.Archive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > import org.openqa.selenium.WebDriver; > import org.openqa.selenium.WebElement; > import org.openqa.selenium.support.FindBy; > @RunWith(Arquillian.class) > public class GrapheneBugDroneTest { > @Drone > @BugReport > WebDriver driver; > @Deployment(testable = false) > public static Archive deployHtml5DemoApp() { > return Deployments.createDeployment(); > } > @ArquillianResource > URL url; > @FindBy(id = "name") > WebElement nameField; > @Test > public void addUser() throws Exception { > driver.get(url.toString()); > Graphene.waitGui(driver).until().element(nameField).is().present(); > Assert.assertTrue(true); > } > @Qualifier > @Retention(RetentionPolicy.RUNTIME) > public static @interface BugReport { > } > } > {code} > Wait *Graphene.waitGui(driver).until().element(nameField).is().present();* > fails with > {code} > java.lang.IllegalStateException: There is no context available for qualifier org.jboss.arquillian.drone.api.annotation.Default. Available contexts are [interface com.acme.example.test.GrapheneBugDroneTest$BugReport]. > at org.jboss.arquillian.graphene.context.GrapheneContextImpl$LazyContext.getContext(GrapheneContextImpl.java:302) > at org.jboss.arquillian.graphene.context.GrapheneContextImpl$LazyContext.getConfiguration(GrapheneContextImpl.java:234) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.waitGui(DefaultGrapheneRuntime.java:104) > at org.jboss.arquillian.graphene.Graphene.waitGui(Graphene.java:216) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy28.isDisplayed(Unknown Source) > at org.jboss.arquillian.graphene.condition.element.ElementIsPresent.check(ElementIsPresent.java:44) > at org.jboss.arquillian.graphene.condition.element.ElementIsPresent.check(ElementIsPresent.java:31) > at org.jboss.arquillian.graphene.condition.element.AbstractElementBooleanCondition.apply(AbstractElementBooleanCondition.java:52) > at org.jboss.arquillian.graphene.condition.element.AbstractElementBooleanCondition.apply(AbstractElementBooleanCondition.java:33) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:102) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.commit(WebDriverWaitImpl.java:110) > at org.jboss.arquillian.graphene.wait.IsNotElementBuilderImpl.present(IsNotElementBuilderImpl.java:47) > at com.acme.example.test.GrapheneBugDroneTest.addUser(GrapheneBugDroneTest.java:42) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:273) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:266) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:229) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:243) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:188) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:202) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:150) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) > {code} > Arquillian configuration: > * Core 1.1.4.Final > * Graphene 2.0.2.Final > * Drone 2.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 6 12:11:57 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 6 May 2014 12:11:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-435) Graphene wait does not find @Qualified browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965882#comment-12965882 ] Juraj H?ska commented on ARQGRA-435: ------------------------------------ [~smikloso] to your comment: https://issues.jboss.org/browse/ARQGRA-435?focusedCommentId=12961429&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12961429 I think that it is a different issue, which is connected with Graphene & Drone 2.x integration. Feel free to open another issue. I have tried to reproduce this with Graphene 2.0.2-SNAPSHOT (uses Drone 1.3.0.Final) and I have not reproduce it. > Graphene wait does not find @Qualified browser > ---------------------------------------------- > > Key: ARQGRA-435 > URL: https://issues.jboss.org/browse/ARQGRA-435 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Karel Piwko > Assignee: Juraj H?ska > Priority: Critical > Fix For: 2.0.3.Final > > > It is not possible to wait when browser is qualifiered: > {code} > package com.acme.example.test; > import java.lang.annotation.Retention; > import java.lang.annotation.RetentionPolicy; > import java.net.URL; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.drone.api.annotation.Drone; > import org.jboss.arquillian.drone.api.annotation.Qualifier; > import org.jboss.arquillian.graphene.Graphene; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.arquillian.test.api.ArquillianResource; > import org.jboss.shrinkwrap.api.Archive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > import org.openqa.selenium.WebDriver; > import org.openqa.selenium.WebElement; > import org.openqa.selenium.support.FindBy; > @RunWith(Arquillian.class) > public class GrapheneBugDroneTest { > @Drone > @BugReport > WebDriver driver; > @Deployment(testable = false) > public static Archive deployHtml5DemoApp() { > return Deployments.createDeployment(); > } > @ArquillianResource > URL url; > @FindBy(id = "name") > WebElement nameField; > @Test > public void addUser() throws Exception { > driver.get(url.toString()); > Graphene.waitGui(driver).until().element(nameField).is().present(); > Assert.assertTrue(true); > } > @Qualifier > @Retention(RetentionPolicy.RUNTIME) > public static @interface BugReport { > } > } > {code} > Wait *Graphene.waitGui(driver).until().element(nameField).is().present();* > fails with > {code} > java.lang.IllegalStateException: There is no context available for qualifier org.jboss.arquillian.drone.api.annotation.Default. Available contexts are [interface com.acme.example.test.GrapheneBugDroneTest$BugReport]. > at org.jboss.arquillian.graphene.context.GrapheneContextImpl$LazyContext.getContext(GrapheneContextImpl.java:302) > at org.jboss.arquillian.graphene.context.GrapheneContextImpl$LazyContext.getConfiguration(GrapheneContextImpl.java:234) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.waitGui(DefaultGrapheneRuntime.java:104) > at org.jboss.arquillian.graphene.Graphene.waitGui(Graphene.java:216) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy28.isDisplayed(Unknown Source) > at org.jboss.arquillian.graphene.condition.element.ElementIsPresent.check(ElementIsPresent.java:44) > at org.jboss.arquillian.graphene.condition.element.ElementIsPresent.check(ElementIsPresent.java:31) > at org.jboss.arquillian.graphene.condition.element.AbstractElementBooleanCondition.apply(AbstractElementBooleanCondition.java:52) > at org.jboss.arquillian.graphene.condition.element.AbstractElementBooleanCondition.apply(AbstractElementBooleanCondition.java:33) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:102) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.commit(WebDriverWaitImpl.java:110) > at org.jboss.arquillian.graphene.wait.IsNotElementBuilderImpl.present(IsNotElementBuilderImpl.java:47) > at com.acme.example.test.GrapheneBugDroneTest.addUser(GrapheneBugDroneTest.java:42) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:273) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:266) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:229) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:243) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:188) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:202) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:150) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) > {code} > Arquillian configuration: > * Core 1.1.4.Final > * Graphene 2.0.2.Final > * Drone 2.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 7 08:28:56 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 7 May 2014 08:28:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-440) Upgrade Drone to 2.0.0.Alpha1 and Arquillian core to 1.1.4 In-Reply-To: References: Message-ID: Juraj H?ska created ARQGRA-440: ---------------------------------- Summary: Upgrade Drone to 2.0.0.Alpha1 and Arquillian core to 1.1.4 Key: ARQGRA-440 URL: https://issues.jboss.org/browse/ARQGRA-440 Project: Arquillian Graphene Issue Type: Task Components: core Affects Versions: 2.1.0.Alpha1 Reporter: Juraj H?ska IMHO we should upgrade to new Drone {{2.0.0.Alpha1}} as well as to Arquillian core {{1.1.4.Final}} in a non stable 2.1.x branch to try compatibility with these versions. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 8 15:03:56 2014 From: issues at jboss.org (Matej Briskar (JIRA)) Date: Thu, 8 May 2014 15:03:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1770) Root.war deployed to Wildfly gives wrong @ArquillianResource URL In-Reply-To: References: Message-ID: Matej Briskar created ARQ-1770: ---------------------------------- Summary: Root.war deployed to Wildfly gives wrong @ArquillianResource URL Key: ARQ-1770 URL: https://issues.jboss.org/browse/ARQ-1770 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Matej Briskar This bug is a small one and had easy workaround, but it happens. When I deploy a ROOT.war to the Wildfly embedded container, the returned @ArquillianResource Url url gives localhost:8080/ROOT instead of the correct localhost:8080/. Tested with wildfly 8.1.0.CR1 dependency version. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 9 03:07:56 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 9 May 2014 03:07:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-439) Infer WebDriver context for @FindBy injections when there is only one qualified browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-439: ------------------------------ Fix Version/s: 2.1-Tracking > Infer WebDriver context for @FindBy injections when there is only one qualified browser > ---------------------------------------------------------------------------------------- > > Key: ARQGRA-439 > URL: https://issues.jboss.org/browse/ARQGRA-439 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core, ftest > Affects Versions: 2.0.2.Final > Reporter: Juraj H?ska > Fix For: 2.1-Tracking > > > When one is using qualified {{WebDriver}} instances, he needs to annotate also his {{WebElement}}, ... to distinguish in which context those elements should be resolved. > This has to be done also when there is only one (though qualified) browser injected. > Suppose: > {code} > @RunWith(Arquillian.class) > public class GrapheneBugDroneTest { > @Drone > @BugReport > WebDriver driver; > @Deployment(testable = false) > public static Archive deployHtml5DemoApp() { > return Deployments.createDeployment(); > } > @ArquillianResource > URL url; > @FindBy(id = "name") > @BugReport > WebElement nameField; > @Test > public void addUser() throws Exception { > driver.get(url.toString()); > Graphene.waitGui(driver).until().element(nameField).is().present(); > Assert.assertTrue(true); > } > @Qualifier > @Retention(RetentionPolicy.RUNTIME) > public static @interface BugReport { > } > } > {code} > Graphene can interfere which {{WebDriver}} instance was injected and act accordingly. The idea is also described [here|https://issues.jboss.org/browse/ARQGRA-435?focusedCommentId=12965697&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12965697]. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 9 03:07:56 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 9 May 2014 03:07:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-439) Infer WebDriver context for @FindBy injections when there is only one qualified browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966659#comment-12966659 ] Luk?? Fry? commented on ARQGRA-439: ----------------------------------- What do you think about prototyping this in 2.1 branch and if the complexity of the fix will be low, we can include it in 2.0 as well? > Infer WebDriver context for @FindBy injections when there is only one qualified browser > ---------------------------------------------------------------------------------------- > > Key: ARQGRA-439 > URL: https://issues.jboss.org/browse/ARQGRA-439 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core, ftest > Affects Versions: 2.0.2.Final > Reporter: Juraj H?ska > Fix For: 2.1-Tracking > > > When one is using qualified {{WebDriver}} instances, he needs to annotate also his {{WebElement}}, ... to distinguish in which context those elements should be resolved. > This has to be done also when there is only one (though qualified) browser injected. > Suppose: > {code} > @RunWith(Arquillian.class) > public class GrapheneBugDroneTest { > @Drone > @BugReport > WebDriver driver; > @Deployment(testable = false) > public static Archive deployHtml5DemoApp() { > return Deployments.createDeployment(); > } > @ArquillianResource > URL url; > @FindBy(id = "name") > @BugReport > WebElement nameField; > @Test > public void addUser() throws Exception { > driver.get(url.toString()); > Graphene.waitGui(driver).until().element(nameField).is().present(); > Assert.assertTrue(true); > } > @Qualifier > @Retention(RetentionPolicy.RUNTIME) > public static @interface BugReport { > } > } > {code} > Graphene can interfere which {{WebDriver}} instance was injected and act accordingly. The idea is also described [here|https://issues.jboss.org/browse/ARQGRA-435?focusedCommentId=12965697&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12965697]. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 9 03:09:56 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 9 May 2014 03:09:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-440) Upgrade Drone to 2.0.0.Alpha1 and Arquillian core to 1.1.4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966660#comment-12966660 ] Luk?? Fry? commented on ARQGRA-440: ----------------------------------- We can upgrade to Core 1.1.4 in 2.0 branch, but imho Drone 2.x upgrade should happen in 2.1 branch. > Upgrade Drone to 2.0.0.Alpha1 and Arquillian core to 1.1.4 > ---------------------------------------------------------- > > Key: ARQGRA-440 > URL: https://issues.jboss.org/browse/ARQGRA-440 > Project: Arquillian Graphene > Issue Type: Task > Components: core > Affects Versions: 2.1.0.Alpha1 > Reporter: Juraj H?ska > > IMHO we should upgrade to new Drone {{2.0.0.Alpha1}} as well as to Arquillian core {{1.1.4.Final}} in a non stable 2.1.x branch to try compatibility with these versions. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 9 04:45:56 2014 From: issues at jboss.org (Nikolay Nikolov (JIRA)) Date: Fri, 9 May 2014 04:45:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-332) Add support for injectable configuration options In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966690#comment-12966690 ] Nikolay Nikolov commented on ARQ-332: ------------------------------------- More specific example why this is needed. If you have a local container, that is used by multiple test project, run by separate jenkins jobs, it is common that default ports clash. So it is normal that ports are generated dynamically if not specified explicitly. In cases when you need those ports in your test (and you need not the http port but another one) you cannot get them - only way is to hardcode the ports in the arquillian.xml and to hope there will be no clash. > Add support for injectable configuration options > ------------------------------------------------ > > Key: ARQ-332 > URL: https://issues.jboss.org/browse/ARQ-332 > Project: Arquillian > Issue Type: Feature Request > Components: Configuration > Environment: All > Reporter: John Ament > Priority: Minor > > I may have more of a unique situation here, not sure, but I figure something like this would be useful to a lot of people. In my case, I have to test my application against multiple RDBMSs. Amongst the test cases I need to execute, the only deltas between them is really the orm.xml and persistence.xml for JPA, since we override the configuration. Currently, arquillian requires me to point to the files in my test cases. Granted, I could use a static string to manage them, but I was wondering if arquillian could provide something like this in arquillian.xml > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:glassfish="urn:arq:org.jboss.arquillian.container.glassfish.embedded_3"> > > src/test/resources/sun-resources-mysql.xml > > > > > > > And then in the test case itself > @Inject ArquillianConfiguration config; > config.getProperty("orm-xml"); > in order to access the property. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 9 10:51:56 2014 From: issues at jboss.org (=?UTF-8?Q?Oliver_Ki=C5=A1=C5=A1_=28JIRA=29?=) Date: Fri, 9 May 2014 10:51:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-441) xhrInterception breaks applications using jQuery 2.x In-Reply-To: References: Message-ID: Oliver Ki?? created ARQGRA-441: ---------------------------------- Summary: xhrInterception breaks applications using jQuery 2.x Key: ARQGRA-441 URL: https://issues.jboss.org/browse/ARQGRA-441 Project: Arquillian Graphene Issue Type: Bug Affects Versions: 2.0.2.Final, 2.0.0.Final Environment: Firefox 29, Chrome 34 Reporter: Oliver Ki?? Priority: Critical After {{[kitchensink-backbone|https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.6.x-develop/kitchensink-backbone]}} and {{[contacts-mobile-basic|https://github.com/jboss-developer/jboss-wfk-quickstarts/pull/154]}} quickstarts were updated to use jQuery 2.0.3, Graphene guards no longer work properly in their functional tests. After {{window.Graphene.xhrInterception.install()}}, the quickstarts do not react to responses to ajax requests they make (server side validation messages are not shown, member list is not displayed, no feedback is shown after a new member is registered). When {{window.Graphene.xhrInterception.uninstall()}} is run, the quickstarts start behaving normally again. I tried reproducing the issue with different versions of javascript libraries used in the quickstarts and could reproduce it if jQuery 2.x was used, other libraries do not seem to have an effect on the issue. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 9 11:37:58 2014 From: issues at jboss.org (=?UTF-8?Q?Oliver_Ki=C5=A1=C5=A1_=28JIRA=29?=) Date: Fri, 9 May 2014 11:37:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-441) xhrInterception breaks applications using jQuery 2.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Ki?? updated ARQGRA-441: ------------------------------- Description: After {{[kitchensink-backbone|https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.6.x-develop/kitchensink-backbone]}} and {{[contacts-mobile-basic|https://github.com/jboss-developer/jboss-wfk-quickstarts/pull/154]}} quickstarts were updated to use jQuery 2.0.3, Graphene guards no longer work properly in their functional tests. After {{window.Graphene.xhrInterception.install()}}, the quickstarts do not react to responses to ajax requests they make (server side validation messages are not shown, member list is not displayed, no feedback is shown after a new member is registered). When {{window.Graphene.xhrInterception.uninstall()}} is run, the quickstarts start behaving normally again. I tried reproducing the issue with different versions of javascript libraries used in the quickstarts and could reproduce it if jQuery 2.x was used (tested 2.0.3 and 2.1.0). Other libraries do not seem to have an effect on the issue. was: After {{[kitchensink-backbone|https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.6.x-develop/kitchensink-backbone]}} and {{[contacts-mobile-basic|https://github.com/jboss-developer/jboss-wfk-quickstarts/pull/154]}} quickstarts were updated to use jQuery 2.0.3, Graphene guards no longer work properly in their functional tests. After {{window.Graphene.xhrInterception.install()}}, the quickstarts do not react to responses to ajax requests they make (server side validation messages are not shown, member list is not displayed, no feedback is shown after a new member is registered). When {{window.Graphene.xhrInterception.uninstall()}} is run, the quickstarts start behaving normally again. I tried reproducing the issue with different versions of javascript libraries used in the quickstarts and could reproduce it if jQuery 2.x was used, other libraries do not seem to have an effect on the issue. > xhrInterception breaks applications using jQuery 2.x > ---------------------------------------------------- > > Key: ARQGRA-441 > URL: https://issues.jboss.org/browse/ARQGRA-441 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final, 2.0.2.Final > Environment: Firefox 29, Chrome 34 > Reporter: Oliver Ki?? > Priority: Critical > > After {{[kitchensink-backbone|https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.6.x-develop/kitchensink-backbone]}} and {{[contacts-mobile-basic|https://github.com/jboss-developer/jboss-wfk-quickstarts/pull/154]}} quickstarts were updated to use jQuery 2.0.3, Graphene guards no longer work properly in their functional tests. > After {{window.Graphene.xhrInterception.install()}}, the quickstarts do not react to responses to ajax requests they make (server side validation messages are not shown, member list is not displayed, no feedback is shown after a new member is registered). > When {{window.Graphene.xhrInterception.uninstall()}} is run, the quickstarts start behaving normally again. > I tried reproducing the issue with different versions of javascript libraries used in the quickstarts and could reproduce it if jQuery 2.x was used (tested 2.0.3 and 2.1.0). Other libraries do not seem to have an effect on the issue. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 9 15:07:56 2014 From: issues at jboss.org (=?UTF-8?Q?Oliver_Ki=C5=A1=C5=A1_=28JIRA=29?=) Date: Fri, 9 May 2014 15:07:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-441) xhrInterception breaks applications using jQuery 2.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966897#comment-12966897 ] Oliver Ki?? commented on ARQGRA-441: ------------------------------------ [this commit|https://github.com/jquery/jquery/commit/17049c73bc5bf1a41cce4a5b648f55da7bbac533] in jQuery seems to be causing the problems. I tried reverting it and kitchensink-backbone worked correctly after xhrInterceptor was installed. > xhrInterception breaks applications using jQuery 2.x > ---------------------------------------------------- > > Key: ARQGRA-441 > URL: https://issues.jboss.org/browse/ARQGRA-441 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final, 2.0.2.Final > Environment: Firefox 29, Chrome 34 > Reporter: Oliver Ki?? > Priority: Critical > > After {{[kitchensink-backbone|https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.6.x-develop/kitchensink-backbone]}} and {{[contacts-mobile-basic|https://github.com/jboss-developer/jboss-wfk-quickstarts/pull/154]}} quickstarts were updated to use jQuery 2.0.3, Graphene guards no longer work properly in their functional tests. > After {{window.Graphene.xhrInterception.install()}}, the quickstarts do not react to responses to ajax requests they make (server side validation messages are not shown, member list is not displayed, no feedback is shown after a new member is registered). > When {{window.Graphene.xhrInterception.uninstall()}} is run, the quickstarts start behaving normally again. > I tried reproducing the issue with different versions of javascript libraries used in the quickstarts and could reproduce it if jQuery 2.x was used (tested 2.0.3 and 2.1.0). Other libraries do not seem to have an effect on the issue. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 9 15:09:56 2014 From: issues at jboss.org (=?UTF-8?Q?Oliver_Ki=C5=A1=C5=A1_=28JIRA=29?=) Date: Fri, 9 May 2014 15:09:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-441) xhrInterception breaks applications using jQuery 2.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966897#comment-12966897 ] Oliver Ki?? edited comment on ARQGRA-441 at 5/9/14 3:09 PM: ------------------------------------------------------------ [this commit|https://github.com/jquery/jquery/commit/17049c73bc5bf1a41cce4a5b648f55da7bbac533] in jQuery seems to be causing the problems. I tried reverting it and kitchensink-backbone worked correctly after xhrInterception was installed. was (Author: okiss): [this commit|https://github.com/jquery/jquery/commit/17049c73bc5bf1a41cce4a5b648f55da7bbac533] in jQuery seems to be causing the problems. I tried reverting it and kitchensink-backbone worked correctly after xhrInterceptor was installed. > xhrInterception breaks applications using jQuery 2.x > ---------------------------------------------------- > > Key: ARQGRA-441 > URL: https://issues.jboss.org/browse/ARQGRA-441 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final, 2.0.2.Final > Environment: Firefox 29, Chrome 34 > Reporter: Oliver Ki?? > Priority: Critical > > After {{[kitchensink-backbone|https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.6.x-develop/kitchensink-backbone]}} and {{[contacts-mobile-basic|https://github.com/jboss-developer/jboss-wfk-quickstarts/pull/154]}} quickstarts were updated to use jQuery 2.0.3, Graphene guards no longer work properly in their functional tests. > After {{window.Graphene.xhrInterception.install()}}, the quickstarts do not react to responses to ajax requests they make (server side validation messages are not shown, member list is not displayed, no feedback is shown after a new member is registered). > When {{window.Graphene.xhrInterception.uninstall()}} is run, the quickstarts start behaving normally again. > I tried reproducing the issue with different versions of javascript libraries used in the quickstarts and could reproduce it if jQuery 2.x was used (tested 2.0.3 and 2.1.0). Other libraries do not seem to have an effect on the issue. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sat May 10 13:01:56 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 10 May 2014 13:01:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1331) Should be able to define default persistence unit as a complementary option for data source used for seeding/comparing test data. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1331: -------------------------------- Fix Version/s: (was: persistence_1.0.0.next) > Should be able to define default persistence unit as a complementary option for data source used for seeding/comparing test data. > --------------------------------------------------------------------------------------------------------------------------------- > > Key: ARQ-1331 > URL: https://issues.jboss.org/browse/ARQ-1331 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > > Instead of relying on JNDI conventions using persistence unit name might be more portable. Using a name we can easily extract data source JNDI from the persistence.xml -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sat May 10 13:03:56 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 10 May 2014 13:03:56 -0400 (EDT) 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: (was: 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 > > BOM will help importing all required deps for APE in the controlled, yet simple manner. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sat May 10 13:03:56 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 10 May 2014 13:03:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1374) Should support global exclude column rules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1374: -------------------------------- Fix Version/s: (was: persistence_1.0.0.next) > Should support global exclude column rules > ------------------------------------------ > > Key: ARQ-1374 > URL: https://issues.jboss.org/browse/ARQ-1374 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Aslak Knutsen > Assignee: Bartosz Majsak > Priority: Minor > > As a Tester I should be able to exclude columns from comparison on a global level. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sat May 10 16:25:56 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 10 May 2014 16:25:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1644) Arquillian Persistence doesn't work with embedded/Local containers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1644: -------------------------------- Fix Version/s: (was: persistence_1.0.0.next) > Arquillian Persistence doesn't work with embedded/Local containers > ------------------------------------------------------------------ > > Key: ARQ-1644 > URL: https://issues.jboss.org/browse/ARQ-1644 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Romain Manni-Bucau > Assignee: Bartosz Majsak > > Because of the way its Extensions are written arquillien-extension-persistence doesn't work with Local containers (tested with OpenEJB, need hack like http://rmannibucau.wordpress.com/2013/09/05/arquillian-persistence-and-embedded-container-openejbdbunithsqldb-case/) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sat May 10 16:25:57 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 10 May 2014 16:25:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1013) Embedded weld integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1013: -------------------------------- Fix Version/s: (was: persistence_1.0.0.next) > Embedded weld integration > ------------------------- > > Key: ARQ-1013 > URL: https://issues.jboss.org/browse/ARQ-1013 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Trevor Baker > Assignee: Bartosz Majsak > Attachments: sample.zip, sample.zip > > > Better integration with embedded weld. Developers still need to manually wire in JNDI initial context, datasource, jta, and hibernate. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sun May 11 05:21:56 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sun, 11 May 2014 05:21:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1644) Arquillian Persistence doesn't work with embedded/Local containers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1644: -------------------------------- Description: Because of the way its Extensions are written arquillien-extension-persistence doesn't work with Local containers (tested with OpenEJB, need hack like [the one mentiong in the blog|http://rmannibucau.wordpress.com/2013/09/05/arquillian-persistence-and-embedded-container-openejbdbunithsqldb-case/]) (was: Because of the way its Extensions are written arquillien-extension-persistence doesn't work with Local containers (tested with OpenEJB, need hack like http://rmannibucau.wordpress.com/2013/09/05/arquillian-persistence-and-embedded-container-openejbdbunithsqldb-case/)) > Arquillian Persistence doesn't work with embedded/Local containers > ------------------------------------------------------------------ > > Key: ARQ-1644 > URL: https://issues.jboss.org/browse/ARQ-1644 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Romain Manni-Bucau > Assignee: Bartosz Majsak > > Because of the way its Extensions are written arquillien-extension-persistence doesn't work with Local containers (tested with OpenEJB, need hack like [the one mentiong in the blog|http://rmannibucau.wordpress.com/2013/09/05/arquillian-persistence-and-embedded-container-openejbdbunithsqldb-case/]) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sun May 11 05:21:56 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sun, 11 May 2014 05:21:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1644) Arquillian Persistence doesn't work with embedded/Local containers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966937#comment-12966937 ] Bartosz Majsak commented on ARQ-1644: ------------------------------------- [Working sample|https://github.com/rmannibucau/persistence-with-openejb-and-arquillian/] shared by [~rmannibucau] > Arquillian Persistence doesn't work with embedded/Local containers > ------------------------------------------------------------------ > > Key: ARQ-1644 > URL: https://issues.jboss.org/browse/ARQ-1644 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Romain Manni-Bucau > Assignee: Bartosz Majsak > > Because of the way its Extensions are written arquillien-extension-persistence doesn't work with Local containers (tested with OpenEJB, need hack like [the one mentiong in the blog|http://rmannibucau.wordpress.com/2013/09/05/arquillian-persistence-and-embedded-container-openejbdbunithsqldb-case/]) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sun May 11 16:55:57 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sun, 11 May 2014 16:55:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1771) Putting custom annotation on Drone creates multiple instances In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1771: -------------------------------------- Summary: Putting custom annotation on Drone creates multiple instances Key: ARQ-1771 URL: https://issues.jboss.org/browse/ARQ-1771 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_2.0.0.Alpha1 Reporter: Stefan Miklosovic I have a test case like this {code} @RunWith(Arquillian.class) @RunAsClient public class SomeTestCase { @Drone @Mobile @Custom private WebDriver mobile; // tests } {code} where @Custom is just an annotation: {code} @Retention(RetentionPolicy.RUNTIME) @Target({ ElementType.FIELD, ElementType.PARAMETER }) public @interface Custom { } {code} it is _not_ annotated with @Qualifier. Realize that the same problem arise when using @OperateOnDeployment from Arquillian which is not annotated with @Qualifier neither. I am getting this: http://pastebin.com/raw.php?i=i9DVqeaC You see that InstrumentationPerformDecider.decidePerformingInstrumentation observes BeforeDroneInstantiated so when it is treated twice, you are going to instantiate two Drones which is another argument why Drone does it wrong. When I declare Drone injection like that, it results into two instances of WebDrivers so that means it instruments Android package twice with two Selendroids so that mean I am getting NoUniqueWebDriverException when I want to start some activity because from now on you have "by accident" two webdrivers instrumenting the same deployment as a result of a bug where putting custom annotation on Drone instantiates it twice. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sun May 11 17:01:56 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sun, 11 May 2014 17:01:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1771) Putting custom annotation on Drone creates multiple instances In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966944#comment-12966944 ] Stefan Miklosovic commented on ARQ-1771: ---------------------------------------- It seems that DroneTestEnricher#ensureInjectionPointPrepared parse Drone point without custom annotation, only @Drone and annotations with @Qualifier are treated so it thinks that @Drone @Mobile @Custom is different from @Drone @Mobile so it instantiates it for the second time with missleading log message. > Putting custom annotation on Drone creates multiple instances > ------------------------------------------------------------- > > Key: ARQ-1771 > URL: https://issues.jboss.org/browse/ARQ-1771 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha1 > Reporter: Stefan Miklosovic > > I have a test case like this > {code} > @RunWith(Arquillian.class) > @RunAsClient > public class SomeTestCase > { > @Drone > @Mobile > @Custom > private WebDriver mobile; > // tests > } > {code} > where @Custom is just an annotation: > {code} > @Retention(RetentionPolicy.RUNTIME) > @Target({ ElementType.FIELD, ElementType.PARAMETER }) > public @interface Custom { > } > {code} > it is _not_ annotated with @Qualifier. > Realize that the same problem arise when using @OperateOnDeployment from Arquillian which is not annotated with @Qualifier neither. > I am getting this: > http://pastebin.com/raw.php?i=i9DVqeaC > You see that InstrumentationPerformDecider.decidePerformingInstrumentation observes BeforeDroneInstantiated so when it is treated twice, you are going to instantiate two Drones which is another argument why Drone does it wrong. > When I declare Drone injection like that, it results into two instances of WebDrivers so that means it instruments Android package twice with two Selendroids so that mean I am getting NoUniqueWebDriverException when I want to start some activity because from now on you have "by accident" two webdrivers instrumenting the same deployment as a result of a bug where putting custom annotation on Drone instantiates it twice. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 04:35:56 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 12 May 2014 04:35:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1772) Arquillian Debug does not print real event class In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1772: -------------------------------- Summary: Arquillian Debug does not print real event class Key: ARQ-1772 URL: https://issues.jboss.org/browse/ARQ-1772 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.1.4.Final Reporter: Karel Piwko When using inheritance to define events, Arquillian Debug prints out following: {code} (E) PrepareDrone (O) EventRegisterObserver.register (O) DroneConfigurator.prepareDrone (E) DroneConfigurationEvent (O) EventRegisterObserver.register (E) DroneConfigurationEvent (O) EventRegisterObserver.register (E) DroneLifecycleEvent (O) EventRegisterObserver.register (E) DroneLifecycleEvent (O) EventRegisterObserver.register (E) Before (O) EventRegisterObserver.register (O) DroneLifecycleManager.before (E) DroneLifecycleEvent (O) EventRegisterObserver.register (E) DroneLifecycleEvent (O) EventRegisterObserver.register (O) DroneEnhancer.enhanceDrone (E) DroneLifecycleEvent (O) EventRegisterObserver.register (E) DroneLifecycleEvent (O) EventRegisterObserver.register (O) DroneEnhancer.enhanceDrone {code} Which is not really super useful, as debug log can't show what actual events were fired. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 04:53:56 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 12 May 2014 04:53:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1771) Putting custom annotation on Drone creates multiple instances In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967002#comment-12967002 ] Stefan Miklosovic commented on ARQ-1771: ---------------------------------------- The problem was that in a test project there was a page object used which has injected webdriver in it. Injection of Drone was like {code} class TestCase { @Drone @Mobile @Custom AndroidDriver mobile; } {code} and page object was like {code} class PageObject { @Drone @Mobile AndroidDriver mobile; } {code} So Graphene could not resolve that Drone injection point for page object since there is not such point - there is a point which is additionally annotated by @Custom, but there is not such point which is annotated only by these two annotations (@Drone and @Mobile). What we are missing here is some kind of resolution and guessing what is "enough" to know in order to inject something into a page object. Imagine you have 2 browsers so they are annotated by @Drone @Chrome and @Drone @Firefox and injected into a test. Additionally you have page object - that abstraction is independent from the choice of browsers so it would be enough to use just @Drone in page object and you are not changing your page object model at all. > Putting custom annotation on Drone creates multiple instances > ------------------------------------------------------------- > > Key: ARQ-1771 > URL: https://issues.jboss.org/browse/ARQ-1771 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha1 > Reporter: Stefan Miklosovic > > I have a test case like this > {code} > @RunWith(Arquillian.class) > @RunAsClient > public class SomeTestCase > { > @Drone > @Mobile > @Custom > private WebDriver mobile; > // tests > } > {code} > where @Custom is just an annotation: > {code} > @Retention(RetentionPolicy.RUNTIME) > @Target({ ElementType.FIELD, ElementType.PARAMETER }) > public @interface Custom { > } > {code} > it is _not_ annotated with @Qualifier. > Realize that the same problem arise when using @OperateOnDeployment from Arquillian which is not annotated with @Qualifier neither. > I am getting this: > http://pastebin.com/raw.php?i=i9DVqeaC > You see that InstrumentationPerformDecider.decidePerformingInstrumentation observes BeforeDroneInstantiated so when it is treated twice, you are going to instantiate two Drones which is another argument why Drone does it wrong. > When I declare Drone injection like that, it results into two instances of WebDrivers so that means it instruments Android package twice with two Selendroids so that mean I am getting NoUniqueWebDriverException when I want to start some activity because from now on you have "by accident" two webdrivers instrumenting the same deployment as a result of a bug where putting custom annotation on Drone instantiates it twice. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 04:55:57 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 12 May 2014 04:55:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1771) Putting custom annotation on Drone creates multiple instances In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1771. ------------------------------------ Fix Version/s: drone_2.0.0.Alpha2 Resolution: Rejected > Putting custom annotation on Drone creates multiple instances > ------------------------------------------------------------- > > Key: ARQ-1771 > URL: https://issues.jboss.org/browse/ARQ-1771 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha1 > Reporter: Stefan Miklosovic > Fix For: drone_2.0.0.Alpha2 > > > I have a test case like this > {code} > @RunWith(Arquillian.class) > @RunAsClient > public class SomeTestCase > { > @Drone > @Mobile > @Custom > private WebDriver mobile; > // tests > } > {code} > where @Custom is just an annotation: > {code} > @Retention(RetentionPolicy.RUNTIME) > @Target({ ElementType.FIELD, ElementType.PARAMETER }) > public @interface Custom { > } > {code} > it is _not_ annotated with @Qualifier. > Realize that the same problem arise when using @OperateOnDeployment from Arquillian which is not annotated with @Qualifier neither. > I am getting this: > http://pastebin.com/raw.php?i=i9DVqeaC > You see that InstrumentationPerformDecider.decidePerformingInstrumentation observes BeforeDroneInstantiated so when it is treated twice, you are going to instantiate two Drones which is another argument why Drone does it wrong. > When I declare Drone injection like that, it results into two instances of WebDrivers so that means it instruments Android package twice with two Selendroids so that mean I am getting NoUniqueWebDriverException when I want to start some activity because from now on you have "by accident" two webdrivers instrumenting the same deployment as a result of a bug where putting custom annotation on Drone instantiates it twice. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 06:27:56 2014 From: issues at jboss.org (Mattias Persson (JIRA)) Date: Mon, 12 May 2014 06:27:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1773) JUnittests pass when exception is thrown from @Before-annotated method In-Reply-To: References: Message-ID: Mattias Persson created ARQ-1773: ------------------------------------ Summary: JUnittests pass when exception is thrown from @Before-annotated method Key: ARQ-1773 URL: https://issues.jboss.org/browse/ARQ-1773 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.1.4.Final Reporter: Mattias Persson When an exception is thrown from a method with @Before, tests that should fail actually pass when using Arquillian 1.1.4.Final. When stepping down to 1.1.3.Final, the tests fail as expected. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 06:29:56 2014 From: issues at jboss.org (Mattias Persson (JIRA)) Date: Mon, 12 May 2014 06:29:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1773) JUnittests pass when exception is thrown from @Before-annotated method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mattias Persson updated ARQ-1773: --------------------------------- Attachment: arquillian_test_should_fail.zip Project for reproducing error > JUnittests pass when exception is thrown from @Before-annotated method > ---------------------------------------------------------------------- > > Key: ARQ-1773 > URL: https://issues.jboss.org/browse/ARQ-1773 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Mattias Persson > Attachments: arquillian_test_should_fail.zip > > > When an exception is thrown from a method with @Before, tests that should fail actually pass when using Arquillian 1.1.4.Final. When stepping down to 1.1.3.Final, the tests fail as expected. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 06:29:57 2014 From: issues at jboss.org (Mattias Persson (JIRA)) Date: Mon, 12 May 2014 06:29:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1773) JUnittests pass when exception is thrown from @Before-annotated method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mattias Persson updated ARQ-1773: --------------------------------- Steps to Reproduce: See attached file, Maven dependency according to: org.jboss.arquillian arquillian-bom 1.1.4.Final import pom Testclass according to: package se.shouldfailtest; import org.jboss.arquillian.container.test.api.Deployment; import org.jboss.arquillian.junit.Arquillian; import org.jboss.shrinkwrap.api.Archive; import org.jboss.shrinkwrap.api.ShrinkWrap; import org.jboss.shrinkwrap.api.asset.EmptyAsset; import org.jboss.shrinkwrap.api.spec.WebArchive; import org.junit.Before; import org.junit.Test; import org.junit.runner.RunWith; import static org.junit.Assert.assertTrue; @RunWith(Arquillian.class) public class ShouldFailTest { @Deployment public static Archive createDeployment() { WebArchive war = ShrinkWrap.create(WebArchive.class, "test.war") .addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml"); return war; } @Before public void preparePersistenceTest() throws Exception { throw new Exception("Test should fail when exception is thrown in @Before..."); } @Test public void shouldFail() throws Exception { //This test will pass in 1.1.4.Final but not in 1.1.3.Final (as expected). assertTrue(false); } } was: Maven dependency according to: org.jboss.arquillian arquillian-bom 1.1.4.Final import pom Testclass according to: package se.shouldfailtest; import org.jboss.arquillian.container.test.api.Deployment; import org.jboss.arquillian.junit.Arquillian; import org.jboss.shrinkwrap.api.Archive; import org.jboss.shrinkwrap.api.ShrinkWrap; import org.jboss.shrinkwrap.api.asset.EmptyAsset; import org.jboss.shrinkwrap.api.spec.WebArchive; import org.junit.Before; import org.junit.Test; import org.junit.runner.RunWith; import static org.junit.Assert.assertTrue; @RunWith(Arquillian.class) public class ShouldFailTest { @Deployment public static Archive createDeployment() { WebArchive war = ShrinkWrap.create(WebArchive.class, "test.war") .addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml"); return war; } @Before public void preparePersistenceTest() throws Exception { throw new Exception("Test should fail when exception is thrown in @Before..."); } @Test public void shouldFail() throws Exception { //This test will pass in 1.1.4.Final but not in 1.1.3.Final (as expected). assertTrue(false); } } > JUnittests pass when exception is thrown from @Before-annotated method > ---------------------------------------------------------------------- > > Key: ARQ-1773 > URL: https://issues.jboss.org/browse/ARQ-1773 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Mattias Persson > Attachments: arquillian_test_should_fail.zip > > > When an exception is thrown from a method with @Before, tests that should fail actually pass when using Arquillian 1.1.4.Final. When stepping down to 1.1.3.Final, the tests fail as expected. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 06:31:56 2014 From: issues at jboss.org (Mattias Persson (JIRA)) Date: Mon, 12 May 2014 06:31:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1773) JUnittests pass when exception is thrown from @Before-annotated method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mattias Persson updated ARQ-1773: --------------------------------- Steps to Reproduce: See attached file. Maven dependency according to: org.jboss.arquillian arquillian-bom 1.1.4.Final import pom Testclass according to: package se.shouldfailtest; import org.jboss.arquillian.container.test.api.Deployment; import org.jboss.arquillian.junit.Arquillian; import org.jboss.shrinkwrap.api.Archive; import org.jboss.shrinkwrap.api.ShrinkWrap; import org.jboss.shrinkwrap.api.asset.EmptyAsset; import org.jboss.shrinkwrap.api.spec.WebArchive; import org.junit.Before; import org.junit.Test; import org.junit.runner.RunWith; import static org.junit.Assert.assertTrue; @RunWith(Arquillian.class) public class ShouldFailTest { @Deployment public static Archive createDeployment() { WebArchive war = ShrinkWrap.create(WebArchive.class, "test.war") .addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml"); return war; } @Before public void preparePersistenceTest() throws Exception { throw new Exception("Test should fail when exception is thrown in @Before..."); } @Test public void shouldFail() throws Exception { //This test will pass in 1.1.4.Final but not in 1.1.3.Final (as expected). assertTrue(false); } } was: See attached file, Maven dependency according to: org.jboss.arquillian arquillian-bom 1.1.4.Final import pom Testclass according to: package se.shouldfailtest; import org.jboss.arquillian.container.test.api.Deployment; import org.jboss.arquillian.junit.Arquillian; import org.jboss.shrinkwrap.api.Archive; import org.jboss.shrinkwrap.api.ShrinkWrap; import org.jboss.shrinkwrap.api.asset.EmptyAsset; import org.jboss.shrinkwrap.api.spec.WebArchive; import org.junit.Before; import org.junit.Test; import org.junit.runner.RunWith; import static org.junit.Assert.assertTrue; @RunWith(Arquillian.class) public class ShouldFailTest { @Deployment public static Archive createDeployment() { WebArchive war = ShrinkWrap.create(WebArchive.class, "test.war") .addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml"); return war; } @Before public void preparePersistenceTest() throws Exception { throw new Exception("Test should fail when exception is thrown in @Before..."); } @Test public void shouldFail() throws Exception { //This test will pass in 1.1.4.Final but not in 1.1.3.Final (as expected). assertTrue(false); } } > JUnittests pass when exception is thrown from @Before-annotated method > ---------------------------------------------------------------------- > > Key: ARQ-1773 > URL: https://issues.jboss.org/browse/ARQ-1773 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Mattias Persson > Attachments: arquillian_test_should_fail.zip > > > When an exception is thrown from a method with @Before, tests that should fail actually pass when using Arquillian 1.1.4.Final. When stepping down to 1.1.3.Final, the tests fail as expected. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 06:31:56 2014 From: issues at jboss.org (Mattias Persson (JIRA)) Date: Mon, 12 May 2014 06:31:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1773) JUnittests pass when exception is thrown from @Before-annotated method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mattias Persson updated ARQ-1773: --------------------------------- Steps to Reproduce: See attached file Maven dependency according to: org.jboss.arquillian arquillian-bom 1.1.4.Final import pom Testclass according to: package se.shouldfailtest; import org.jboss.arquillian.container.test.api.Deployment; import org.jboss.arquillian.junit.Arquillian; import org.jboss.shrinkwrap.api.Archive; import org.jboss.shrinkwrap.api.ShrinkWrap; import org.jboss.shrinkwrap.api.asset.EmptyAsset; import org.jboss.shrinkwrap.api.spec.WebArchive; import org.junit.Before; import org.junit.Test; import org.junit.runner.RunWith; import static org.junit.Assert.assertTrue; @RunWith(Arquillian.class) public class ShouldFailTest { @Deployment public static Archive createDeployment() { WebArchive war = ShrinkWrap.create(WebArchive.class, "test.war") .addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml"); return war; } @Before public void preparePersistenceTest() throws Exception { throw new Exception("Test should fail when exception is thrown in @Before..."); } @Test public void shouldFail() throws Exception { //This test will pass in 1.1.4.Final but not in 1.1.3.Final (as expected). assertTrue(false); } } was: See attached file. Maven dependency according to: org.jboss.arquillian arquillian-bom 1.1.4.Final import pom Testclass according to: package se.shouldfailtest; import org.jboss.arquillian.container.test.api.Deployment; import org.jboss.arquillian.junit.Arquillian; import org.jboss.shrinkwrap.api.Archive; import org.jboss.shrinkwrap.api.ShrinkWrap; import org.jboss.shrinkwrap.api.asset.EmptyAsset; import org.jboss.shrinkwrap.api.spec.WebArchive; import org.junit.Before; import org.junit.Test; import org.junit.runner.RunWith; import static org.junit.Assert.assertTrue; @RunWith(Arquillian.class) public class ShouldFailTest { @Deployment public static Archive createDeployment() { WebArchive war = ShrinkWrap.create(WebArchive.class, "test.war") .addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml"); return war; } @Before public void preparePersistenceTest() throws Exception { throw new Exception("Test should fail when exception is thrown in @Before..."); } @Test public void shouldFail() throws Exception { //This test will pass in 1.1.4.Final but not in 1.1.3.Final (as expected). assertTrue(false); } } > JUnittests pass when exception is thrown from @Before-annotated method > ---------------------------------------------------------------------- > > Key: ARQ-1773 > URL: https://issues.jboss.org/browse/ARQ-1773 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Mattias Persson > Attachments: arquillian_test_should_fail.zip > > > When an exception is thrown from a method with @Before, tests that should fail actually pass when using Arquillian 1.1.4.Final. When stepping down to 1.1.3.Final, the tests fail as expected. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 06:45:57 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 12 May 2014 06:45:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-441) xhrInterception breaks applications using jQuery 2.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-441: ------------------------------ Fix Version/s: 2.0.3.Final > xhrInterception breaks applications using jQuery 2.x > ---------------------------------------------------- > > Key: ARQGRA-441 > URL: https://issues.jboss.org/browse/ARQGRA-441 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final, 2.0.2.Final > Environment: Firefox 29, Chrome 34 > Reporter: Oliver Ki?? > Priority: Critical > Fix For: 2.0.3.Final > > > After {{[kitchensink-backbone|https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.6.x-develop/kitchensink-backbone]}} and {{[contacts-mobile-basic|https://github.com/jboss-developer/jboss-wfk-quickstarts/pull/154]}} quickstarts were updated to use jQuery 2.0.3, Graphene guards no longer work properly in their functional tests. > After {{window.Graphene.xhrInterception.install()}}, the quickstarts do not react to responses to ajax requests they make (server side validation messages are not shown, member list is not displayed, no feedback is shown after a new member is registered). > When {{window.Graphene.xhrInterception.uninstall()}} is run, the quickstarts start behaving normally again. > I tried reproducing the issue with different versions of javascript libraries used in the quickstarts and could reproduce it if jQuery 2.x was used (tested 2.0.3 and 2.1.0). Other libraries do not seem to have an effect on the issue. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:17:56 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 07:17:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1772) Arquillian Debug does not print real event class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967075#comment-12967075 ] Aslak Knutsen commented on ARQ-1772: ------------------------------------ that would be this piece of code: https://github.com/arquillian/arquillian-core/blob/master/core/impl-base/src/main/java/org/jboss/arquillian/core/impl/ManagerImpl.java#L630 It was added to avoid showing the 'anonymous innerclass' v of the ManagerStarted event. > Arquillian Debug does not print real event class > ------------------------------------------------ > > Key: ARQ-1772 > URL: https://issues.jboss.org/browse/ARQ-1772 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Karel Piwko > > When using inheritance to define events, Arquillian Debug prints out following: > {code} > (E) PrepareDrone > (O) EventRegisterObserver.register > (O) DroneConfigurator.prepareDrone > (E) DroneConfigurationEvent > (O) EventRegisterObserver.register > (E) DroneConfigurationEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) Before > (O) EventRegisterObserver.register > (O) DroneLifecycleManager.before > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (O) DroneEnhancer.enhanceDrone > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (O) DroneEnhancer.enhanceDrone > {code} > Which is not really super useful, as debug log can't show what actual events were fired. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:19:56 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 07:19:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-332) Add support for injectable configuration options In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-332: ------------------------------ Fix Version/s: 2.0.0.CR1 > Add support for injectable configuration options > ------------------------------------------------ > > Key: ARQ-332 > URL: https://issues.jboss.org/browse/ARQ-332 > Project: Arquillian > Issue Type: Feature Request > Components: Configuration > Environment: All > Reporter: John Ament > Priority: Minor > Fix For: 2.0.0.CR1 > > > I may have more of a unique situation here, not sure, but I figure something like this would be useful to a lot of people. In my case, I have to test my application against multiple RDBMSs. Amongst the test cases I need to execute, the only deltas between them is really the orm.xml and persistence.xml for JPA, since we override the configuration. Currently, arquillian requires me to point to the files in my test cases. Granted, I could use a static string to manage them, but I was wondering if arquillian could provide something like this in arquillian.xml > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:glassfish="urn:arq:org.jboss.arquillian.container.glassfish.embedded_3"> > > src/test/resources/sun-resources-mysql.xml > > > > > > > And then in the test case itself > @Inject ArquillianConfiguration config; > config.getProperty("orm-xml"); > in order to access the property. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:43:57 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 07:43:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1355) Access the DatabaseConnection for additional verifications in an arquillian test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1355: ------------------------------- Fix Version/s: persistence_1.0.0.Alpha7 (was: persistence_1.0.0.next) > Access the DatabaseConnection for additional verifications in an arquillian test > -------------------------------------------------------------------------------- > > Key: ARQ-1355 > URL: https://issues.jboss.org/browse/ARQ-1355 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Dominik Grupp > Assignee: Bartosz Majsak > Priority: Minor > Fix For: persistence_1.0.0.Alpha7 > > > There should be a possibility in an arquillian test to access the DatabaseConnection for additional verifications using dbunit. Using @UsingDataSet and @ShouldMatchDataSet first the already provided verifications could be done but then additional verification with dbunit using the DatabaseConnection - e.g. verfiy with a rowcount to make sure not more entries than expected have been created by the test. > Original post (with a code example): https://community.jboss.org/thread/222401?tstart=0 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:43:58 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 07:43:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1309) Persistence extension does not work with Jacoco extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1309: ------------------------------- Fix Version/s: persistence_1.0.0.Alpha7 (was: persistence_1.0.0.next) > Persistence extension does not work with Jacoco extension > --------------------------------------------------------- > > Key: ARQ-1309 > URL: https://issues.jboss.org/browse/ARQ-1309 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: 1.0.0.Alpha5 > Reporter: Peter Schonhofen > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > When the Jacoco and persistence extension is used together in a project, a "PersistenceExtensionInitializationException: Unable to create persistence configuration" is thrown. > The cause of the exception is that in the ConfigurationImporter class the createConfiguration method receives a fieldsWithValues map with a "$jacocoData" item in it. Because the method cannot process this item, it fails. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:43:58 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 07:43:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1646) Add WildFly managed container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1646: ------------------------------- Fix Version/s: persistence_1.0.0.Alpha7 (was: persistence_1.0.0.next) > Add WildFly managed container > ----------------------------- > > Key: ARQ-1646 > URL: https://issues.jboss.org/browse/ARQ-1646 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Trivial > Fix For: persistence_1.0.0.Alpha7 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:43:58 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 07:43:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1530) Column ordering does not work properly due to DBUnit bug In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1530: ------------------------------- Fix Version/s: persistence_1.0.0.Alpha7 (was: persistence_1.0.0.next) > Column ordering does not work properly due to DBUnit bug > -------------------------------------------------------- > > Key: ARQ-1530 > URL: https://issues.jboss.org/browse/ARQ-1530 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > Details in the referenced forum thread. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:43:58 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 07:43:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1664) Provide custom table filter for seeding and cleaning databases In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1664: ------------------------------- Fix Version/s: persistence_1.0.0.Alpha7 (was: persistence_1.0.0.next) > Provide custom table filter for seeding and cleaning databases > -------------------------------------------------------------- > > Key: ARQ-1664 > URL: https://issues.jboss.org/browse/ARQ-1664 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > In order to resolve Foreign Key dependency and remove tables in the correct order DatabaseSequenceFilter has been introduced. As it's causing significant performance drop, especially in Oracle DB, it should be possible to define custom table filtering through SPI mechanism. This is also useful when seeding database. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:43:58 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 07:43:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1398) DatabaseSequenceFilter should be optional In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1398: ------------------------------- Fix Version/s: persistence_1.0.0.Alpha7 (was: persistence_1.0.0.next) > DatabaseSequenceFilter should be optional > ----------------------------------------- > > Key: ARQ-1398 > URL: https://issues.jboss.org/browse/ARQ-1398 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > Disabled by default, possible to enable through dbunit configuration. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:43:59 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 07:43:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-812) Split DBUnit and Core implemenation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-812: ------------------------------ Fix Version/s: persistence_1.0.0.Alpha7 (was: persistence_1.0.0.next) > Split DBUnit and Core implemenation > ----------------------------------- > > Key: ARQ-812 > URL: https://issues.jboss.org/browse/ARQ-812 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > Split Core and DBUnit modules in order to prepare the ground for extension model which will open integration with other tools such as Liquibase. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:43:59 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 07:43:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1147) Improve the column filtering feature to use custom IColumnFilter implementations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1147: ------------------------------- Fix Version/s: persistence_1.0.0.Alpha7 (was: persistence_1.0.0.next) > Improve the column filtering feature to use custom IColumnFilter implementations > -------------------------------------------------------------------------------- > > Key: ARQ-1147 > URL: https://issues.jboss.org/browse/ARQ-1147 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Vineet Reynolds > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > For now, APE implements column filtering based on column names specified in the {{excludeColumns}} attribute of the {{@ShouldMatchDataSet}} annotation (introduced in ARQ-772). This could be extended to allow custom {{IColumnFilter}} implementations to be plugged in during the verification phase. > The use of {{IColumnFilter}} implementations is described here: http://www.dbunit.org/faq.html#columnfilter -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:43:59 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 07:43:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1440) Performance drops > 300% In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1440: ------------------------------- Fix Version/s: persistence_1.0.0.Alpha7 (was: persistence_1.0.0.next) > Performance drops > 300% > ------------------------ > > Key: ARQ-1440 > URL: https://issues.jboss.org/browse/ARQ-1440 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: transaction_1.0.0.Alpha3, persistence_1.0.0.Alpha6 > Environment: Windows 7 / JDK 1.7.0_25 x64 / Oracle 11gR2 / Oracle ojdbc6 driver / Glassfish 3.1.2 b23 / Arquillian 1.1.0-Final / Arq persistence ext 1.0.0a6 / Arq tx ext 1.0.0a3 > Reporter: Noah White > Assignee: Bartosz Majsak > Priority: Critical > Fix For: persistence_1.0.0.Alpha7 > > > I updated my Arquillian environment to 1.1.0-Final, Arq persistence ext 1.0.0a6 and Arq 1.0.0a3 FROM Arq 1.0.1, persistence 1.0.0a5 (no tx ext in that env since it was part of the persistence ext) and my Arquillian persistence tests which deploy to a managed Glassfish container take over 3x as long as they did in the old environment. > For example one test which took 13s to run in the old environment now takes 44s. > This slow down only seems to affect tests which use the persistence extension. > Arquillian tests which do not use the persistence extension take the same amount of time as they did in the old environment. If I switch the environment back I see the performance goes back up for persistence extension tests. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:43:59 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 07:43:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1373) Cleanup does not work when none datasets provided for seeding In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1373: ------------------------------- Fix Version/s: persistence_1.0.0.Alpha7 (was: persistence_1.0.0.next) > Cleanup does not work when none datasets provided for seeding > ------------------------------------------------------------- > > Key: ARQ-1373 > URL: https://issues.jboss.org/browse/ARQ-1373 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > If "used tables only" strategy is selected and none datasets provided for the the test itself, cleanup procedure results with NPE. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:43:59 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 07:43:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1338) Should be able to define ad-hoc sql script through ApplyScript annotation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1338: ------------------------------- Fix Version/s: persistence_1.0.0.Alpha7 (was: persistence_1.0.0.next) > Should be able to define ad-hoc sql script through ApplyScript annotation > ------------------------------------------------------------------------- > > Key: ARQ-1338 > URL: https://issues.jboss.org/browse/ARQ-1338 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Minor > Fix For: persistence_1.0.0.Alpha7 > > > This should be handy for some cases, when external script is not really needed. In particular for some fiddling around with the tests during development / diagnostic of errors. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:44:00 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 07:44:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1360) Persistence extension doesn't handle certain special characters. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1360: ------------------------------- Fix Version/s: persistence_1.0.0.Alpha7 (was: persistence_1.0.0.next) > Persistence extension doesn't handle certain special characters. > ---------------------------------------------------------------- > > Key: ARQ-1360 > URL: https://issues.jboss.org/browse/ARQ-1360 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: John Ament > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > The persistence extension seems to choke when sql scripts (.sql files) contain certain characters. > 1. If I put "©" in my statement it treats the ; as a terminator. > 2. If I put a new line in my file, it treats that as a terminator. > 3. If I put a / (e.g. from xml) in my SQL, it gets very confused. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:44:00 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 07:44:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1572) Marry Persistence and JRebel extensions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1572: ------------------------------- Fix Version/s: persistence_1.0.0.Alpha7 (was: persistence_1.0.0.next) > Marry Persistence and JRebel extensions > --------------------------------------- > > Key: ARQ-1572 > URL: https://issues.jboss.org/browse/ARQ-1572 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Bernard Labno > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > JRebel extension currently does not pick up changes in datasets. > Here is how it works: > If there is no target/jrebel-temp/.../*.meta file for given deployment then it assumes user wants full redeploy. If such file is present then deployment is blocked and tests are run at once. > JRebel extension also checks if there is a rebel.xml file in the archive. If not then it generates such file based on exact content of the archive and explodes archive into target/jrebel-temp/*. > Now the problem is that if resource is not in the archive then it will not be included in generated rebel.xml and thus won't be picked up by JRebel. > Datasets are now automatically packed inside WEB-INF/lib/randomUUID.jar. JRebel will not substitute resources or classes from bundled libs. We could generate additional rebel.xml for that but I'd have to know what is the name of such archive and we would tightly couple both extensions. > It would be easiest if Persistence ext would pack datasets directly into WE-INF/classes. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:44:00 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 07:44:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1352) Script can not insert unix path separator '/' into the DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1352: ------------------------------- Fix Version/s: persistence_1.0.0.Alpha7 (was: persistence_1.0.0.next) > Script can not insert unix path separator '/' into the DB > --------------------------------------------------------- > > Key: ARQ-1352 > URL: https://issues.jboss.org/browse/ARQ-1352 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Sandor Bodo-Merle > Assignee: Sandor Bodo-Merle > Fix For: persistence_1.0.0.Alpha7 > > Attachments: 0001-ScriptExecutor-fix-commit-parsing.patch > > > I have a test class which try to insert a unix path value in the DB on schema creation: > @CreateSchema({"setup.sql"}) > public class UserTest { > ... > } > Th the ScriptExecutor introduced in 1.0.0.Alpha6 will iron out the '/' character from the path on insert - like in the following small example: > public class main { > public static void main(String[] args) { > final String ANSI_SQL_COMMENTS_PATTERN = "--.*|//.*|(?s)/\\\\*.*?\\\\*/|(?s)\\{.*?\\}"; > String script = "INSERT INTO config (name, value) VALUES ('path', '/home/sbodo/test.txt');"; > System.out.println(script.replaceAll(ANSI_SQL_COMMENTS_PATTERN, "")); > } > } > Output is: > INSERT INTO config (name, value) VALUES ('path', 'sbodo/test.txt'); > instead of: > INSERT INTO config (name, value) VALUES ('path', '/home/sbodo/test.txt'); > Tested with Jboss 7.1.1 and Postgres 9.1. > The test worked fine in 1.0.0.Alpha5. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:44:01 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 07:44:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1009) ClassNotFoundException when using CLEAN_INSERT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1009: ------------------------------- Fix Version/s: persistence_1.0.0.Alpha7 (was: persistence_1.0.0.next) > ClassNotFoundException when using CLEAN_INSERT > ---------------------------------------------- > > Key: ARQ-1009 > URL: https://issues.jboss.org/browse/ARQ-1009 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha4 > Environment: Windows 7, Java 1.6.0_31 > Reporter: Karsten Ohme > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > I set in arquillian.xml the configuration property: > CLEAN_INSERT > When starting the test I get a ClassNotFoundException in ConfigurationTypeConverter in line 182: > Object instance = Class.forName(value).newInstance(); -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:44:01 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 07:44:01 -0400 (EDT) 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 ] Aslak Knutsen updated ARQ-1444: ------------------------------- Fix Version/s: persistence_1.0.0.Alpha7 (was: persistence_1.0.0.next) > 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 > Fix For: persistence_1.0.0.Alpha7 > > > 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 was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:25:56 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:25:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1774) Prepare Persistence 1.0.0.ALpha7 In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1774: ---------------------------------- Summary: Prepare Persistence 1.0.0.ALpha7 Key: ARQ-1774 URL: https://issues.jboss.org/browse/ARQ-1774 Project: Arquillian Issue Type: Release Security Level: Public (Everyone can see) Components: Extension - Persistence Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: persistence_1.0.0.Alpha7 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:25:56 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:25:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1774) Prepare Persistence 1.0.0.ALphal In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1774: ------------------------------- Summary: Prepare Persistence 1.0.0.ALphal (was: Prepare Persistence 1.0.0.ALpha7) > Prepare Persistence 1.0.0.ALphal > -------------------------------- > > Key: ARQ-1774 > URL: https://issues.jboss.org/browse/ARQ-1774 > Project: Arquillian > Issue Type: Release > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: persistence_1.0.0.Alpha7 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:25:58 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:25:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1774) Prepare Persistence 1.0.0.Alpha7 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1774: ------------------------------- Summary: Prepare Persistence 1.0.0.Alpha7 (was: Prepare Persistence 1.0.0.ALphal) > Prepare Persistence 1.0.0.Alpha7 > -------------------------------- > > Key: ARQ-1774 > URL: https://issues.jboss.org/browse/ARQ-1774 > Project: Arquillian > Issue Type: Release > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: persistence_1.0.0.Alpha7 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:47:57 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:47:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1774) Prepare Persistence 1.0.0.Alpha7 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1774. ------------------------------ Resolution: Done pushed to nexus > Prepare Persistence 1.0.0.Alpha7 > -------------------------------- > > Key: ARQ-1774 > URL: https://issues.jboss.org/browse/ARQ-1774 > Project: Arquillian > Issue Type: Release > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: persistence_1.0.0.Alpha7 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:47:57 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:47:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1664) Provide custom table filter for seeding and cleaning databases In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1664. ------------------------------ > Provide custom table filter for seeding and cleaning databases > -------------------------------------------------------------- > > Key: ARQ-1664 > URL: https://issues.jboss.org/browse/ARQ-1664 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > In order to resolve Foreign Key dependency and remove tables in the correct order DatabaseSequenceFilter has been introduced. As it's causing significant performance drop, especially in Oracle DB, it should be possible to define custom table filtering through SPI mechanism. This is also useful when seeding database. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:47:57 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:47:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1440) Performance drops > 300% In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1440. ------------------------------ > Performance drops > 300% > ------------------------ > > Key: ARQ-1440 > URL: https://issues.jboss.org/browse/ARQ-1440 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: transaction_1.0.0.Alpha3, persistence_1.0.0.Alpha6 > Environment: Windows 7 / JDK 1.7.0_25 x64 / Oracle 11gR2 / Oracle ojdbc6 driver / Glassfish 3.1.2 b23 / Arquillian 1.1.0-Final / Arq persistence ext 1.0.0a6 / Arq tx ext 1.0.0a3 > Reporter: Noah White > Assignee: Bartosz Majsak > Priority: Critical > Fix For: persistence_1.0.0.Alpha7 > > > I updated my Arquillian environment to 1.1.0-Final, Arq persistence ext 1.0.0a6 and Arq 1.0.0a3 FROM Arq 1.0.1, persistence 1.0.0a5 (no tx ext in that env since it was part of the persistence ext) and my Arquillian persistence tests which deploy to a managed Glassfish container take over 3x as long as they did in the old environment. > For example one test which took 13s to run in the old environment now takes 44s. > This slow down only seems to affect tests which use the persistence extension. > Arquillian tests which do not use the persistence extension take the same amount of time as they did in the old environment. If I switch the environment back I see the performance goes back up for persistence extension tests. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:47:58 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:47:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1646) Add WildFly managed container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1646. ------------------------------ > Add WildFly managed container > ----------------------------- > > Key: ARQ-1646 > URL: https://issues.jboss.org/browse/ARQ-1646 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Trivial > Fix For: persistence_1.0.0.Alpha7 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:47:58 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:47:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1009) ClassNotFoundException when using CLEAN_INSERT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1009. ------------------------------ > ClassNotFoundException when using CLEAN_INSERT > ---------------------------------------------- > > Key: ARQ-1009 > URL: https://issues.jboss.org/browse/ARQ-1009 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha4 > Environment: Windows 7, Java 1.6.0_31 > Reporter: Karsten Ohme > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > I set in arquillian.xml the configuration property: > CLEAN_INSERT > When starting the test I get a ClassNotFoundException in ConfigurationTypeConverter in line 182: > Object instance = Class.forName(value).newInstance(); -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:47:59 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:47:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1309) Persistence extension does not work with Jacoco extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1309. ------------------------------ > Persistence extension does not work with Jacoco extension > --------------------------------------------------------- > > Key: ARQ-1309 > URL: https://issues.jboss.org/browse/ARQ-1309 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: 1.0.0.Alpha5 > Reporter: Peter Schonhofen > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > When the Jacoco and persistence extension is used together in a project, a "PersistenceExtensionInitializationException: Unable to create persistence configuration" is thrown. > The cause of the exception is that in the ConfigurationImporter class the createConfiguration method receives a fieldsWithValues map with a "$jacocoData" item in it. Because the method cannot process this item, it fails. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:47:59 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:47:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1572) Marry Persistence and JRebel extensions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1572. ------------------------------ > Marry Persistence and JRebel extensions > --------------------------------------- > > Key: ARQ-1572 > URL: https://issues.jboss.org/browse/ARQ-1572 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Bernard Labno > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > JRebel extension currently does not pick up changes in datasets. > Here is how it works: > If there is no target/jrebel-temp/.../*.meta file for given deployment then it assumes user wants full redeploy. If such file is present then deployment is blocked and tests are run at once. > JRebel extension also checks if there is a rebel.xml file in the archive. If not then it generates such file based on exact content of the archive and explodes archive into target/jrebel-temp/*. > Now the problem is that if resource is not in the archive then it will not be included in generated rebel.xml and thus won't be picked up by JRebel. > Datasets are now automatically packed inside WEB-INF/lib/randomUUID.jar. JRebel will not substitute resources or classes from bundled libs. We could generate additional rebel.xml for that but I'd have to know what is the name of such archive and we would tightly couple both extensions. > It would be easiest if Persistence ext would pack datasets directly into WE-INF/classes. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:47:59 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:47:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1355) Access the DatabaseConnection for additional verifications in an arquillian test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1355. ------------------------------ > Access the DatabaseConnection for additional verifications in an arquillian test > -------------------------------------------------------------------------------- > > Key: ARQ-1355 > URL: https://issues.jboss.org/browse/ARQ-1355 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Dominik Grupp > Assignee: Bartosz Majsak > Priority: Minor > Fix For: persistence_1.0.0.Alpha7 > > > There should be a possibility in an arquillian test to access the DatabaseConnection for additional verifications using dbunit. Using @UsingDataSet and @ShouldMatchDataSet first the already provided verifications could be done but then additional verification with dbunit using the DatabaseConnection - e.g. verfiy with a rowcount to make sure not more entries than expected have been created by the test. > Original post (with a code example): https://community.jboss.org/thread/222401?tstart=0 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:48:00 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:48:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1398) DatabaseSequenceFilter should be optional In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1398. ------------------------------ > DatabaseSequenceFilter should be optional > ----------------------------------------- > > Key: ARQ-1398 > URL: https://issues.jboss.org/browse/ARQ-1398 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > Disabled by default, possible to enable through dbunit configuration. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:48:00 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:48:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1147) Improve the column filtering feature to use custom IColumnFilter implementations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1147. ------------------------------ > Improve the column filtering feature to use custom IColumnFilter implementations > -------------------------------------------------------------------------------- > > Key: ARQ-1147 > URL: https://issues.jboss.org/browse/ARQ-1147 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Vineet Reynolds > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > For now, APE implements column filtering based on column names specified in the {{excludeColumns}} attribute of the {{@ShouldMatchDataSet}} annotation (introduced in ARQ-772). This could be extended to allow custom {{IColumnFilter}} implementations to be plugged in during the verification phase. > The use of {{IColumnFilter}} implementations is described here: http://www.dbunit.org/faq.html#columnfilter -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:48:00 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:48:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1373) Cleanup does not work when none datasets provided for seeding In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1373. ------------------------------ > Cleanup does not work when none datasets provided for seeding > ------------------------------------------------------------- > > Key: ARQ-1373 > URL: https://issues.jboss.org/browse/ARQ-1373 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > If "used tables only" strategy is selected and none datasets provided for the the test itself, cleanup procedure results with NPE. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:48:01 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:48:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1338) Should be able to define ad-hoc sql script through ApplyScript annotation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1338. ------------------------------ > Should be able to define ad-hoc sql script through ApplyScript annotation > ------------------------------------------------------------------------- > > Key: ARQ-1338 > URL: https://issues.jboss.org/browse/ARQ-1338 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Minor > Fix For: persistence_1.0.0.Alpha7 > > > This should be handy for some cases, when external script is not really needed. In particular for some fiddling around with the tests during development / diagnostic of errors. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:48:01 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:48:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1352) Script can not insert unix path separator '/' into the DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1352. ------------------------------ > Script can not insert unix path separator '/' into the DB > --------------------------------------------------------- > > Key: ARQ-1352 > URL: https://issues.jboss.org/browse/ARQ-1352 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Sandor Bodo-Merle > Assignee: Sandor Bodo-Merle > Fix For: persistence_1.0.0.Alpha7 > > Attachments: 0001-ScriptExecutor-fix-commit-parsing.patch > > > I have a test class which try to insert a unix path value in the DB on schema creation: > @CreateSchema({"setup.sql"}) > public class UserTest { > ... > } > Th the ScriptExecutor introduced in 1.0.0.Alpha6 will iron out the '/' character from the path on insert - like in the following small example: > public class main { > public static void main(String[] args) { > final String ANSI_SQL_COMMENTS_PATTERN = "--.*|//.*|(?s)/\\\\*.*?\\\\*/|(?s)\\{.*?\\}"; > String script = "INSERT INTO config (name, value) VALUES ('path', '/home/sbodo/test.txt');"; > System.out.println(script.replaceAll(ANSI_SQL_COMMENTS_PATTERN, "")); > } > } > Output is: > INSERT INTO config (name, value) VALUES ('path', 'sbodo/test.txt'); > instead of: > INSERT INTO config (name, value) VALUES ('path', '/home/sbodo/test.txt'); > Tested with Jboss 7.1.1 and Postgres 9.1. > The test worked fine in 1.0.0.Alpha5. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:49:56 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:49:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1360) Persistence extension doesn't handle certain special characters. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1360. ------------------------------ > Persistence extension doesn't handle certain special characters. > ---------------------------------------------------------------- > > Key: ARQ-1360 > URL: https://issues.jboss.org/browse/ARQ-1360 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: John Ament > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > The persistence extension seems to choke when sql scripts (.sql files) contain certain characters. > 1. If I put "©" in my statement it treats the ; as a terminator. > 2. If I put a new line in my file, it treats that as a terminator. > 3. If I put a / (e.g. from xml) in my SQL, it gets very confused. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:49:57 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:49:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-812) Split DBUnit and Core implemenation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-812. ----------------------------- > Split DBUnit and Core implemenation > ----------------------------------- > > Key: ARQ-812 > URL: https://issues.jboss.org/browse/ARQ-812 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > Split Core and DBUnit modules in order to prepare the ground for extension model which will open integration with other tools such as Liquibase. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:49:57 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:49:57 -0400 (EDT) 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 ] Aslak Knutsen closed ARQ-1444. ------------------------------ > 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 > Fix For: persistence_1.0.0.Alpha7 > > > 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 was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 08:49:57 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 08:49:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1530) Column ordering does not work properly due to DBUnit bug In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1530. ------------------------------ > Column ordering does not work properly due to DBUnit bug > -------------------------------------------------------- > > Key: ARQ-1530 > URL: https://issues.jboss.org/browse/ARQ-1530 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.Alpha7 > > > Details in the referenced forum thread. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 11:02:00 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 12 May 2014 11:02:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1772) Arquillian Debug does not print real event class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967178#comment-12967178 ] Karel Piwko commented on ARQ-1772: ---------------------------------- I can fix that to show interface name only if class is anonymous, wdyt? > Arquillian Debug does not print real event class > ------------------------------------------------ > > Key: ARQ-1772 > URL: https://issues.jboss.org/browse/ARQ-1772 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Karel Piwko > > When using inheritance to define events, Arquillian Debug prints out following: > {code} > (E) PrepareDrone > (O) EventRegisterObserver.register > (O) DroneConfigurator.prepareDrone > (E) DroneConfigurationEvent > (O) EventRegisterObserver.register > (E) DroneConfigurationEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) Before > (O) EventRegisterObserver.register > (O) DroneLifecycleManager.before > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (O) DroneEnhancer.enhanceDrone > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (O) DroneEnhancer.enhanceDrone > {code} > Which is not really super useful, as debug log can't show what actual events were fired. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 12:42:56 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 12:42:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1772) Arquillian Debug does not print real event class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967241#comment-12967241 ] Aslak Knutsen commented on ARQ-1772: ------------------------------------ Sounds reasonable.. > Arquillian Debug does not print real event class > ------------------------------------------------ > > Key: ARQ-1772 > URL: https://issues.jboss.org/browse/ARQ-1772 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Karel Piwko > > When using inheritance to define events, Arquillian Debug prints out following: > {code} > (E) PrepareDrone > (O) EventRegisterObserver.register > (O) DroneConfigurator.prepareDrone > (E) DroneConfigurationEvent > (O) EventRegisterObserver.register > (E) DroneConfigurationEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) Before > (O) EventRegisterObserver.register > (O) DroneLifecycleManager.before > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (O) DroneEnhancer.enhanceDrone > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (E) DroneLifecycleEvent > (O) EventRegisterObserver.register > (O) DroneEnhancer.enhanceDrone > {code} > Which is not really super useful, as debug log can't show what actual events were fired. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 14:50:56 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 12 May 2014 14:50:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1769) org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1769: ------------------------------- Component/s: Extension - Warp (was: Base Implementation) > org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > -------------------------------------------------------------------------- > > Key: ARQ-1769 > URL: https://issues.jboss.org/browse/ARQ-1769 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, 1.1.3.Final, 1.1.4.Final > Environment: Windows 7 Enterprise SP1 64-bit > Reporter: William Crowell > > I am using the following: > Arquillian Core: 1.1.4.Final (as well as 1.1.3.Final) > Arquillian Drone: 1.2.4.Final (I've tried Drone 2 as well) > Arquillian Warp: 1.0.0.Alpha7 (as well as 1.0.0.Beta1-SNAPSHOT) > Arquillian Transaction: 1.0.1.Final > Arquillian Tomcat 7 Embedded Container using Tomcat 7.0.27: 1.0.0.Final-SNAPSHOT > Spring: 3.2.4.RELEASE > Spring Web: 3.2.2.RELEASE > Spring Security: 3.1.4.RELEASE > Spring WebFlow: 2.4.0.RC1 > PrimeFaces 3.4.2 > JUnit: 4.8.2 > Mojarra 2.1.17 > I am receiving this exception: > java.lang.IllegalStateException: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:69) > ... > 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.LifecycleTestClassExecutor.afterRequest(LifecycleTestClassExecutor.java:78) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.request.RequestContextHandler.handleRequestContext(RequestContextHandler.java:93) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:151) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:120) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:93) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:183) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192) > at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160) > at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) > at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) > at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > ... > Caused by: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl.checkUnbound(LifecycleManagerStoreImpl.java:126) > at org.jboss.arquillian.warp.spi.LifecycleManager.checkUnbound(LifecycleManager.java:158) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:67) > ... 74 more -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 13 05:12:57 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 13 May 2014 05:12:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1763) Download boilerplate APKs for Droidium by Spacelift In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1763. ------------------------------------ Assignee: Stefan Miklosovic Fix Version/s: droidium_1.0.0.Beta1 Resolution: Done > Download boilerplate APKs for Droidium by Spacelift > --------------------------------------------------- > > Key: ARQ-1763 > URL: https://issues.jboss.org/browse/ARQ-1763 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha5 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Beta1 > > > Ftesting with Droidium native plugin requires selendroid-server.apk from Selendroid project. Web testing requires android-driver.apk from same project. > Right now, these apks need to be downloaded manually by user so he has to find it on the net and manually setup it in arq.xml. As this is not desired, Spacelift 1.0.0.Alpha2 can download these artifacts automatically and they can be downloaded to target/ when it is not found so user does not have to do a thing. > https://gist.github.com/kpiwko/10738725 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 14 10:17:57 2014 From: issues at jboss.org (Joe Punk (JIRA)) Date: Wed, 14 May 2014 10:17:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1387) Support code coverage for jar/war deployed by ZipImporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967823#comment-12967823 ] Joe Punk commented on ARQ-1387: ------------------------------- If you have ever installed dcevm, it hacks it's jar into your JDK installlation(for example: jdk1.7.0_25\jre\lib\ext\dcevm.jar). This jar contains interface org.objectweb.asm.ClassVisitor which is used while your integration test is run(or build?) instead of using org.objectweb.asm.ClassVisitor from org.jacoco:org.jacoco.core:0.7.1.201405082137. Maybe it's not your problem but I have solved this exception with removing dcevm.jar from jdk's folder. > Support code coverage for jar/war deployed by ZipImporter > --------------------------------------------------------- > > Key: ARQ-1387 > URL: https://issues.jboss.org/browse/ARQ-1387 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Environment: jdk 1.7, org.jacoco.core.0.6.2.20130203000 > Reporter: Andy Ma > Assignee: Aslak Knutsen > Labels: arquillian-jacoco, jacoco > Fix For: jacoco_1.0.0.Alpha6 > > > If deployed with ZipImporter like: > ShrinkWrap.create(ZipImporter.class, name) > .importFrom(new File(MODULE_PATH + "/" + name)).as(WebArchive.class); > the code coverage of imported archive can not be reported. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 14 10:31:56 2014 From: issues at jboss.org (Sona Jamborova (JIRA)) Date: Wed, 14 May 2014 10:31:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1775) Allow to disable/enable nativeEvents via arquillian.xml In-Reply-To: References: Message-ID: Sona Jamborova created ARQ-1775: ----------------------------------- Summary: Allow to disable/enable nativeEvents via arquillian.xml Key: ARQ-1775 URL: https://issues.jboss.org/browse/ARQ-1775 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Sona Jamborova Selenium 2 allows to enable/disable nativeEvents for WebDriver. This feature should be set before initialization of WebDriver instance. See: FirefoxProfile profile = new FirefoxProfile(); profile.setEnableNativeEvents(true); WebDriver driver = new FirefoxDriver(profile); Drone injects instance of FirefoxDriver and I have not any option how disable native Events for Firefox and Windows. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 14 10:51:56 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 14 May 2014 10:51:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1775) Allow to disable/enable nativeEvents via arquillian.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1775: ----------------------------- Affects Version/s: drone_1.3.0.Final > Allow to disable/enable nativeEvents via arquillian.xml > ------------------------------------------------------- > > Key: ARQ-1775 > URL: https://issues.jboss.org/browse/ARQ-1775 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.3.0.Final > Reporter: Sona Jamborova > > Selenium 2 allows to enable/disable nativeEvents for WebDriver. This feature should be set before initialization of WebDriver instance. See: > FirefoxProfile profile = new FirefoxProfile(); > profile.setEnableNativeEvents(true); > WebDriver driver = new FirefoxDriver(profile); > Drone injects instance of FirefoxDriver and I have not any option how disable native Events for Firefox and Windows. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 14 11:43:56 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Wed, 14 May 2014 11:43:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1776) Make class KarafManagedDeployableContainer compatible with OSGi JMX API 4.2 In-Reply-To: References: Message-ID: Martin Basovnik created ARQ-1776: ------------------------------------ Summary: Make class KarafManagedDeployableContainer compatible with OSGi JMX API 4.2 Key: ARQ-1776 URL: https://issues.jboss.org/browse/ARQ-1776 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Martin Basovnik Assignee: Thomas Diesler Method [KarafManagedDeployableContainer#undeploy|https://github.com/arquillian/arquillian-container-osgi/blob/c577df65c87435d07681ca34550e62310508c755/container/karaf/managed/src/main/java/org/jboss/arquillian/container/osgi/karaf/managed/KarafManagedDeployableContainer.java#L276] uses following method from class [BundleStateMBean|http://grepcode.com/file/repo1.maven.org/maven2/org.osgi/org.osgi.enterprise/5.0.0/org/osgi/jmx/framework/BundleStateMBean.java#432] which is available from API 5.0. We need to make it compatible with API 4.2. {code} CompositeData getBundle(long bundleIdentifier) throws IOException; {code} Solution is to exchange this method with those available in API 4.2. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 15 04:29:56 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Thu, 15 May 2014 04:29:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1776) Make class KarafManagedDeployableContainer compatible with OSGi API 4.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1776: --------------------------------- Summary: Make class KarafManagedDeployableContainer compatible with OSGi API 4.2 (was: Make class KarafManagedDeployableContainer compatible with OSGi JMX API 4.2 ) > Make class KarafManagedDeployableContainer compatible with OSGi API 4.2 > ------------------------------------------------------------------------ > > Key: ARQ-1776 > URL: https://issues.jboss.org/browse/ARQ-1776 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Method [KarafManagedDeployableContainer#undeploy|https://github.com/arquillian/arquillian-container-osgi/blob/c577df65c87435d07681ca34550e62310508c755/container/karaf/managed/src/main/java/org/jboss/arquillian/container/osgi/karaf/managed/KarafManagedDeployableContainer.java#L276] uses following method from class [BundleStateMBean|http://grepcode.com/file/repo1.maven.org/maven2/org.osgi/org.osgi.enterprise/5.0.0/org/osgi/jmx/framework/BundleStateMBean.java#432] which is available from API 5.0. We need to make it compatible with API 4.2. > {code} > CompositeData getBundle(long bundleIdentifier) throws IOException; > {code} > Solution is to exchange this method with those available in API 4.2. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 15 06:03:56 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Thu, 15 May 2014 06:03:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1776) Make class KarafManagedDeployableContainer compatible with OSGi API 4.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1776: --------------------------------- Description: Class [KarafManagedDeployableContainer|https://github.com/arquillian/arquillian-container-osgi/blob/c577df65c87435d07681ca34550e62310508c755/container/karaf/managed/src/main/java/org/jboss/arquillian/container/osgi/karaf/managed/KarafManagedDeployableContainer.java] uses two methods from JMX API for OSGi [5.0|http://www.osgi.org/javadoc/r5/enterprise/]. {code} BundleStateMBean#getBundle(long bundleIdentifier); ServiceStateMBean#listServices(String clazz, String filter); {code} We need to support OSGi API [4.2|http://www.osgi.org/javadoc/r4v42/] for JMX MBeans. Is it possible to get rid of these methods? was: Method [KarafManagedDeployableContainer#undeploy|https://github.com/arquillian/arquillian-container-osgi/blob/c577df65c87435d07681ca34550e62310508c755/container/karaf/managed/src/main/java/org/jboss/arquillian/container/osgi/karaf/managed/KarafManagedDeployableContainer.java#L276] uses following method from class [BundleStateMBean|http://grepcode.com/file/repo1.maven.org/maven2/org.osgi/org.osgi.enterprise/5.0.0/org/osgi/jmx/framework/BundleStateMBean.java#432] which is available from API 5.0. We need to make it compatible with API 4.2. {code} CompositeData getBundle(long bundleIdentifier) throws IOException; {code} Solution is to exchange this method with those available in API 4.2. > Make class KarafManagedDeployableContainer compatible with OSGi API 4.2 > ------------------------------------------------------------------------ > > Key: ARQ-1776 > URL: https://issues.jboss.org/browse/ARQ-1776 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Class [KarafManagedDeployableContainer|https://github.com/arquillian/arquillian-container-osgi/blob/c577df65c87435d07681ca34550e62310508c755/container/karaf/managed/src/main/java/org/jboss/arquillian/container/osgi/karaf/managed/KarafManagedDeployableContainer.java] uses two methods from JMX API for OSGi [5.0|http://www.osgi.org/javadoc/r5/enterprise/]. > {code} > BundleStateMBean#getBundle(long bundleIdentifier); > ServiceStateMBean#listServices(String clazz, String filter); > {code} > We need to support OSGi API [4.2|http://www.osgi.org/javadoc/r4v42/] for JMX MBeans. Is it possible to get rid of these methods? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 15 16:33:56 2014 From: issues at jboss.org (Pramod Kankure (JIRA)) Date: Thu, 15 May 2014 16:33:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1777) Test hangs on remote Tomcat 6 In-Reply-To: References: Message-ID: Pramod Kankure created ARQ-1777: ----------------------------------- Summary: Test hangs on remote Tomcat 6 Key: ARQ-1777 URL: https://issues.jboss.org/browse/ARQ-1777 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Pramod Kankure -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 15 16:37:56 2014 From: issues at jboss.org (Pramod Kankure (JIRA)) Date: Thu, 15 May 2014 16:37:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1777) Test hangs on remote Tomcat 6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Kankure updated ARQ-1777: -------------------------------- Description: I have observed that test hangs when executing on tomcat 6 remote container. My arquillian.xml looks like below. ( I don't use authentication for jmx) 1776 localhost 8090 The test do stops with an error when the server is down or wrong HTTP port is specified. It does execute @deployment method of the test but never comes to execute the test method annoted with [~test.todd] > Test hangs on remote Tomcat 6 > ----------------------------- > > Key: ARQ-1777 > URL: https://issues.jboss.org/browse/ARQ-1777 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Pramod Kankure > > I have observed that test hangs when executing on tomcat 6 remote container. > My arquillian.xml looks like below. ( I don't use authentication for jmx) > > xmlns="http://jboss.org/schema/arquillian" > xsi:schemaLocation="http://jboss.org/schema/arquillian > http://jboss.org/schema/arquillian/arquillian_1_0.xsd"> > > > > > 1776 > localhost > 8090 > > > > > The test do stops with an error when the server is down or wrong HTTP port is specified. It does execute @deployment method of the test but never comes to execute the test method annoted with [~test.todd] -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 10:53:56 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Fri, 16 May 2014 10:53:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1776) Make class KarafManagedDeployableContainer compatible with OSGi API 4.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1776: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-osgi/pull/15 > Make class KarafManagedDeployableContainer compatible with OSGi API 4.2 > ------------------------------------------------------------------------ > > Key: ARQ-1776 > URL: https://issues.jboss.org/browse/ARQ-1776 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Class [KarafManagedDeployableContainer|https://github.com/arquillian/arquillian-container-osgi/blob/c577df65c87435d07681ca34550e62310508c755/container/karaf/managed/src/main/java/org/jboss/arquillian/container/osgi/karaf/managed/KarafManagedDeployableContainer.java] uses two methods from JMX API for OSGi [5.0|http://www.osgi.org/javadoc/r5/enterprise/]. > {code} > BundleStateMBean#getBundle(long bundleIdentifier); > ServiceStateMBean#listServices(String clazz, String filter); > {code} > We need to support OSGi API [4.2|http://www.osgi.org/javadoc/r4v42/] for JMX MBeans. Is it possible to get rid of these methods? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 11:03:56 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Fri, 16 May 2014 11:03:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1776) Make class KarafManagedDeployableContainer compatible with OSGi API 4.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968450#comment-12968450 ] Martin Basovnik commented on ARQ-1776: -------------------------------------- Pull request also adds support for setting of multiple bootstrap complete services (property bootstrapCompleteService). These services are delimited by comma. > Make class KarafManagedDeployableContainer compatible with OSGi API 4.2 > ------------------------------------------------------------------------ > > Key: ARQ-1776 > URL: https://issues.jboss.org/browse/ARQ-1776 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Class [KarafManagedDeployableContainer|https://github.com/arquillian/arquillian-container-osgi/blob/c577df65c87435d07681ca34550e62310508c755/container/karaf/managed/src/main/java/org/jboss/arquillian/container/osgi/karaf/managed/KarafManagedDeployableContainer.java] uses two methods from JMX API for OSGi [5.0|http://www.osgi.org/javadoc/r5/enterprise/]. > {code} > BundleStateMBean#getBundle(long bundleIdentifier); > ServiceStateMBean#listServices(String clazz, String filter); > {code} > We need to support OSGi API [4.2|http://www.osgi.org/javadoc/r4v42/] for JMX MBeans. Is it possible to get rid of these methods? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 11:03:57 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Fri, 16 May 2014 11:03:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1776) Make class KarafManagedDeployableContainer compatible with OSGi API 4.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968450#comment-12968450 ] Martin Basovnik edited comment on ARQ-1776 at 5/16/14 11:03 AM: ---------------------------------------------------------------- [Pull request|https://github.com/arquillian/arquillian-container-osgi/pull/15] also adds support for setting of multiple bootstrap complete services (property bootstrapCompleteService). These services are delimited by comma. was (Author: mbasovni): Pull request also adds support for setting of multiple bootstrap complete services (property bootstrapCompleteService). These services are delimited by comma. > Make class KarafManagedDeployableContainer compatible with OSGi API 4.2 > ------------------------------------------------------------------------ > > Key: ARQ-1776 > URL: https://issues.jboss.org/browse/ARQ-1776 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Class [KarafManagedDeployableContainer|https://github.com/arquillian/arquillian-container-osgi/blob/c577df65c87435d07681ca34550e62310508c755/container/karaf/managed/src/main/java/org/jboss/arquillian/container/osgi/karaf/managed/KarafManagedDeployableContainer.java] uses two methods from JMX API for OSGi [5.0|http://www.osgi.org/javadoc/r5/enterprise/]. > {code} > BundleStateMBean#getBundle(long bundleIdentifier); > ServiceStateMBean#listServices(String clazz, String filter); > {code} > We need to support OSGi API [4.2|http://www.osgi.org/javadoc/r4v42/] for JMX MBeans. Is it possible to get rid of these methods? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 11:17:57 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Fri, 16 May 2014 11:17:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1778) Add support for automatic starting of bundle after installation In-Reply-To: References: Message-ID: Martin Basovnik created ARQ-1778: ------------------------------------ Summary: Add support for automatic starting of bundle after installation Key: ARQ-1778 URL: https://issues.jboss.org/browse/ARQ-1778 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Martin Basovnik Assignee: Thomas Diesler Bundle is not started automaticly after installation now. Create new container property **autostartBundle**. It's type will be {{boolean}} and default value {{false}}. BundleContext cannot be injected in application servers (e.g. EAP) and arquillian tests cannot be shared now with both containers. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 12:01:58 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Fri, 16 May 2014 12:01:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1778) Add support for automatic starting of bundle after installation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1778: --------------------------------- Description: Bundle is not started automaticly after installation now. Create new container property **autostartBundle**. It's type will be {{boolean}} and default value {{false}}. BundleContext cannot be injected in application servers (e.g. EAP) and arquillian tests cannot be shared now with both containers. Annotation {{@org.jboss.arquillian.osgi.StartLevelAware(autostart = true)}} does not solve this problem, because maven artifact with this annotation can add another container on classpath and this is problem. was: Bundle is not started automaticly after installation now. Create new container property **autostartBundle**. It's type will be {{boolean}} and default value {{false}}. BundleContext cannot be injected in application servers (e.g. EAP) and arquillian tests cannot be shared now with both containers. > Add support for automatic starting of bundle after installation > --------------------------------------------------------------- > > Key: ARQ-1778 > URL: https://issues.jboss.org/browse/ARQ-1778 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Bundle is not started automaticly after installation now. > Create new container property **autostartBundle**. It's type will be {{boolean}} and default value {{false}}. > BundleContext cannot be injected in application servers (e.g. EAP) and arquillian tests cannot be shared now with both containers. > Annotation {{@org.jboss.arquillian.osgi.StartLevelAware(autostart = true)}} does not solve this problem, because maven artifact with this annotation can add another container on classpath and this is problem. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 12:01:58 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Fri, 16 May 2014 12:01:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1778) Add support for automatic starting of bundle after installation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1778: --------------------------------- Description: Bundle is not started automaticly after installation now. Create new container property *autostartBundle*. It's type will be {{boolean}} and default value {{false}}. BundleContext cannot be injected in application servers (e.g. EAP) and arquillian tests cannot be shared now with both containers. Annotation {{@org.jboss.arquillian.osgi.StartLevelAware(autostart = true)}} does not solve this problem, because maven artifact with this annotation can add another container on classpath and this is problem. was: Bundle is not started automaticly after installation now. Create new container property **autostartBundle**. It's type will be {{boolean}} and default value {{false}}. BundleContext cannot be injected in application servers (e.g. EAP) and arquillian tests cannot be shared now with both containers. Annotation {{@org.jboss.arquillian.osgi.StartLevelAware(autostart = true)}} does not solve this problem, because maven artifact with this annotation can add another container on classpath and this is problem. > Add support for automatic starting of bundle after installation > --------------------------------------------------------------- > > Key: ARQ-1778 > URL: https://issues.jboss.org/browse/ARQ-1778 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Bundle is not started automaticly after installation now. > Create new container property *autostartBundle*. It's type will be {{boolean}} and default value {{false}}. > BundleContext cannot be injected in application servers (e.g. EAP) and arquillian tests cannot be shared now with both containers. > Annotation {{@org.jboss.arquillian.osgi.StartLevelAware(autostart = true)}} does not solve this problem, because maven artifact with this annotation can add another container on classpath and this is problem. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 18:43:56 2014 From: issues at jboss.org (Cesar Ricardez (JIRA)) Date: Fri, 16 May 2014 18:43:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-364) Spurious (?) warnings about "More then one reference to the same implementation was found for org.jboss.arquillian.spi.ApplicationArchiveGenerator, please verify you classpath" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968551#comment-12968551 ] Cesar Ricardez commented on ARQ-364: ------------------------------------ I'm going to check the typo... i think the warning is ok like [~aslak] said > Spurious (?) warnings about "More then one reference to the same implementation was found for org.jboss.arquillian.spi.ApplicationArchiveGenerator, please verify you classpath" > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: ARQ-364 > URL: https://issues.jboss.org/browse/ARQ-364 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Reporter: Bob McWhirter > Priority: Trivial > > In our Arquillian+RSpec (JRuby) integration, everything works, but we repeatedly get this warning: > {noformat} > [WARNING] Feb 8, 2011 10:46:57 AM org.jboss.arquillian.impl.DynamicServiceLoader verifySameImplementation > [WARNING] WARNING: More then one reference to the same implementation was found for org.jboss.arquillian.spi.ApplicationArchiveGenerator, please verify you classpath > {noformat} > Would be lovely to have one of: > * Instructions on how to solve the root cause (which classpath? I think we have 3: maven's, jruby's and AS's...) > * Instructions on how to mute the warning -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sat May 17 09:15:58 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Sat, 17 May 2014 09:15:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1778) Add global container setting for bundle autostart after deployment. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1778: --------------------------------- Summary: Add global container setting for bundle autostart after deployment. (was: Add support for automatic starting of bundle after installation) > Add global container setting for bundle autostart after deployment. > ------------------------------------------------------------------- > > Key: ARQ-1778 > URL: https://issues.jboss.org/browse/ARQ-1778 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Bundle is not started automaticly after installation now. > Create new container property *autostartBundle*. It's type will be {{boolean}} and default value {{false}}. > BundleContext cannot be injected in application servers (e.g. EAP) and arquillian tests cannot be shared now with both containers. > Annotation {{@org.jboss.arquillian.osgi.StartLevelAware(autostart = true)}} does not solve this problem, because maven artifact with this annotation can add another container on classpath and this is problem. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sat May 17 09:29:56 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Sat, 17 May 2014 09:29:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1778) Add global container setting for bundle autostart after deployment. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1778: --------------------------------- Description: Bundle is not started automaticly after deployment. It is possible to use annotation {{@StartLevelAware(autostart = true)}} for specific test now. Add new global container property *autostartBundle*. This will cause autostart of all deployed bundles. If either annotation of specific bundle or container property will have positive value bundle will be started. One setting with positive value will always override the second one with negative value. Property type will be {{boolean}} and default value {{false}}. was: Bundle is not started automaticly after installation now. Create new container property *autostartBundle*. It's type will be {{boolean}} and default value {{false}}. BundleContext cannot be injected in application servers (e.g. EAP) and arquillian tests cannot be shared now with both containers. Annotation {{@org.jboss.arquillian.osgi.StartLevelAware(autostart = true)}} does not solve this problem, because maven artifact with this annotation can add another container on classpath and this is problem. > Add global container setting for bundle autostart after deployment. > ------------------------------------------------------------------- > > Key: ARQ-1778 > URL: https://issues.jboss.org/browse/ARQ-1778 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Bundle is not started automaticly after deployment. It is possible to use annotation {{@StartLevelAware(autostart = true)}} for specific test now. > Add new global container property *autostartBundle*. This will cause autostart of all deployed bundles. If either annotation of specific bundle or container property will have positive value bundle will be started. One setting with positive value will always override the second one with negative value. > Property type will be {{boolean}} and default value {{false}}. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sat May 17 09:33:56 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Sat, 17 May 2014 09:33:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1778) Add global container setting for bundle autostart after deployment. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1778: --------------------------------- Description: Bundle is not started automaticly after deployment. It is possible to use annotation {{@StartLevelAware(autostart = true)}} for specific test now. Add new global container property *autostartBundle*. This will cause autostart of every deployed bundle via container's public method {{deploy(Archive archive)}}. If either annotation of specific bundle or container property will have positive value bundle will be started. One setting with positive value will always override the second one with negative value. Property type will be {{boolean}} and default value {{false}}. was: Bundle is not started automaticly after deployment. It is possible to use annotation {{@StartLevelAware(autostart = true)}} for specific test now. Add new global container property *autostartBundle*. This will cause autostart of all deployed bundles. If either annotation of specific bundle or container property will have positive value bundle will be started. One setting with positive value will always override the second one with negative value. Property type will be {{boolean}} and default value {{false}}. > Add global container setting for bundle autostart after deployment. > ------------------------------------------------------------------- > > Key: ARQ-1778 > URL: https://issues.jboss.org/browse/ARQ-1778 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Bundle is not started automaticly after deployment. It is possible to use annotation {{@StartLevelAware(autostart = true)}} for specific test now. > Add new global container property *autostartBundle*. This will cause autostart of every deployed bundle via container's public method {{deploy(Archive archive)}}. If either annotation of specific bundle or container property will have positive value bundle will be started. One setting with positive value will always override the second one with negative value. > Property type will be {{boolean}} and default value {{false}}. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sat May 17 10:55:56 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Sat, 17 May 2014 10:55:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1778) Add global container setting for bundle autostart after deployment. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1778: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-osgi/pull/16 > Add global container setting for bundle autostart after deployment. > ------------------------------------------------------------------- > > Key: ARQ-1778 > URL: https://issues.jboss.org/browse/ARQ-1778 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Bundle is not started automaticly after deployment. It is possible to use annotation {{@StartLevelAware(autostart = true)}} for specific test now. > Add new global container property *autostartBundle*. This will cause autostart of every deployed bundle via container's public method {{deploy(Archive archive)}}. If either annotation of specific bundle or container property will have positive value bundle will be started. One setting with positive value will always override the second one with negative value. > Property type will be {{boolean}} and default value {{false}}. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sat May 17 11:07:56 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Sat, 17 May 2014 11:07:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1778) Add global container setting for bundle autostart after deployment. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968568#comment-12968568 ] Martin Basovnik commented on ARQ-1778: -------------------------------------- I would like to create a unit test for this feature but I do not want to modify {{arquillian.xml}} file. I have created *ResourceProvider* for container configuration class but injection into my test works only in client tests ({{@RunAsClient}}). When I modify the configuration and then execute another "in-container" test, some classes are missing in deployed bundle (e.g. {{KarafManagedContainerConfiguration}} and others). Why? I do not use this class in this method, just in client method. > Add global container setting for bundle autostart after deployment. > ------------------------------------------------------------------- > > Key: ARQ-1778 > URL: https://issues.jboss.org/browse/ARQ-1778 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Bundle is not started automaticly after deployment. It is possible to use annotation {{@StartLevelAware(autostart = true)}} for specific test now. > Add new global container property *autostartBundle*. This will cause autostart of every deployed bundle via container's public method {{deploy(Archive archive)}}. If either annotation of specific bundle or container property will have positive value bundle will be started. One setting with positive value will always override the second one with negative value. > Property type will be {{boolean}} and default value {{false}}. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sat May 17 11:15:58 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Sat, 17 May 2014 11:15:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1778) Add global container setting for bundle autostart after deployment. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968568#comment-12968568 ] Martin Basovnik edited comment on ARQ-1778 at 5/17/14 11:14 AM: ---------------------------------------------------------------- I would like to create a unit test for this feature but I do not want to modify {{arquillian.xml}} file. I have created *ResourceProvider* for container configuration class but injection into my test works only in _client_ tests ({{@RunAsClient}}). When I modify the configuration in client test and then execute another _in-container_ test, some classes are missing in deployed bundle (e.g. {{KarafManagedContainerConfiguration}} and others). Why? I do not use this class in this test, only in that client test. How can I inject configuration via {{@ArquillianResource}} (it is already implemented) into in-container test? Or how to make a client test independent of in-container test? was (Author: mbasovni): I would like to create a unit test for this feature but I do not want to modify {{arquillian.xml}} file. I have created *ResourceProvider* for container configuration class but injection into my test works only in client tests ({{@RunAsClient}}). When I modify the configuration and then execute another "in-container" test, some classes are missing in deployed bundle (e.g. {{KarafManagedContainerConfiguration}} and others). Why? I do not use this class in this method, just in client method. > Add global container setting for bundle autostart after deployment. > ------------------------------------------------------------------- > > Key: ARQ-1778 > URL: https://issues.jboss.org/browse/ARQ-1778 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Bundle is not started automaticly after deployment. It is possible to use annotation {{@StartLevelAware(autostart = true)}} for specific test now. > Add new global container property *autostartBundle*. This will cause autostart of every deployed bundle via container's public method {{deploy(Archive archive)}}. If either annotation of specific bundle or container property will have positive value bundle will be started. One setting with positive value will always override the second one with negative value. > Property type will be {{boolean}} and default value {{false}}. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sun May 18 13:27:56 2014 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Sun, 18 May 2014 13:27:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1750) Support javaVmArguments configuration option to control forked vm In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Poul reassigned ARQ-1750: --------------------------------- Assignee: Gerhard Poul > Support javaVmArguments configuration option to control forked vm > ----------------------------------------------------------------- > > Key: ARQ-1750 > URL: https://issues.jboss.org/browse/ARQ-1750 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Assignee: Gerhard Poul > > Support configuration option javaVmArguments to add extra information to the launched WLP vm. > * memory settings > * debug options > java [javaVmArguments] -javaagent:lib/bootstrap-agent.jar -jar lib/ws-launch.jar -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sun May 18 13:27:56 2014 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Sun, 18 May 2014 13:27:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1750) Support javaVmArguments configuration option to control forked vm In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Poul updated ARQ-1750: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-was/pull/19 > Support javaVmArguments configuration option to control forked vm > ----------------------------------------------------------------- > > Key: ARQ-1750 > URL: https://issues.jboss.org/browse/ARQ-1750 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Assignee: Gerhard Poul > > Support configuration option javaVmArguments to add extra information to the launched WLP vm. > * memory settings > * debug options > java [javaVmArguments] -javaagent:lib/bootstrap-agent.jar -jar lib/ws-launch.jar -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sun May 18 13:27:57 2014 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Sun, 18 May 2014 13:27:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1750) Support javaVmArguments configuration option to control forked vm In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968589#comment-12968589 ] Gerhard Poul commented on ARQ-1750: ----------------------------------- I added a pull request that hopefully covers this. > Support javaVmArguments configuration option to control forked vm > ----------------------------------------------------------------- > > Key: ARQ-1750 > URL: https://issues.jboss.org/browse/ARQ-1750 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Assignee: Gerhard Poul > > Support configuration option javaVmArguments to add extra information to the launched WLP vm. > * memory settings > * debug options > java [javaVmArguments] -javaagent:lib/bootstrap-agent.jar -jar lib/ws-launch.jar -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 19 05:32:57 2014 From: issues at jboss.org (=?UTF-8?Q?Thomas_K=C3=BCstermann_=28JIRA=29?=) Date: Mon, 19 May 2014 05:32:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1779) Test are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter In-Reply-To: References: Message-ID: Thomas K?stermann created ARQ-1779: -------------------------------------- Summary: Test are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter Key: ARQ-1779 URL: https://issues.jboss.org/browse/ARQ-1779 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha7 Reporter: Thomas K?stermann Assignee: Bartosz Majsak Forum reference: https://community.jboss.org/message/874117 The following test case succeeds (green bar) although it should fail: {code:java} @RunWith(Arquillian.class) @DataSource("java:oracleDS") @Cleanup(phase=TestExecutionPhase.NONE) @ApplyScriptBefore("deploy-db-functionality.sql") @ApplyScriptAfter("undeploy-db-functionality.sql") public class PersistenceIT { // @Deployment ... @Test @ApplyScriptBefore("trigger-db-functionality.sql") public void shouldFail() { Assert.fail("should fail, but doesn't"); } } {code} Removing class level annotations does not work either: {code:java} @Test @ApplyScriptBefore({ "deploy-db-functionality.sql", "trigger-db-functionality.sql" }) @ApplyScriptAfter("undeploy-db-functionality.sql") public void shouldFail() { ... } {code} What actually works is to use only one ApplyScriptBefore / ApplyScriptAfter annotation per test, each with only one script to execute. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 19 05:34:58 2014 From: issues at jboss.org (=?UTF-8?Q?Thomas_K=C3=BCstermann_=28JIRA=29?=) Date: Mon, 19 May 2014 05:34:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1779) Tests are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas K?stermann updated ARQ-1779: ----------------------------------- Summary: Tests are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter (was: Test are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter) > Tests are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter > ----------------------------------------------------------------------------------- > > Key: ARQ-1779 > URL: https://issues.jboss.org/browse/ARQ-1779 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Thomas K?stermann > Assignee: Bartosz Majsak > > Forum reference: https://community.jboss.org/message/874117 > The following test case succeeds (green bar) although it should fail: > {code:java} > @RunWith(Arquillian.class) > @DataSource("java:oracleDS") > @Cleanup(phase=TestExecutionPhase.NONE) > @ApplyScriptBefore("deploy-db-functionality.sql") > @ApplyScriptAfter("undeploy-db-functionality.sql") > public class PersistenceIT { > // @Deployment ... > > @Test > @ApplyScriptBefore("trigger-db-functionality.sql") > public void shouldFail() { > Assert.fail("should fail, but doesn't"); > } > } > {code} > Removing class level annotations does not work either: > {code:java} > @Test > @ApplyScriptBefore({ "deploy-db-functionality.sql", "trigger-db-functionality.sql" }) > @ApplyScriptAfter("undeploy-db-functionality.sql") > public void shouldFail() { ... } > {code} > What actually works is to use only one ApplyScriptBefore / ApplyScriptAfter annotation per test, each with only one script to execute. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 19 05:36:57 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Mon, 19 May 2014 05:36:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1779) Tests are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1779: -------------------------------- Fix Version/s: persistence_1.0.0.next > Tests are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter > ----------------------------------------------------------------------------------- > > Key: ARQ-1779 > URL: https://issues.jboss.org/browse/ARQ-1779 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Thomas K?stermann > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > Forum reference: https://community.jboss.org/message/874117 > The following test case succeeds (green bar) although it should fail: > {code:java} > @RunWith(Arquillian.class) > @DataSource("java:oracleDS") > @Cleanup(phase=TestExecutionPhase.NONE) > @ApplyScriptBefore("deploy-db-functionality.sql") > @ApplyScriptAfter("undeploy-db-functionality.sql") > public class PersistenceIT { > // @Deployment ... > > @Test > @ApplyScriptBefore("trigger-db-functionality.sql") > public void shouldFail() { > Assert.fail("should fail, but doesn't"); > } > } > {code} > Removing class level annotations does not work either: > {code:java} > @Test > @ApplyScriptBefore({ "deploy-db-functionality.sql", "trigger-db-functionality.sql" }) > @ApplyScriptAfter("undeploy-db-functionality.sql") > public void shouldFail() { ... } > {code} > What actually works is to use only one ApplyScriptBefore / ApplyScriptAfter annotation per test, each with only one script to execute. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 19 08:10:57 2014 From: issues at jboss.org (=?UTF-8?Q?Thomas_K=C3=BCstermann_=28JIRA=29?=) Date: Mon, 19 May 2014 08:10:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1779) Tests are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968711#comment-12968711 ] Thomas K?stermann commented on ARQ-1779: ---------------------------------------- I activated {{arquillian.debug}} and observed a bunch of {{(E) ScriptExecutionException}} entries. And indeed, there were errors in the scripts to execute (missed to set {{sqlDialect}} to oracle). So the problem is not that the tests aren't executed. The issue is that the exceptions don't fail the tests. The exceptions are not reported, neither in Eclipse nor on the command line (using maven). > Tests are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter > ----------------------------------------------------------------------------------- > > Key: ARQ-1779 > URL: https://issues.jboss.org/browse/ARQ-1779 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: Thomas K?stermann > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > Forum reference: https://community.jboss.org/message/874117 > The following test case succeeds (green bar) although it should fail: > {code:java} > @RunWith(Arquillian.class) > @DataSource("java:oracleDS") > @Cleanup(phase=TestExecutionPhase.NONE) > @ApplyScriptBefore("deploy-db-functionality.sql") > @ApplyScriptAfter("undeploy-db-functionality.sql") > public class PersistenceIT { > // @Deployment ... > > @Test > @ApplyScriptBefore("trigger-db-functionality.sql") > public void shouldFail() { > Assert.fail("should fail, but doesn't"); > } > } > {code} > Removing class level annotations does not work either: > {code:java} > @Test > @ApplyScriptBefore({ "deploy-db-functionality.sql", "trigger-db-functionality.sql" }) > @ApplyScriptAfter("undeploy-db-functionality.sql") > public void shouldFail() { ... } > {code} > What actually works is to use only one ApplyScriptBefore / ApplyScriptAfter annotation per test, each with only one script to execute. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 19 10:47:00 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Mon, 19 May 2014 10:47:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1780) Class AbstractOSGiApplicationArchiveProcessor cannot parse import packages correctly In-Reply-To: References: Message-ID: Martin Basovnik created ARQ-1780: ------------------------------------ Summary: Class AbstractOSGiApplicationArchiveProcessor cannot parse import packages correctly Key: ARQ-1780 URL: https://issues.jboss.org/browse/ARQ-1780 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Martin Basovnik Assignee: Thomas Diesler Method {{enhanceApplicationArchive()}} in specified class cannot parse import packages from file {{MANIFEST.MF}} correctly. Input string must be split only by those commas that are not surrounded by double-quotes. Example: {{org.jboss.arquillian.junit;version="[X.0.0,Y.0.0)";extra="A,B",org.junit"}} must be split as follows: {{org.jboss.arquillian.junit;version="[X.0.0,Y.0.0)";extra="A,B"}} and {{org.junit}} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 19 10:50:56 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Mon, 19 May 2014 10:50:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1780) Fix parsing of import-export packages in class AbstractOSGiApplicationArchiveProcessor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1780: --------------------------------- Summary: Fix parsing of import-export packages in class AbstractOSGiApplicationArchiveProcessor (was: Class AbstractOSGiApplicationArchiveProcessor cannot parse import packages correctly) > Fix parsing of import-export packages in class AbstractOSGiApplicationArchiveProcessor > -------------------------------------------------------------------------------------- > > Key: ARQ-1780 > URL: https://issues.jboss.org/browse/ARQ-1780 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Method {{enhanceApplicationArchive()}} in specified class cannot parse import packages from file {{MANIFEST.MF}} correctly. Input string must be split only by those commas that are not surrounded by double-quotes. > Example: > {{org.jboss.arquillian.junit;version="[X.0.0,Y.0.0)";extra="A,B",org.junit"}} > must be split as follows: > {{org.jboss.arquillian.junit;version="[X.0.0,Y.0.0)";extra="A,B"}} and {{org.junit}} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 19 12:26:56 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Mon, 19 May 2014 12:26:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1780) Fix parsing of import-export packages in class AbstractOSGiApplicationArchiveProcessor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1780: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-osgi/pull/17 > Fix parsing of import-export packages in class AbstractOSGiApplicationArchiveProcessor > -------------------------------------------------------------------------------------- > > Key: ARQ-1780 > URL: https://issues.jboss.org/browse/ARQ-1780 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Method {{enhanceApplicationArchive()}} in specified class cannot parse import packages from file {{MANIFEST.MF}} correctly. Input string must be split only by those commas that are not surrounded by double-quotes. > Example: > {{org.jboss.arquillian.junit;version="[X.0.0,Y.0.0)";extra="A,B",org.junit"}} > must be split as follows: > {{org.jboss.arquillian.junit;version="[X.0.0,Y.0.0)";extra="A,B"}} and {{org.junit}} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 19 16:44:56 2014 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Mon, 19 May 2014 16:44:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1750) Support javaVmArguments configuration option to control forked vm In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Poul updated ARQ-1750: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: was_1.0.0.next Resolution: Done merged into master > Support javaVmArguments configuration option to control forked vm > ----------------------------------------------------------------- > > Key: ARQ-1750 > URL: https://issues.jboss.org/browse/ARQ-1750 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Assignee: Gerhard Poul > Fix For: was_1.0.0.next > > > Support configuration option javaVmArguments to add extra information to the launched WLP vm. > * memory settings > * debug options > java [javaVmArguments] -javaagent:lib/bootstrap-agent.jar -jar lib/ws-launch.jar -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 20 22:54:56 2014 From: issues at jboss.org (Cesar Ricardez (JIRA)) Date: Tue, 20 May 2014 22:54:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1773) JUnittests pass when exception is thrown from @Before-annotated method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969212#comment-12969212 ] Cesar Ricardez commented on ARQ-1773: ------------------------------------- I think this is related to ARQ-1758 > JUnittests pass when exception is thrown from @Before-annotated method > ---------------------------------------------------------------------- > > Key: ARQ-1773 > URL: https://issues.jboss.org/browse/ARQ-1773 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.4.Final > Reporter: Mattias Persson > Attachments: arquillian_test_should_fail.zip > > > When an exception is thrown from a method with @Before, tests that should fail actually pass when using Arquillian 1.1.4.Final. When stepping down to 1.1.3.Final, the tests fail as expected. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 20 23:54:56 2014 From: issues at jboss.org (Cesar Ricardez (JIRA)) Date: Tue, 20 May 2014 23:54:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1770) Root.war deployed to Wildfly gives wrong @ArquillianResource URL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969214#comment-12969214 ] Cesar Ricardez commented on ARQ-1770: ------------------------------------- Also, this bus is affecting when using managed: Caused by: java.lang.IllegalStateException: Error launching request at http://127.0.0.1:8080/ROOT/ArquillianServletRunner?outputMode=serializedObject&className=se.shouldfailtest.ShouldFailTest&methodName=shouldFail. No result returned at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.executeWithRetry(ServletMethodExecutor.java:139) at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.invoke(ServletMethodExecutor.java:99) at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) 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:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) 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.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > Root.war deployed to Wildfly gives wrong @ArquillianResource URL > ---------------------------------------------------------------- > > Key: ARQ-1770 > URL: https://issues.jboss.org/browse/ARQ-1770 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Matej Briskar > Attachments: arquillian_test_should_fail.zip > > > This bug is a small one and had easy workaround, but it happens. > When I deploy a ROOT.war to the Wildfly embedded container, the returned @ArquillianResource Url url gives localhost:8080/ROOT instead of the correct localhost:8080/. Tested with wildfly 8.1.0.CR1 dependency version. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 20 23:54:57 2014 From: issues at jboss.org (Cesar Ricardez (JIRA)) Date: Tue, 20 May 2014 23:54:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1770) Root.war deployed to Wildfly gives wrong @ArquillianResource URL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Ricardez updated ARQ-1770: -------------------------------- Attachment: arquillian_test_should_fail.zip The file to reproduce error > Root.war deployed to Wildfly gives wrong @ArquillianResource URL > ---------------------------------------------------------------- > > Key: ARQ-1770 > URL: https://issues.jboss.org/browse/ARQ-1770 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Matej Briskar > Attachments: arquillian_test_should_fail.zip > > > This bug is a small one and had easy workaround, but it happens. > When I deploy a ROOT.war to the Wildfly embedded container, the returned @ArquillianResource Url url gives localhost:8080/ROOT instead of the correct localhost:8080/. Tested with wildfly 8.1.0.CR1 dependency version. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 21 16:24:57 2014 From: issues at jboss.org (Pramod Kankure (JIRA)) Date: Wed, 21 May 2014 16:24:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1777) Test hangs on remote Tomcat 6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969511#comment-12969511 ] Pramod Kankure commented on ARQ-1777: ------------------------------------- I debugged this and it happens in copy method of IOUtils. The reason for that is setting of setFixedLengthStreamingMode and then using buffer of 4096 size. This causes problem. Removal of setFixedLengthStreamingMode fixes the issue. Can existing contributors fix this? > Test hangs on remote Tomcat 6 > ----------------------------- > > Key: ARQ-1777 > URL: https://issues.jboss.org/browse/ARQ-1777 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Pramod Kankure > > I have observed that test hangs when executing on tomcat 6 remote container. > My arquillian.xml looks like below. ( I don't use authentication for jmx) > > xmlns="http://jboss.org/schema/arquillian" > xsi:schemaLocation="http://jboss.org/schema/arquillian > http://jboss.org/schema/arquillian/arquillian_1_0.xsd"> > > > > > 1776 > localhost > 8090 > > > > > The test do stops with an error when the server is down or wrong HTTP port is specified. It does execute @deployment method of the test but never comes to execute the test method annoted with [~test.todd] -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 22 07:14:56 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Thu, 22 May 2014 07:14:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1776) Create branch for OSGi containers compatible with OSGi 4.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1776: --------------------------------- Summary: Create branch for OSGi containers compatible with OSGi 4.2 (was: Make class KarafManagedDeployableContainer compatible with OSGi API 4.2 ) > Create branch for OSGi containers compatible with OSGi 4.2 > ---------------------------------------------------------- > > Key: ARQ-1776 > URL: https://issues.jboss.org/browse/ARQ-1776 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Class [KarafManagedDeployableContainer|https://github.com/arquillian/arquillian-container-osgi/blob/c577df65c87435d07681ca34550e62310508c755/container/karaf/managed/src/main/java/org/jboss/arquillian/container/osgi/karaf/managed/KarafManagedDeployableContainer.java] uses two methods from JMX API for OSGi [5.0|http://www.osgi.org/javadoc/r5/enterprise/]. > {code} > BundleStateMBean#getBundle(long bundleIdentifier); > ServiceStateMBean#listServices(String clazz, String filter); > {code} > We need to support OSGi API [4.2|http://www.osgi.org/javadoc/r4v42/] for JMX MBeans. Is it possible to get rid of these methods? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 22 07:14:57 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Thu, 22 May 2014 07:14:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1776) Create branch for OSGi containers compatible with OSGi 4.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1776: --------------------------------- Description: We need to support OSGi API [4.2|http://www.osgi.org/javadoc/r4v42/]. (was: Class [KarafManagedDeployableContainer|https://github.com/arquillian/arquillian-container-osgi/blob/c577df65c87435d07681ca34550e62310508c755/container/karaf/managed/src/main/java/org/jboss/arquillian/container/osgi/karaf/managed/KarafManagedDeployableContainer.java] uses two methods from JMX API for OSGi [5.0|http://www.osgi.org/javadoc/r5/enterprise/]. {code} BundleStateMBean#getBundle(long bundleIdentifier); ServiceStateMBean#listServices(String clazz, String filter); {code} We need to support OSGi API [4.2|http://www.osgi.org/javadoc/r4v42/] for JMX MBeans. Is it possible to get rid of these methods?) > Create branch for OSGi containers compatible with OSGi 4.2 > ---------------------------------------------------------- > > Key: ARQ-1776 > URL: https://issues.jboss.org/browse/ARQ-1776 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > We need to support OSGi API [4.2|http://www.osgi.org/javadoc/r4v42/]. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 23 09:37:56 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Fri, 23 May 2014 09:37:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1778) Add OSGi container support for bundle autostart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1778: --------------------------------- Summary: Add OSGi container support for bundle autostart (was: Add global container setting for bundle autostart after deployment.) > Add OSGi container support for bundle autostart > ----------------------------------------------- > > Key: ARQ-1778 > URL: https://issues.jboss.org/browse/ARQ-1778 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Bundle is not started automaticly after deployment. It is possible to use annotation {{@StartLevelAware(autostart = true)}} for specific test now. > Add new global container property *autostartBundle*. This will cause autostart of every deployed bundle via container's public method {{deploy(Archive archive)}}. If either annotation of specific bundle or container property will have positive value bundle will be started. One setting with positive value will always override the second one with negative value. > Property type will be {{boolean}} and default value {{false}}. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 23 09:39:56 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Fri, 23 May 2014 09:39:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1778) Add OSGi container support for bundle autostart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1778: --------------------------------- Description: Add OSGi container support for bundle autostart. Container configuration will contain new property *autostartBundle*. This will cause autostart of every deployed bundle. Property type will be {{boolean}} and default value {{false}}. was: Bundle is not started automaticly after deployment. It is possible to use annotation {{@StartLevelAware(autostart = true)}} for specific test now. Add new global container property *autostartBundle*. This will cause autostart of every deployed bundle via container's public method {{deploy(Archive archive)}}. If either annotation of specific bundle or container property will have positive value bundle will be started. One setting with positive value will always override the second one with negative value. Property type will be {{boolean}} and default value {{false}}. > Add OSGi container support for bundle autostart > ----------------------------------------------- > > Key: ARQ-1778 > URL: https://issues.jboss.org/browse/ARQ-1778 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Add OSGi container support for bundle autostart. > Container configuration will contain new property *autostartBundle*. This will cause autostart of every deployed bundle. Property type will be {{boolean}} and default value {{false}}. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 23 09:41:56 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Fri, 23 May 2014 09:41:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1778) Add OSGi container support for bundle autostart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968568#comment-12968568 ] Martin Basovnik edited comment on ARQ-1778 at 5/23/14 9:40 AM: --------------------------------------------------------------- Feature is implemented for karaf managed container. was (Author: mbasovni): I would like to create a unit test for this feature but I do not want to modify {{arquillian.xml}} file. I have created *ResourceProvider* for container configuration class but injection into my test works only in _client_ tests ({{@RunAsClient}}). When I modify the configuration in client test and then execute another _in-container_ test, some classes are missing in deployed bundle (e.g. {{KarafManagedContainerConfiguration}} and others). Why? I do not use this class in this test, only in that client test. How can I inject configuration via {{@ArquillianResource}} (it is already implemented) into in-container test? Or how to make a client test independent of in-container test? > Add OSGi container support for bundle autostart > ----------------------------------------------- > > Key: ARQ-1778 > URL: https://issues.jboss.org/browse/ARQ-1778 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Add OSGi container support for bundle autostart. > Container configuration will contain new property *autostartBundle*. This will cause autostart of every deployed bundle. Property type will be {{boolean}} and default value {{false}}. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 23 10:11:56 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Fri, 23 May 2014 10:11:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1781) Add support for multiple bootstrap complete services In-Reply-To: References: Message-ID: Martin Basovnik created ARQ-1781: ------------------------------------ Summary: Add support for multiple bootstrap complete services Key: ARQ-1781 URL: https://issues.jboss.org/browse/ARQ-1781 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Martin Basovnik Assignee: Thomas Diesler Add support both for master and 4.2 branches. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 23 10:11:57 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Fri, 23 May 2014 10:11:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1781) Add support for multiple bootstrap complete services In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1781: --------------------------------- Description: Add support for both master and 4.2 branches. (was: Add support both for master and 4.2 branches.) > Add support for multiple bootstrap complete services > ---------------------------------------------------- > > Key: ARQ-1781 > URL: https://issues.jboss.org/browse/ARQ-1781 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Add support for both master and 4.2 branches. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sun May 25 09:33:56 2014 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Sun, 25 May 2014 09:33:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1749) auto discover httpPort from Container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Poul reassigned ARQ-1749: --------------------------------- Assignee: Gerhard Poul > auto discover httpPort from Container > ------------------------------------- > > Key: ARQ-1749 > URL: https://issues.jboss.org/browse/ARQ-1749 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Assignee: Gerhard Poul > > The exposed MBean WebSphere/endpoint/channelfw/defaultHttpEndpoint contain Host and Port attributes which could be used if httpPort is not configured in arquillian.xml. > The Container require serverName to detect which VM is running, and as long as you have the VM you have the httpPort info. Defaulting to the 'defaultHttpEndpoint' should remove a few possible error configurations. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sun May 25 09:33:57 2014 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Sun, 25 May 2014 09:33:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1749) Retrieve httpPort from MBean when not provided in configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Poul updated ARQ-1749: ------------------------------ Summary: Retrieve httpPort from MBean when not provided in configuration (was: auto discover httpPort from Container) > Retrieve httpPort from MBean when not provided in configuration > --------------------------------------------------------------- > > Key: ARQ-1749 > URL: https://issues.jboss.org/browse/ARQ-1749 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Assignee: Gerhard Poul > > The exposed MBean WebSphere/endpoint/channelfw/defaultHttpEndpoint contain Host and Port attributes which could be used if httpPort is not configured in arquillian.xml. > The Container require serverName to detect which VM is running, and as long as you have the VM you have the httpPort info. Defaulting to the 'defaultHttpEndpoint' should remove a few possible error configurations. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sun May 25 09:36:05 2014 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Sun, 25 May 2014 09:36:05 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1749) Retrieve httpPort from MBean when not provided in configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Poul updated ARQ-1749: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-was/pull/20 > Retrieve httpPort from MBean when not provided in configuration > --------------------------------------------------------------- > > Key: ARQ-1749 > URL: https://issues.jboss.org/browse/ARQ-1749 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Assignee: Gerhard Poul > > The exposed MBean WebSphere/endpoint/channelfw/defaultHttpEndpoint contain Host and Port attributes which could be used if httpPort is not configured in arquillian.xml. > The Container require serverName to detect which VM is running, and as long as you have the VM you have the httpPort info. Defaulting to the 'defaultHttpEndpoint' should remove a few possible error configurations. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 26 03:27:56 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 May 2014 03:27:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-441) xhrInterception breaks applications using jQuery 2.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970362#comment-12970362 ] Luk?? Fry? commented on ARQGRA-441: ----------------------------------- Hey [~okiss], have you tried to investigate what's going on in the javascript part? > xhrInterception breaks applications using jQuery 2.x > ---------------------------------------------------- > > Key: ARQGRA-441 > URL: https://issues.jboss.org/browse/ARQGRA-441 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final, 2.0.2.Final > Environment: Firefox 29, Chrome 34 > Reporter: Oliver Ki?? > Priority: Critical > Fix For: 2.0.3.Final > > > After {{[kitchensink-backbone|https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.6.x-develop/kitchensink-backbone]}} and {{[contacts-mobile-basic|https://github.com/jboss-developer/jboss-wfk-quickstarts/pull/154]}} quickstarts were updated to use jQuery 2.0.3, Graphene guards no longer work properly in their functional tests. > After {{window.Graphene.xhrInterception.install()}}, the quickstarts do not react to responses to ajax requests they make (server side validation messages are not shown, member list is not displayed, no feedback is shown after a new member is registered). > When {{window.Graphene.xhrInterception.uninstall()}} is run, the quickstarts start behaving normally again. > I tried reproducing the issue with different versions of javascript libraries used in the quickstarts and could reproduce it if jQuery 2.x was used (tested 2.0.3 and 2.1.0). Other libraries do not seem to have an effect on the issue. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 26 03:40:02 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 May 2014 03:40:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1769) org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1769: ---------------------------- Steps to Reproduce: When running a simple test case like the following: {code} import static org.jboss.arquillian.warp.client.filter.http.HttpFilters.request; import static org.junit.Assert.assertEquals; import static org.junit.Assert.assertFalse; import static org.junit.Assert.assertTrue; import java.io.File; import java.io.IOException; import java.net.URL; import javax.faces.context.FacesContext; import javax.servlet.http.HttpServletResponse; import org.apache.log4j.Logger; import org.jboss.arquillian.container.test.api.Deployment; import org.jboss.arquillian.container.test.api.RunAsClient; import org.jboss.arquillian.drone.api.annotation.Drone; import org.jboss.arquillian.junit.Arquillian; import org.jboss.arquillian.test.api.ArquillianResource; import org.jboss.arquillian.warp.Activity; import org.jboss.arquillian.warp.Inspection; import org.jboss.arquillian.warp.Warp; import org.jboss.arquillian.warp.WarpTest; import org.jboss.arquillian.warp.jsf.AfterPhase; import org.jboss.arquillian.warp.jsf.Phase; import org.jboss.arquillian.warp.servlet.AfterServlet; import org.jboss.arquillian.warp.servlet.BeforeServlet; import org.jboss.shrinkwrap.api.Filters; import org.jboss.shrinkwrap.api.GenericArchive; import org.jboss.shrinkwrap.api.ShrinkWrap; import org.jboss.shrinkwrap.api.importer.ExplodedImporter; import org.jboss.shrinkwrap.api.spec.WebArchive; import org.jboss.shrinkwrap.resolver.api.DependencyResolvers; import org.jboss.shrinkwrap.resolver.api.maven.MavenDependencyResolver; import org.junit.Test; import org.junit.runner.RunWith; import org.openqa.selenium.By; import org.openqa.selenium.WebDriver; import org.openqa.selenium.WebElement; import org.springframework.validation.Errors; @WarpTest @RunWith(Arquillian.class) @RunAsClient public class MyTestClass { @Drone WebDriver browser; ... @Deployment public static WebArchive createDeployment() { WebArchive war = ShrinkWrap .create(WebArchive.class, "losingthis.war") .setWebXML(new File("web.xml")) .addPackages(true, new Package[] { Package.getPackage("com.shrinkwrap.me.please") }) .addAsLibraries( DependencyResolvers.use(MavenDependencyResolver.class) .configureFrom("settings.xml") .artifact("com.sun.faces:jsf-api:jar:2.1.17").artifact(com.sun.faces:jsf-impl:jar:2.1.17) .resolveAs(GenericArchive.class)); war.merge(ShrinkWrap.create(GenericArchive.class) .as(ExplodedImporter.class).importDirectory("src/main/webapp") .as(GenericArchive.class), "/", Filters.includeAll()); return war; } @Test public void test() { browser.navigate().to("http://localhost:8080/test/" + INITIAL_PAGE); Warp.initiate(new Activity() { public void perform() { WebElement element = browser.findElement(By.name("f")); element.submit(); }); {code} was: When running a simple test case like the following: import static org.jboss.arquillian.warp.client.filter.http.HttpFilters.request; import static org.junit.Assert.assertEquals; import static org.junit.Assert.assertFalse; import static org.junit.Assert.assertTrue; import java.io.File; import java.io.IOException; import java.net.URL; import javax.faces.context.FacesContext; import javax.servlet.http.HttpServletResponse; import org.apache.log4j.Logger; import org.jboss.arquillian.container.test.api.Deployment; import org.jboss.arquillian.container.test.api.RunAsClient; import org.jboss.arquillian.drone.api.annotation.Drone; import org.jboss.arquillian.junit.Arquillian; import org.jboss.arquillian.test.api.ArquillianResource; import org.jboss.arquillian.warp.Activity; import org.jboss.arquillian.warp.Inspection; import org.jboss.arquillian.warp.Warp; import org.jboss.arquillian.warp.WarpTest; import org.jboss.arquillian.warp.jsf.AfterPhase; import org.jboss.arquillian.warp.jsf.Phase; import org.jboss.arquillian.warp.servlet.AfterServlet; import org.jboss.arquillian.warp.servlet.BeforeServlet; import org.jboss.shrinkwrap.api.Filters; import org.jboss.shrinkwrap.api.GenericArchive; import org.jboss.shrinkwrap.api.ShrinkWrap; import org.jboss.shrinkwrap.api.importer.ExplodedImporter; import org.jboss.shrinkwrap.api.spec.WebArchive; import org.jboss.shrinkwrap.resolver.api.DependencyResolvers; import org.jboss.shrinkwrap.resolver.api.maven.MavenDependencyResolver; import org.junit.Test; import org.junit.runner.RunWith; import org.openqa.selenium.By; import org.openqa.selenium.WebDriver; import org.openqa.selenium.WebElement; import org.springframework.validation.Errors; @WarpTest @RunWith(Arquillian.class) @RunAsClient public class MyTestClass { @Drone WebDriver browser; ... @Deployment public static WebArchive createDeployment() { WebArchive war = ShrinkWrap .create(WebArchive.class, "losingthis.war") .setWebXML(new File("web.xml")) .addPackages(true, new Package[] { Package.getPackage("com.shrinkwrap.me.please") }) .addAsLibraries( DependencyResolvers.use(MavenDependencyResolver.class) .configureFrom("settings.xml") .artifact("com.sun.faces:jsf-api:jar:2.1.17").artifact(com.sun.faces:jsf-impl:jar:2.1.17) .resolveAs(GenericArchive.class)); war.merge(ShrinkWrap.create(GenericArchive.class) .as(ExplodedImporter.class).importDirectory("src/main/webapp") .as(GenericArchive.class), "/", Filters.includeAll()); return war; } @Test public void test() { browser.navigate().to("http://localhost:8080/test/" + INITIAL_PAGE); Warp.initiate(new Activity() { public void perform() { WebElement element = browser.findElement(By.name("f")); element.submit(); }); > org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > -------------------------------------------------------------------------- > > Key: ARQ-1769 > URL: https://issues.jboss.org/browse/ARQ-1769 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, 1.1.3.Final, 1.1.4.Final > Environment: Windows 7 Enterprise SP1 64-bit > Reporter: William Crowell > > I am using the following: > Arquillian Core: 1.1.4.Final (as well as 1.1.3.Final) > Arquillian Drone: 1.2.4.Final (I've tried Drone 2 as well) > Arquillian Warp: 1.0.0.Alpha7 (as well as 1.0.0.Beta1-SNAPSHOT) > Arquillian Transaction: 1.0.1.Final > Arquillian Tomcat 7 Embedded Container using Tomcat 7.0.27: 1.0.0.Final-SNAPSHOT > Spring: 3.2.4.RELEASE > Spring Web: 3.2.2.RELEASE > Spring Security: 3.1.4.RELEASE > Spring WebFlow: 2.4.0.RC1 > PrimeFaces 3.4.2 > JUnit: 4.8.2 > Mojarra 2.1.17 > I am receiving this exception: > java.lang.IllegalStateException: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:69) > ... > 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.LifecycleTestClassExecutor.afterRequest(LifecycleTestClassExecutor.java:78) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.request.RequestContextHandler.handleRequestContext(RequestContextHandler.java:93) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:151) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:120) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:93) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:183) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192) > at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160) > at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) > at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) > at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > ... > Caused by: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl.checkUnbound(LifecycleManagerStoreImpl.java:126) > at org.jboss.arquillian.warp.spi.LifecycleManager.checkUnbound(LifecycleManager.java:158) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:67) > ... 74 more -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 26 03:40:03 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 May 2014 03:40:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1769) org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1769: ---------------------------- Description: I am using the following: Arquillian Core: 1.1.4.Final (as well as 1.1.3.Final) Arquillian Drone: 1.2.4.Final (I've tried Drone 2 as well) Arquillian Warp: 1.0.0.Alpha7 (as well as 1.0.0.Beta1-SNAPSHOT) Arquillian Transaction: 1.0.1.Final Arquillian Tomcat 7 Embedded Container using Tomcat 7.0.27: 1.0.0.Final-SNAPSHOT Spring: 3.2.4.RELEASE Spring Web: 3.2.2.RELEASE Spring Security: 3.1.4.RELEASE Spring WebFlow: 2.4.0.RC1 PrimeFaces 3.4.2 JUnit: 4.8.2 Mojarra 2.1.17 I am receiving this exception: {code} java.lang.IllegalStateException: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:69) ... 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.LifecycleTestClassExecutor.afterRequest(LifecycleTestClassExecutor.java:78) ... 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:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.warp.impl.server.request.RequestContextHandler.handleRequestContext(RequestContextHandler.java:93) ... 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:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:151) at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:120) at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:93) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:183) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192) at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160) at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) ... Caused by: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl.checkUnbound(LifecycleManagerStoreImpl.java:126) at org.jboss.arquillian.warp.spi.LifecycleManager.checkUnbound(LifecycleManager.java:158) at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:67) ... 74 more {code} was: I am using the following: Arquillian Core: 1.1.4.Final (as well as 1.1.3.Final) Arquillian Drone: 1.2.4.Final (I've tried Drone 2 as well) Arquillian Warp: 1.0.0.Alpha7 (as well as 1.0.0.Beta1-SNAPSHOT) Arquillian Transaction: 1.0.1.Final Arquillian Tomcat 7 Embedded Container using Tomcat 7.0.27: 1.0.0.Final-SNAPSHOT Spring: 3.2.4.RELEASE Spring Web: 3.2.2.RELEASE Spring Security: 3.1.4.RELEASE Spring WebFlow: 2.4.0.RC1 PrimeFaces 3.4.2 JUnit: 4.8.2 Mojarra 2.1.17 I am receiving this exception: java.lang.IllegalStateException: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:69) ... 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.LifecycleTestClassExecutor.afterRequest(LifecycleTestClassExecutor.java:78) ... 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:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.warp.impl.server.request.RequestContextHandler.handleRequestContext(RequestContextHandler.java:93) ... 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:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:151) at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:120) at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:93) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:183) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192) at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160) at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) ... Caused by: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl.checkUnbound(LifecycleManagerStoreImpl.java:126) at org.jboss.arquillian.warp.spi.LifecycleManager.checkUnbound(LifecycleManager.java:158) at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:67) ... 74 more > org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > -------------------------------------------------------------------------- > > Key: ARQ-1769 > URL: https://issues.jboss.org/browse/ARQ-1769 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, 1.1.3.Final, 1.1.4.Final > Environment: Windows 7 Enterprise SP1 64-bit > Reporter: William Crowell > > I am using the following: > Arquillian Core: 1.1.4.Final (as well as 1.1.3.Final) > Arquillian Drone: 1.2.4.Final (I've tried Drone 2 as well) > Arquillian Warp: 1.0.0.Alpha7 (as well as 1.0.0.Beta1-SNAPSHOT) > Arquillian Transaction: 1.0.1.Final > Arquillian Tomcat 7 Embedded Container using Tomcat 7.0.27: 1.0.0.Final-SNAPSHOT > Spring: 3.2.4.RELEASE > Spring Web: 3.2.2.RELEASE > Spring Security: 3.1.4.RELEASE > Spring WebFlow: 2.4.0.RC1 > PrimeFaces 3.4.2 > JUnit: 4.8.2 > Mojarra 2.1.17 > I am receiving this exception: > {code} > java.lang.IllegalStateException: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:69) > ... > 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.LifecycleTestClassExecutor.afterRequest(LifecycleTestClassExecutor.java:78) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.request.RequestContextHandler.handleRequestContext(RequestContextHandler.java:93) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:151) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:120) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:93) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:183) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192) > at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160) > at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) > at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) > at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > ... > Caused by: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl.checkUnbound(LifecycleManagerStoreImpl.java:126) > at org.jboss.arquillian.warp.spi.LifecycleManager.checkUnbound(LifecycleManager.java:158) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:67) > ... 74 more > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 26 03:41:57 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 May 2014 03:41:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1769) org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964870#comment-12964870 ] Luk?? Fry? edited comment on ARQ-1769 at 5/26/14 3:40 AM: ---------------------------------------------------------- More information on this. I switched to Arquillian Core 1.1.4, Drone 2.0.0.Alpha1, Warp 1.0.0.Alpha6 and HtmlUnit 2.14 but I am still using Arquillian Test SPI 1.1.3.Final. It appears this issue is not present in Warp 1.0.0.Alpha6, but whenever an anonymous inner class of type org.jboss.arquillian.warp.Inspection is created then Warp never returns and throws a WarpSynchronizationException. Here's the trace: {code} (E) ActivateManager (I) ManagerActivationObserver.activateApplicationContext (E) BeforeRequest (I) RequestContextHandler.createRequestContext (O) LifecycleTestClassExecutor.beforeRequest (O) LifecycleManagerObserver.initializeLifecycleManagerAndInspectionRegistry (E) LifecycleManagerImpl (E) InspectionRegistry (E) ProcessHttpRequest (O) HttpRequestProcessor.processHttpRequest (E) ResponsePayload (E) AfterRequest (I) RequestContextHandler.destroyRequestContext (I) LifecycleTestClassExecutor.afterRequest (E) PassivateManager (I) ManagerActivationObserver.deactivateApplicationContext 2014-05-01 01:18:32,971 ERROR [com.gargoylesoftware.htmlunit.javascript.StrictErrorReporter] - runtimeError: message=[An invalid or illegal selector was specified (selector: '[id='j_idt33:j_idt35_menu'] .ui-menuitem:not(.ui-state-disabled)' error: Invalid selector: *[id="j_idt33:j_idt35_menu"] *.ui-menuitem:not(*.ui-state-disabled)).] sourceName=[http://localhost:8080/test/spring/javax.faces.resource/jquery/jquery.js?ln=primefaces] line=[21] lineSource=[null] lineOffset=[0] (E) AwaitResponse (O) WarpExecutionObserver.awaitResponse (E) WarpSynchronizationException (E) WarpSynchronizationException (E) CleanEnrichment (O) WarpExecutionObserver.cleanEnrichment (E) TestResult {code} was (Author: bcrowell2): More information on this. I switched to Arquillian Core 1.1.4, Drone 2.0.0.Alpha1, Warp 1.0.0.Alpha6 and HtmlUnit 2.14 but I am still using Arquillian Test SPI 1.1.3.Final. It appears this issue is not present in Warp 1.0.0.Alpha6, but whenever an anonymous inner class of type org.jboss.arquillian.warp.Inspection is created then Warp never returns and throws a WarpSynchronizationException. Here's the trace: (E) ActivateManager (I) ManagerActivationObserver.activateApplicationContext (E) BeforeRequest (I) RequestContextHandler.createRequestContext (O) LifecycleTestClassExecutor.beforeRequest (O) LifecycleManagerObserver.initializeLifecycleManagerAndInspectionRegistry (E) LifecycleManagerImpl (E) InspectionRegistry (E) ProcessHttpRequest (O) HttpRequestProcessor.processHttpRequest (E) ResponsePayload (E) AfterRequest (I) RequestContextHandler.destroyRequestContext (I) LifecycleTestClassExecutor.afterRequest (E) PassivateManager (I) ManagerActivationObserver.deactivateApplicationContext 2014-05-01 01:18:32,971 ERROR [com.gargoylesoftware.htmlunit.javascript.StrictErrorReporter] - runtimeError: message=[An invalid or illegal selector was specified (selector: '[id='j_idt33:j_idt35_menu'] .ui-menuitem:not(.ui-state-disabled)' error: Invalid selector: *[id="j_idt33:j_idt35_menu"] *.ui-menuitem:not(*.ui-state-disabled)).] sourceName=[http://localhost:8080/test/spring/javax.faces.resource/jquery/jquery.js?ln=primefaces] line=[21] lineSource=[null] lineOffset=[0] (E) AwaitResponse (O) WarpExecutionObserver.awaitResponse (E) WarpSynchronizationException (E) WarpSynchronizationException (E) CleanEnrichment (O) WarpExecutionObserver.cleanEnrichment (E) TestResult > org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > -------------------------------------------------------------------------- > > Key: ARQ-1769 > URL: https://issues.jboss.org/browse/ARQ-1769 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, 1.1.3.Final, 1.1.4.Final > Environment: Windows 7 Enterprise SP1 64-bit > Reporter: William Crowell > > I am using the following: > Arquillian Core: 1.1.4.Final (as well as 1.1.3.Final) > Arquillian Drone: 1.2.4.Final (I've tried Drone 2 as well) > Arquillian Warp: 1.0.0.Alpha7 (as well as 1.0.0.Beta1-SNAPSHOT) > Arquillian Transaction: 1.0.1.Final > Arquillian Tomcat 7 Embedded Container using Tomcat 7.0.27: 1.0.0.Final-SNAPSHOT > Spring: 3.2.4.RELEASE > Spring Web: 3.2.2.RELEASE > Spring Security: 3.1.4.RELEASE > Spring WebFlow: 2.4.0.RC1 > PrimeFaces 3.4.2 > JUnit: 4.8.2 > Mojarra 2.1.17 > I am receiving this exception: > {code} > java.lang.IllegalStateException: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:69) > ... > 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.LifecycleTestClassExecutor.afterRequest(LifecycleTestClassExecutor.java:78) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.request.RequestContextHandler.handleRequestContext(RequestContextHandler.java:93) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:151) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:120) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:93) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:183) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192) > at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160) > at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) > at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) > at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > ... > Caused by: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl.checkUnbound(LifecycleManagerStoreImpl.java:126) > at org.jboss.arquillian.warp.spi.LifecycleManager.checkUnbound(LifecycleManager.java:158) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:67) > ... 74 more > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 26 03:45:57 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 May 2014 03:45:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1769) org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970367#comment-12970367 ] Luk?? Fry? commented on ARQ-1769: --------------------------------- More insight into why this issue might happen: 1. when you send an Inspection to the server, 2. the server registers the inspection to registry (store) 3. and kicks off regular servlet processing that might trigger inspection code 4. once processed, the server unregisters registered inspections 5. and verifies that there are no more registered inspections left in the registry (store) this is exactly where StoreHasAssociatedObjectsException might happen > org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > -------------------------------------------------------------------------- > > Key: ARQ-1769 > URL: https://issues.jboss.org/browse/ARQ-1769 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, 1.1.3.Final, 1.1.4.Final > Environment: Windows 7 Enterprise SP1 64-bit > Reporter: William Crowell > > I am using the following: > Arquillian Core: 1.1.4.Final (as well as 1.1.3.Final) > Arquillian Drone: 1.2.4.Final (I've tried Drone 2 as well) > Arquillian Warp: 1.0.0.Alpha7 (as well as 1.0.0.Beta1-SNAPSHOT) > Arquillian Transaction: 1.0.1.Final > Arquillian Tomcat 7 Embedded Container using Tomcat 7.0.27: 1.0.0.Final-SNAPSHOT > Spring: 3.2.4.RELEASE > Spring Web: 3.2.2.RELEASE > Spring Security: 3.1.4.RELEASE > Spring WebFlow: 2.4.0.RC1 > PrimeFaces 3.4.2 > JUnit: 4.8.2 > Mojarra 2.1.17 > I am receiving this exception: > {code} > java.lang.IllegalStateException: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:69) > ... > 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.LifecycleTestClassExecutor.afterRequest(LifecycleTestClassExecutor.java:78) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.request.RequestContextHandler.handleRequestContext(RequestContextHandler.java:93) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:151) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:120) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:93) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:183) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192) > at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160) > at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) > at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) > at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > ... > Caused by: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl.checkUnbound(LifecycleManagerStoreImpl.java:126) > at org.jboss.arquillian.warp.spi.LifecycleManager.checkUnbound(LifecycleManager.java:158) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:67) > ... 74 more > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 26 03:45:57 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 May 2014 03:45:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1769) org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970367#comment-12970367 ] Luk?? Fry? edited comment on ARQ-1769 at 5/26/14 3:44 AM: ---------------------------------------------------------- More insight into why this issue might happen: 1. when you send an Inspection to the server, 2. the server registers the inspection to registry (store) 3. and kicks off regular servlet processing that might trigger inspection code 4. once processed, the server unregisters registered inspections 5. and verifies that there are no more registered inspections left in the registry (store) this is exactly where {{StoreHasAssociatedObjectsException}} might happen was (Author: lfryc): More insight into why this issue might happen: 1. when you send an Inspection to the server, 2. the server registers the inspection to registry (store) 3. and kicks off regular servlet processing that might trigger inspection code 4. once processed, the server unregisters registered inspections 5. and verifies that there are no more registered inspections left in the registry (store) this is exactly where StoreHasAssociatedObjectsException might happen > org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > -------------------------------------------------------------------------- > > Key: ARQ-1769 > URL: https://issues.jboss.org/browse/ARQ-1769 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, 1.1.3.Final, 1.1.4.Final > Environment: Windows 7 Enterprise SP1 64-bit > Reporter: William Crowell > > I am using the following: > Arquillian Core: 1.1.4.Final (as well as 1.1.3.Final) > Arquillian Drone: 1.2.4.Final (I've tried Drone 2 as well) > Arquillian Warp: 1.0.0.Alpha7 (as well as 1.0.0.Beta1-SNAPSHOT) > Arquillian Transaction: 1.0.1.Final > Arquillian Tomcat 7 Embedded Container using Tomcat 7.0.27: 1.0.0.Final-SNAPSHOT > Spring: 3.2.4.RELEASE > Spring Web: 3.2.2.RELEASE > Spring Security: 3.1.4.RELEASE > Spring WebFlow: 2.4.0.RC1 > PrimeFaces 3.4.2 > JUnit: 4.8.2 > Mojarra 2.1.17 > I am receiving this exception: > {code} > java.lang.IllegalStateException: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:69) > ... > 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.LifecycleTestClassExecutor.afterRequest(LifecycleTestClassExecutor.java:78) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.request.RequestContextHandler.handleRequestContext(RequestContextHandler.java:93) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:151) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:120) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:93) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:183) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192) > at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160) > at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) > at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) > at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > ... > Caused by: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl.checkUnbound(LifecycleManagerStoreImpl.java:126) > at org.jboss.arquillian.warp.spi.LifecycleManager.checkUnbound(LifecycleManager.java:158) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:67) > ... 74 more > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 26 03:47:57 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 May 2014 03:47:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1769) org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970368#comment-12970368 ] Luk?? Fry? commented on ARQ-1769: --------------------------------- If this really didn't happened in Alpha6, then I would blame Filters-related changes done in ARQ-1489: https://github.com/arquillian/arquillian-extension-warp/commit/f53fd5d79e60dc7c5eba731499dfce1f1a331060 > org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > -------------------------------------------------------------------------- > > Key: ARQ-1769 > URL: https://issues.jboss.org/browse/ARQ-1769 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, 1.1.3.Final, 1.1.4.Final > Environment: Windows 7 Enterprise SP1 64-bit > Reporter: William Crowell > > I am using the following: > Arquillian Core: 1.1.4.Final (as well as 1.1.3.Final) > Arquillian Drone: 1.2.4.Final (I've tried Drone 2 as well) > Arquillian Warp: 1.0.0.Alpha7 (as well as 1.0.0.Beta1-SNAPSHOT) > Arquillian Transaction: 1.0.1.Final > Arquillian Tomcat 7 Embedded Container using Tomcat 7.0.27: 1.0.0.Final-SNAPSHOT > Spring: 3.2.4.RELEASE > Spring Web: 3.2.2.RELEASE > Spring Security: 3.1.4.RELEASE > Spring WebFlow: 2.4.0.RC1 > PrimeFaces 3.4.2 > JUnit: 4.8.2 > Mojarra 2.1.17 > I am receiving this exception: > {code} > java.lang.IllegalStateException: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:69) > ... > 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.LifecycleTestClassExecutor.afterRequest(LifecycleTestClassExecutor.java:78) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.request.RequestContextHandler.handleRequestContext(RequestContextHandler.java:93) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:151) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:120) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:93) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:183) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192) > at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160) > at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) > at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) > at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > ... > Caused by: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl.checkUnbound(LifecycleManagerStoreImpl.java:126) > at org.jboss.arquillian.warp.spi.LifecycleManager.checkUnbound(LifecycleManager.java:158) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:67) > ... 74 more > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 26 03:49:56 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 26 May 2014 03:49:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1769) org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970368#comment-12970368 ] Luk?? Fry? edited comment on ARQ-1769 at 5/26/14 3:48 AM: ---------------------------------------------------------- If this really didn't happened in Alpha6, then I would blame Filters-related changes done in ARQ-1489: https://github.com/arquillian/arquillian-extension-warp/commit/f53fd5d79e60dc7c5eba731499dfce1f1a331060 https://github.com/arquillian/arquillian-extension-warp/blob/master/impl/src/main/java/org/jboss/arquillian/warp/impl/server/lifecycle/LifecycleManagerObserver.java#L69 was (Author: lfryc): If this really didn't happened in Alpha6, then I would blame Filters-related changes done in ARQ-1489: https://github.com/arquillian/arquillian-extension-warp/commit/f53fd5d79e60dc7c5eba731499dfce1f1a331060 > org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > -------------------------------------------------------------------------- > > Key: ARQ-1769 > URL: https://issues.jboss.org/browse/ARQ-1769 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, 1.1.3.Final, 1.1.4.Final > Environment: Windows 7 Enterprise SP1 64-bit > Reporter: William Crowell > > I am using the following: > Arquillian Core: 1.1.4.Final (as well as 1.1.3.Final) > Arquillian Drone: 1.2.4.Final (I've tried Drone 2 as well) > Arquillian Warp: 1.0.0.Alpha7 (as well as 1.0.0.Beta1-SNAPSHOT) > Arquillian Transaction: 1.0.1.Final > Arquillian Tomcat 7 Embedded Container using Tomcat 7.0.27: 1.0.0.Final-SNAPSHOT > Spring: 3.2.4.RELEASE > Spring Web: 3.2.2.RELEASE > Spring Security: 3.1.4.RELEASE > Spring WebFlow: 2.4.0.RC1 > PrimeFaces 3.4.2 > JUnit: 4.8.2 > Mojarra 2.1.17 > I am receiving this exception: > {code} > java.lang.IllegalStateException: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:69) > ... > 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.LifecycleTestClassExecutor.afterRequest(LifecycleTestClassExecutor.java:78) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.request.RequestContextHandler.handleRequestContext(RequestContextHandler.java:93) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:151) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:120) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:93) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:183) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192) > at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160) > at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) > at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) > at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > ... > Caused by: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl.checkUnbound(LifecycleManagerStoreImpl.java:126) > at org.jboss.arquillian.warp.spi.LifecycleManager.checkUnbound(LifecycleManager.java:158) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:67) > ... 74 more > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 26 04:27:56 2014 From: issues at jboss.org (=?UTF-8?Q?Oliver_Ki=C5=A1=C5=A1_=28JIRA=29?=) Date: Mon, 26 May 2014 04:27:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-441) xhrInterception breaks applications using jQuery 2.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970378#comment-12970378 ] Oliver Ki?? commented on ARQGRA-441: ------------------------------------ [~lfryc] I have tried, but I couldn't find anything. I was comparing differences in the return value of {{$.ajaxSettings.xhr()}} between jQuery 1.9.1 and 2.1.0 and before/after {{xhrInterception.install()}}, but I didn't find anything that would help me. Do you have any pointers about what to look for and where? > xhrInterception breaks applications using jQuery 2.x > ---------------------------------------------------- > > Key: ARQGRA-441 > URL: https://issues.jboss.org/browse/ARQGRA-441 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final, 2.0.2.Final > Environment: Firefox 29, Chrome 34 > Reporter: Oliver Ki?? > Priority: Critical > Fix For: 2.0.3.Final > > > After {{[kitchensink-backbone|https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.6.x-develop/kitchensink-backbone]}} and {{[contacts-mobile-basic|https://github.com/jboss-developer/jboss-wfk-quickstarts/pull/154]}} quickstarts were updated to use jQuery 2.0.3, Graphene guards no longer work properly in their functional tests. > After {{window.Graphene.xhrInterception.install()}}, the quickstarts do not react to responses to ajax requests they make (server side validation messages are not shown, member list is not displayed, no feedback is shown after a new member is registered). > When {{window.Graphene.xhrInterception.uninstall()}} is run, the quickstarts start behaving normally again. > I tried reproducing the issue with different versions of javascript libraries used in the quickstarts and could reproduce it if jQuery 2.x was used (tested 2.0.3 and 2.1.0). Other libraries do not seem to have an effect on the issue. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 02:59:57 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 02:59:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-927) Configuration for RemoteWebDriver Drone extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-927. --------------------------- > Configuration for RemoteWebDriver Drone extension > ------------------------------------------------- > > Key: ARQ-927 > URL: https://issues.jboss.org/browse/ARQ-927 > Project: Arquillian > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Luk?? Fry? > Assignee: Jan Papousek > Fix For: drone_1.1.0.CR1 > > > See top-level task for details of reusable session feature. > ---- > The support for RemoteWebDriver should be part of Drone, including configuration, but it has been prototyped in Graphene, to allow introduce the feature quickly. > Right now, configuration is hard-coded to Firefox: > https://github.com/arquillian/arquillian-graphene/blob/feature/quick-turnaround/graphene-webdriver-drone/src/main/java/org/jboss/arquillian/graphene/drone/factory/RemoteWebDriverFactory.java#L78 > Allow to configure the {{RemoteWebDriver}} browser in {{arquillian.xml}}. > ---- > The {{RemoteWebDriver}} configuration differs from other types. > ---- > If necessary, {{RemoteWebDriver}} can be moved to Drone at this point and whole configuration might be addressed there. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:01:57 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:01:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1771) Putting custom annotation on Drone creates multiple instances In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1771. ---------------------------- > Putting custom annotation on Drone creates multiple instances > ------------------------------------------------------------- > > Key: ARQ-1771 > URL: https://issues.jboss.org/browse/ARQ-1771 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha1 > Reporter: Stefan Miklosovic > Fix For: drone_2.0.0.Alpha2 > > > I have a test case like this > {code} > @RunWith(Arquillian.class) > @RunAsClient > public class SomeTestCase > { > @Drone > @Mobile > @Custom > private WebDriver mobile; > // tests > } > {code} > where @Custom is just an annotation: > {code} > @Retention(RetentionPolicy.RUNTIME) > @Target({ ElementType.FIELD, ElementType.PARAMETER }) > public @interface Custom { > } > {code} > it is _not_ annotated with @Qualifier. > Realize that the same problem arise when using @OperateOnDeployment from Arquillian which is not annotated with @Qualifier neither. > I am getting this: > http://pastebin.com/raw.php?i=i9DVqeaC > You see that InstrumentationPerformDecider.decidePerformingInstrumentation observes BeforeDroneInstantiated so when it is treated twice, you are going to instantiate two Drones which is another argument why Drone does it wrong. > When I declare Drone injection like that, it results into two instances of WebDrivers so that means it instruments Android package twice with two Selendroids so that mean I am getting NoUniqueWebDriverException when I want to start some activity because from now on you have "by accident" two webdrivers instrumenting the same deployment as a result of a bug where putting custom annotation on Drone instantiates it twice. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:01:58 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:01:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1746) Remove objects (instance, configuration) from Drone events In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1746. ---------------------------- > Remove objects (instance, configuration) from Drone events > ---------------------------------------------------------- > > Key: ARQ-1746 > URL: https://issues.jboss.org/browse/ARQ-1746 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Tadeas Kriz > Fix For: drone_2.0.0.Alpha2 > > > Remove all objects from Drone Events as they might be already old and the time events are processed. > Always use DroneContext to get their actual value. Event model must enforce that. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:01:58 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:01:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1755) Update Selenium to 2.41.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1755. ---------------------------- > Update Selenium to 2.41.0 > ------------------------- > > Key: ARQ-1755 > URL: https://issues.jboss.org/browse/ARQ-1755 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_2.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:01:59 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:01:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1744) Provide metadata storage in DroneContext In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1744. ---------------------------- > Provide metadata storage in DroneContext > ---------------------------------------- > > Key: ARQ-1744 > URL: https://issues.jboss.org/browse/ARQ-1744 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Tadeas Kriz > Fix For: drone_2.0.0.Alpha2 > > > Other extensions might want to store additional data next to Drone callable/instance and its configuration. > It would be convenient to expose key:String and value:Object storage for storing metadata directly in DroneContext. > It is not needed to solve conflict anyhow. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:01:59 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:01:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1752) Upgrade junit dependency to version 4.11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1752. ---------------------------- > Upgrade junit dependency to version 4.11 > ---------------------------------------- > > Key: ARQ-1752 > URL: https://issues.jboss.org/browse/ARQ-1752 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha1 > Reporter: Tadeas Kriz > Assignee: Tadeas Kriz > Fix For: drone_2.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:01:59 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:01:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1745) Rename InjectionPoint In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1745. ---------------------------- > Rename InjectionPoint > --------------------- > > Key: ARQ-1745 > URL: https://issues.jboss.org/browse/ARQ-1745 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Tadeas Kriz > Fix For: drone_2.0.0.Alpha2 > > > InjectionPoint is already in Arquillian SPI. Rather, follow the conventions and rename it to DronePoint. > There is already InjectionPoint and EventPoint in Drone. Having a DronePoint makes perfect sense using this optics. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:01:59 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:01:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1747) Move InjectionPoint one level up in DroneContext In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1747. ---------------------------- > Move InjectionPoint one level up in DroneContext > ------------------------------------------------ > > Key: ARQ-1747 > URL: https://issues.jboss.org/browse/ARQ-1747 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Tadeas Kriz > Fix For: drone_2.0.0.Alpha2 > > > Instead of having > {code} > context.getDrone(InjectionPoint) > context.getDroneConfiguration(InjectionPoint) > {code} > provide rather > {code} > context.get(InjectionPoint).getInstance() // type defined by IP > context.get(InjectionPoint).getInstanceAs(Class) > context.get(InjectionPoint).getConfigurationAs(Class) > context.get(InjectionPoint).getMetadataAs(String, Class) > {code} > Implementation note: We might provide NullInjectionPoint to avoid people doing null checks. Or, we can throw exception instead. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:02:00 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:02:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1754) Replace deprecated junit.framework.Assert In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1754. ---------------------------- > Replace deprecated junit.framework.Assert > ----------------------------------------- > > Key: ARQ-1754 > URL: https://issues.jboss.org/browse/ARQ-1754 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_2.0.0.Alpha2 > > > Replace deprecated assert calls with org.junit.Assert. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:02:00 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:02:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1647) Allow Executor to set process exit code In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1647: ----------------------------- Fix Version/s: spacelift_1.0.0.Alpha2 > Allow Executor to set process exit code > --------------------------------------- > > Key: ARQ-1647 > URL: https://issues.jboss.org/browse/ARQ-1647 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha1 > Reporter: Karel Piwko > Fix For: spacelift_1.0.0.Alpha2 > > > Currently, it is not possible to setup exit code for external process. This makes handling of execution failure quite complicated. > Figure out what API should be used to let user define allowed exit values. 0 is to be kept as default value. Additionally, there might be multiple values to be set. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:05:56 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:05:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1647) Allow Executor to set process exit code In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970647#comment-12970647 ] Karel Piwko commented on ARQ-1647: ---------------------------------- Fix pushed upstream in https://github.com/arquillian/arquillian-spacelift/commit/be33396485e4b69008d80e9fc2e7b3cee4bf07e1 > Allow Executor to set process exit code > --------------------------------------- > > Key: ARQ-1647 > URL: https://issues.jboss.org/browse/ARQ-1647 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha1 > Reporter: Karel Piwko > Fix For: spacelift_1.0.0.Alpha2 > > > Currently, it is not possible to setup exit code for external process. This makes handling of execution failure quite complicated. > Figure out what API should be used to let user define allowed exit values. 0 is to be kept as default value. Additionally, there might be multiple values to be set. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:05:57 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:05:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1647) Allow Executor to set process exit code In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1647. ------------------------------ Assignee: Karel Piwko Resolution: Done > Allow Executor to set process exit code > --------------------------------------- > > Key: ARQ-1647 > URL: https://issues.jboss.org/browse/ARQ-1647 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: spacelift_1.0.0.Alpha2 > > > Currently, it is not possible to setup exit code for external process. This makes handling of execution failure quite complicated. > Figure out what API should be used to let user define allowed exit values. 0 is to be kept as default value. Additionally, there might be multiple values to be set. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:07:56 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:07:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1743) Merge configuration and callable creation together In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1743: ----------------------------- Fix Version/s: drone_2.0.0.Alpha3 (was: drone_2.0.0.Alpha2) > Merge configuration and callable creation together > -------------------------------------------------- > > Key: ARQ-1743 > URL: https://issues.jboss.org/browse/ARQ-1743 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha1 > Reporter: Karel Piwko > Fix For: drone_2.0.0.Alpha3 > > > There should be just one event and either both or none of the object should be present. > This mean that callable and configuration should be created at the same time. This would make usage of Drone much easier. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:07:56 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:07:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1691) Flexible model for browsers SPI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1691: ----------------------------- Fix Version/s: drone_2.0.0.Alpha3 (was: drone_2.0.0.Alpha2) > Flexible model for browsers SPI > ------------------------------- > > Key: ARQ-1691 > URL: https://issues.jboss.org/browse/ARQ-1691 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Karel Piwko > Fix For: drone_2.0.0.Alpha3 > > > Ensure that adding new browser, either via Drone Extension or via a separate extension is super easy. > For instance, Droidium will need to provide "android" browser. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:09:57 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:09:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1691) Flexible model for browsers SPI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1691: ----------------------------- Fix Version/s: drone_2.0.0.Alpha2 (was: drone_2.0.0.Alpha3) > Flexible model for browsers SPI > ------------------------------- > > Key: ARQ-1691 > URL: https://issues.jboss.org/browse/ARQ-1691 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Karel Piwko > Fix For: drone_2.0.0.Alpha2 > > > Ensure that adding new browser, either via Drone Extension or via a separate extension is super easy. > For instance, Droidium will need to provide "android" browser. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:09:57 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:09:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1691) Flexible model for browsers SPI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970648#comment-12970648 ] Karel Piwko commented on ARQ-1691: ---------------------------------- Marking this issue as resolved, SPI seems flexible enough at this moment. > Flexible model for browsers SPI > ------------------------------- > > Key: ARQ-1691 > URL: https://issues.jboss.org/browse/ARQ-1691 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Karel Piwko > Fix For: drone_2.0.0.Alpha2 > > > Ensure that adding new browser, either via Drone Extension or via a separate extension is super easy. > For instance, Droidium will need to provide "android" browser. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:09:57 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:09:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1691) Flexible model for browsers SPI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1691. ------------------------------ Assignee: Karel Piwko Resolution: Done > Flexible model for browsers SPI > ------------------------------- > > Key: ARQ-1691 > URL: https://issues.jboss.org/browse/ARQ-1691 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_2.0.0.Alpha2 > > > Ensure that adding new browser, either via Drone Extension or via a separate extension is super easy. > For instance, Droidium will need to provide "android" browser. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:09:58 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:09:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1691) Flexible model for browsers SPI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1691. ---------------------------- > Flexible model for browsers SPI > ------------------------------- > > Key: ARQ-1691 > URL: https://issues.jboss.org/browse/ARQ-1691 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_2.0.0.Alpha2 > > > Ensure that adding new browser, either via Drone Extension or via a separate extension is super easy. > For instance, Droidium will need to provide "android" browser. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:21:56 2014 From: issues at jboss.org (Nicklas Karlsson (JIRA)) Date: Tue, 27 May 2014 03:21:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1782) @UsingDataSet/@ShouldMatchDataSet always makes test succeed In-Reply-To: References: Message-ID: Nicklas Karlsson created ARQ-1782: ------------------------------------- Summary: @UsingDataSet/@ShouldMatchDataSet always makes test succeed Key: ARQ-1782 URL: https://issues.jboss.org/browse/ARQ-1782 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha7 Environment: WildFly 8 CR 2 Reporter: Nicklas Karlsson Assignee: Bartosz Majsak {code:xml} 4.0.0 fi.affecto.marela arq-concept 1.0.0-SNAPSHOT jar UTF-8 chrome org.jboss.arquillian arquillian-bom 1.1.4.Final import pom org.jboss.arquillian.extension arquillian-drone-bom 1.3.0.Final pom import org.jboss.arquillian.selenium selenium-bom 2.41.0 pom import junit junit 4.11 test org.jboss.arquillian.junit arquillian-junit-container test org.hibernate hibernate-jpamodelgen 4.3.5.Final provided org.jboss.arquillian.graphene graphene-webdriver 2.0.2.Final pom test org.jboss.arquillian.extension arquillian-persistence-core 1.0.0.Alpha7 org.jboss.arquillian.extension arquillian-persistence-dbunit 1.0.0.Alpha7 arq-wildfly org.jboss.spec jboss-javaee-7.0 1.0.0.Final pom provided org.wildfly wildfly-arquillian-container-remote 8.1.0.CR2 test org.jboss.arquillian.protocol arquillian-protocol-servlet test maven-compiler-plugin 2.3.2 1.7 1.7 src/test/resources true {code:xml} {code:java} package fi.affecto.marela.test; import javax.inject.Inject; import javax.persistence.EntityManager; import javax.persistence.PersistenceContext; import javax.transaction.UserTransaction; import org.jboss.arquillian.container.test.api.Deployment; import org.jboss.arquillian.junit.Arquillian; import org.jboss.arquillian.persistence.ShouldMatchDataSet; import org.jboss.arquillian.persistence.UsingDataSet; import org.jboss.arquillian.transaction.api.annotation.Transactional; import org.jboss.shrinkwrap.api.Archive; import org.jboss.shrinkwrap.api.ShrinkWrap; import org.jboss.shrinkwrap.api.asset.EmptyAsset; import org.jboss.shrinkwrap.api.spec.WebArchive; import org.junit.Assert; import org.junit.Test; import org.junit.runner.RunWith; import fi.affecto.marela.jpa.Game; @RunWith(Arquillian.class) public class PersistenceExtensionTest { @Deployment public static Archive createDeployment() { return ShrinkWrap.create(WebArchive.class, "test.war").addPackage(Game.class.getPackage()) .addAsResource("persistence.xml", "META-INF/persistence.xml") .addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml"); } @PersistenceContext EntityManager em; @Inject UserTransaction utx; @Test public void testA() throws Exception { Assert.assertNotNull(em); utx.begin(); // em.joinTransaction(); Game g = new Game(); g.setId(666L); g.setTitle("x"); Assert.assertFalse(em.contains(g)); g = em.merge(g); Assert.assertTrue(em.contains(g)); utx.rollback(); } @Test @Transactional public void testB() throws Exception { Assert.assertNotNull(em); Game g = new Game(); g.setId(666L); g.setTitle("x"); Assert.assertFalse(em.contains(g)); g = em.merge(g); Assert.assertTrue(em.contains(g)); } @Test // @UsingDataSet("games.yml") // @ShouldMatchDataSet("games-check.yml") @Transactional public void testC() throws Exception { Assert.assertTrue(false); } } {code:java} testC succeeds if the annotations are uncommented. Furthermore, there is something strange with the em/transactions, the persistence works even if the em doesn't join the transaction and the em complains of a detached instance if merge() is switched for persist() -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:23:56 2014 From: issues at jboss.org (Nicklas Karlsson (JIRA)) Date: Tue, 27 May 2014 03:23:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1782) @UsingDataSet/@ShouldMatchDataSet always makes test succeed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicklas Karlsson updated ARQ-1782: ---------------------------------- Description: {code:xml} 4.0.0 fi.affecto.marela arq-concept 1.0.0-SNAPSHOT jar UTF-8 chrome org.jboss.arquillian arquillian-bom 1.1.4.Final import pom org.jboss.arquillian.extension arquillian-drone-bom 1.3.0.Final pom import org.jboss.arquillian.selenium selenium-bom 2.41.0 pom import junit junit 4.11 test org.jboss.arquillian.junit arquillian-junit-container test org.hibernate hibernate-jpamodelgen 4.3.5.Final provided org.jboss.arquillian.graphene graphene-webdriver 2.0.2.Final pom test org.jboss.arquillian.extension arquillian-persistence-core 1.0.0.Alpha7 org.jboss.arquillian.extension arquillian-persistence-dbunit 1.0.0.Alpha7 arq-wildfly org.jboss.spec jboss-javaee-7.0 1.0.0.Final pom provided org.wildfly wildfly-arquillian-container-remote 8.1.0.CR2 test org.jboss.arquillian.protocol arquillian-protocol-servlet test maven-compiler-plugin 2.3.2 1.7 1.7 src/test/resources true {code} {code:java} package fi.affecto.marela.test; import javax.inject.Inject; import javax.persistence.EntityManager; import javax.persistence.PersistenceContext; import javax.transaction.UserTransaction; import org.jboss.arquillian.container.test.api.Deployment; import org.jboss.arquillian.junit.Arquillian; import org.jboss.arquillian.persistence.ShouldMatchDataSet; import org.jboss.arquillian.persistence.UsingDataSet; import org.jboss.arquillian.transaction.api.annotation.Transactional; import org.jboss.shrinkwrap.api.Archive; import org.jboss.shrinkwrap.api.ShrinkWrap; import org.jboss.shrinkwrap.api.asset.EmptyAsset; import org.jboss.shrinkwrap.api.spec.WebArchive; import org.junit.Assert; import org.junit.Test; import org.junit.runner.RunWith; import fi.affecto.marela.jpa.Game; @RunWith(Arquillian.class) public class PersistenceExtensionTest { @Deployment public static Archive createDeployment() { return ShrinkWrap.create(WebArchive.class, "test.war").addPackage(Game.class.getPackage()) .addAsResource("persistence.xml", "META-INF/persistence.xml") .addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml"); } @PersistenceContext EntityManager em; @Inject UserTransaction utx; @Test public void testA() throws Exception { Assert.assertNotNull(em); utx.begin(); // em.joinTransaction(); Game g = new Game(); g.setId(666L); g.setTitle("x"); Assert.assertFalse(em.contains(g)); g = em.merge(g); Assert.assertTrue(em.contains(g)); utx.rollback(); } @Test @Transactional public void testB() throws Exception { Assert.assertNotNull(em); Game g = new Game(); g.setId(666L); g.setTitle("x"); Assert.assertFalse(em.contains(g)); g = em.merge(g); Assert.assertTrue(em.contains(g)); } @Test // @UsingDataSet("games.yml") // @ShouldMatchDataSet("games-check.yml") @Transactional public void testC() throws Exception { Assert.assertTrue(false); } } {code} testC succeeds if the annotations are uncommented. Furthermore, there is something strange with the em/transactions, the persistence works even if the em doesn't join the transaction and the em complains of a detached instance if merge() is switched for persist() was: {code:xml} 4.0.0 fi.affecto.marela arq-concept 1.0.0-SNAPSHOT jar UTF-8 chrome org.jboss.arquillian arquillian-bom 1.1.4.Final import pom org.jboss.arquillian.extension arquillian-drone-bom 1.3.0.Final pom import org.jboss.arquillian.selenium selenium-bom 2.41.0 pom import junit junit 4.11 test org.jboss.arquillian.junit arquillian-junit-container test org.hibernate hibernate-jpamodelgen 4.3.5.Final provided org.jboss.arquillian.graphene graphene-webdriver 2.0.2.Final pom test org.jboss.arquillian.extension arquillian-persistence-core 1.0.0.Alpha7 org.jboss.arquillian.extension arquillian-persistence-dbunit 1.0.0.Alpha7 arq-wildfly org.jboss.spec jboss-javaee-7.0 1.0.0.Final pom provided org.wildfly wildfly-arquillian-container-remote 8.1.0.CR2 test org.jboss.arquillian.protocol arquillian-protocol-servlet test maven-compiler-plugin 2.3.2 1.7 1.7 src/test/resources true {code:xml} {code:java} package fi.affecto.marela.test; import javax.inject.Inject; import javax.persistence.EntityManager; import javax.persistence.PersistenceContext; import javax.transaction.UserTransaction; import org.jboss.arquillian.container.test.api.Deployment; import org.jboss.arquillian.junit.Arquillian; import org.jboss.arquillian.persistence.ShouldMatchDataSet; import org.jboss.arquillian.persistence.UsingDataSet; import org.jboss.arquillian.transaction.api.annotation.Transactional; import org.jboss.shrinkwrap.api.Archive; import org.jboss.shrinkwrap.api.ShrinkWrap; import org.jboss.shrinkwrap.api.asset.EmptyAsset; import org.jboss.shrinkwrap.api.spec.WebArchive; import org.junit.Assert; import org.junit.Test; import org.junit.runner.RunWith; import fi.affecto.marela.jpa.Game; @RunWith(Arquillian.class) public class PersistenceExtensionTest { @Deployment public static Archive createDeployment() { return ShrinkWrap.create(WebArchive.class, "test.war").addPackage(Game.class.getPackage()) .addAsResource("persistence.xml", "META-INF/persistence.xml") .addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml"); } @PersistenceContext EntityManager em; @Inject UserTransaction utx; @Test public void testA() throws Exception { Assert.assertNotNull(em); utx.begin(); // em.joinTransaction(); Game g = new Game(); g.setId(666L); g.setTitle("x"); Assert.assertFalse(em.contains(g)); g = em.merge(g); Assert.assertTrue(em.contains(g)); utx.rollback(); } @Test @Transactional public void testB() throws Exception { Assert.assertNotNull(em); Game g = new Game(); g.setId(666L); g.setTitle("x"); Assert.assertFalse(em.contains(g)); g = em.merge(g); Assert.assertTrue(em.contains(g)); } @Test // @UsingDataSet("games.yml") // @ShouldMatchDataSet("games-check.yml") @Transactional public void testC() throws Exception { Assert.assertTrue(false); } } {code:java} testC succeeds if the annotations are uncommented. Furthermore, there is something strange with the em/transactions, the persistence works even if the em doesn't join the transaction and the em complains of a detached instance if merge() is switched for persist() > @UsingDataSet/@ShouldMatchDataSet always makes test succeed > ----------------------------------------------------------- > > Key: ARQ-1782 > URL: https://issues.jboss.org/browse/ARQ-1782 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Environment: WildFly 8 CR 2 > Reporter: Nicklas Karlsson > Assignee: Bartosz Majsak > > {code:xml} > > xsi:schemaLocation=" > http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/xsd/maven-4.0.0.xsd"> > 4.0.0 > fi.affecto.marela > arq-concept > 1.0.0-SNAPSHOT > jar > > UTF-8 > chrome > > > > > org.jboss.arquillian > arquillian-bom > 1.1.4.Final > import > pom > > > org.jboss.arquillian.extension > arquillian-drone-bom > 1.3.0.Final > pom > import > > > org.jboss.arquillian.selenium > selenium-bom > 2.41.0 > pom > import > > > > > > junit > junit > 4.11 > test > > > org.jboss.arquillian.junit > arquillian-junit-container > test > > > org.hibernate > hibernate-jpamodelgen > 4.3.5.Final > provided > > > org.jboss.arquillian.graphene > graphene-webdriver > 2.0.2.Final > pom > test > > > org.jboss.arquillian.extension > arquillian-persistence-core > 1.0.0.Alpha7 > > > org.jboss.arquillian.extension > arquillian-persistence-dbunit > 1.0.0.Alpha7 > > > > > arq-wildfly > > > org.jboss.spec > jboss-javaee-7.0 > 1.0.0.Final > pom > provided > > > org.wildfly > wildfly-arquillian-container-remote > 8.1.0.CR2 > test > > > org.jboss.arquillian.protocol > arquillian-protocol-servlet > test > > > > > > > > maven-compiler-plugin > 2.3.2 > > 1.7 > 1.7 > > > > > > src/test/resources > true > > > > > {code} > {code:java} > package fi.affecto.marela.test; > import javax.inject.Inject; > import javax.persistence.EntityManager; > import javax.persistence.PersistenceContext; > import javax.transaction.UserTransaction; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.arquillian.persistence.ShouldMatchDataSet; > import org.jboss.arquillian.persistence.UsingDataSet; > import org.jboss.arquillian.transaction.api.annotation.Transactional; > import org.jboss.shrinkwrap.api.Archive; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.WebArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > import fi.affecto.marela.jpa.Game; > @RunWith(Arquillian.class) > public class PersistenceExtensionTest > { > @Deployment > public static Archive createDeployment() > { > return ShrinkWrap.create(WebArchive.class, "test.war").addPackage(Game.class.getPackage()) > .addAsResource("persistence.xml", "META-INF/persistence.xml") > .addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml"); > } > @PersistenceContext > EntityManager em; > @Inject > UserTransaction utx; > @Test > public void testA() throws Exception > { > Assert.assertNotNull(em); > utx.begin(); > // em.joinTransaction(); > Game g = new Game(); > g.setId(666L); > g.setTitle("x"); > Assert.assertFalse(em.contains(g)); > g = em.merge(g); > Assert.assertTrue(em.contains(g)); > utx.rollback(); > } > > @Test > @Transactional > public void testB() throws Exception > { > Assert.assertNotNull(em); > Game g = new Game(); > g.setId(666L); > g.setTitle("x"); > Assert.assertFalse(em.contains(g)); > g = em.merge(g); > Assert.assertTrue(em.contains(g)); > } > @Test > // @UsingDataSet("games.yml") > // @ShouldMatchDataSet("games-check.yml") > @Transactional > public void testC() throws Exception > { > Assert.assertTrue(false); > } > } > {code} > testC succeeds if the annotations are uncommented. > Furthermore, there is something strange with the em/transactions, the persistence works even if the em doesn't join the transaction and the em complains of a detached instance if merge() is switched for persist() -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:29:56 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:29:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1783) Update Arquillian Core to 1.1.4.Final In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1783: -------------------------------- Summary: Update Arquillian Core to 1.1.4.Final Key: ARQ-1783 URL: https://issues.jboss.org/browse/ARQ-1783 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.3.0.Final Reporter: Karel Piwko Update to latest available Core. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:37:56 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:37:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1784) Remove obsolote documentation In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1784: -------------------------------- Summary: Remove obsolote documentation Key: ARQ-1784 URL: https://issues.jboss.org/browse/ARQ-1784 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.3.0.Final Reporter: Karel Piwko Priority: Minor Drone contains references to Graphene 1 and Ajocado, that are no longer valid. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:37:57 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:37:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1783) Update Arquillian Core to 1.1.4.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1783: ----------------------------- Fix Version/s: drone_1.3.1.Final > Update Arquillian Core to 1.1.4.Final > ------------------------------------- > > Key: ARQ-1783 > URL: https://issues.jboss.org/browse/ARQ-1783 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.3.0.Final > Reporter: Karel Piwko > Fix For: drone_1.3.1.Final > > > Update to latest available Core. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:37:57 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:37:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1784) Remove obsolote documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1784: ----------------------------- Fix Version/s: drone_1.3.1.Final > Remove obsolote documentation > ----------------------------- > > Key: ARQ-1784 > URL: https://issues.jboss.org/browse/ARQ-1784 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.3.0.Final > Reporter: Karel Piwko > Priority: Minor > Fix For: drone_1.3.1.Final > > > Drone contains references to Graphene 1 and Ajocado, that are no longer valid. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:37:58 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 03:37:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1785) Update Selenium to 2.42.0 In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1785: -------------------------------- Summary: Update Selenium to 2.42.0 Key: ARQ-1785 URL: https://issues.jboss.org/browse/ARQ-1785 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.3.0.Final Reporter: Karel Piwko Update to recent Selenium -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 04:09:58 2014 From: issues at jboss.org (Stefan Bunciak (JIRA)) Date: Tue, 27 May 2014 04:09:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1786) Implement remote container adapter for Karaf In-Reply-To: References: Message-ID: Stefan Bunciak created ARQ-1786: ----------------------------------- Summary: Implement remote container adapter for Karaf Key: ARQ-1786 URL: https://issues.jboss.org/browse/ARQ-1786 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Stefan Bunciak Assignee: Thomas Diesler -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 04:11:56 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 04:11:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1783) Update Arquillian Core to 1.1.4.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1783. ------------------------------ Assignee: Karel Piwko Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/c0c43798794d6bb28c9287769184cbfae6bcb739 > Update Arquillian Core to 1.1.4.Final > ------------------------------------- > > Key: ARQ-1783 > URL: https://issues.jboss.org/browse/ARQ-1783 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.3.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.3.1.Final > > > Update to latest available Core. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 04:13:58 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 04:13:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1784) Remove obsolote documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1784. ------------------------------ Assignee: Karel Piwko Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/623552c60caee0b8764358c5d22ddd5b79ecbd9f > Remove obsolote documentation > ----------------------------- > > Key: ARQ-1784 > URL: https://issues.jboss.org/browse/ARQ-1784 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.3.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Minor > Fix For: drone_1.3.1.Final > > > Drone contains references to Graphene 1 and Ajocado, that are no longer valid. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 04:13:58 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 27 May 2014 04:13:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1785) Update Selenium to 2.42.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1785. ------------------------------ Assignee: Karel Piwko Fix Version/s: drone_1.3.1.Final Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/069d63a5b0a333b6182be25865b74ca22d9b9ef7 > Update Selenium to 2.42.0 > ------------------------- > > Key: ARQ-1785 > URL: https://issues.jboss.org/browse/ARQ-1785 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.3.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.3.1.Final > > > Update to recent Selenium -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 04:17:56 2014 From: issues at jboss.org (Stefan Bunciak (JIRA)) Date: Tue, 27 May 2014 04:17:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1786) Implement remote container adapter for Karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bunciak updated ARQ-1786: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-osgi/pull/20 > Implement remote container adapter for Karaf > -------------------------------------------- > > Key: ARQ-1786 > URL: https://issues.jboss.org/browse/ARQ-1786 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Stefan Bunciak > Assignee: Thomas Diesler > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 05:49:58 2014 From: issues at jboss.org (Nicklas Karlsson (JIRA)) Date: Tue, 27 May 2014 05:49:58 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1782) @UsingDataSet/@ShouldMatchDataSet always makes test succeed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970714#comment-12970714 ] Nicklas Karlsson commented on ARQ-1782: --------------------------------------- Perhaps related to ARQ-1758, downgrading to arq 1.1.3 made the seeding-file-validation error visible. The em/transaction strangeness still remains, though. > @UsingDataSet/@ShouldMatchDataSet always makes test succeed > ----------------------------------------------------------- > > Key: ARQ-1782 > URL: https://issues.jboss.org/browse/ARQ-1782 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Environment: WildFly 8 CR 2 > Reporter: Nicklas Karlsson > Assignee: Bartosz Majsak > > {code:xml} > > xsi:schemaLocation=" > http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/xsd/maven-4.0.0.xsd"> > 4.0.0 > fi.affecto.marela > arq-concept > 1.0.0-SNAPSHOT > jar > > UTF-8 > chrome > > > > > org.jboss.arquillian > arquillian-bom > 1.1.4.Final > import > pom > > > org.jboss.arquillian.extension > arquillian-drone-bom > 1.3.0.Final > pom > import > > > org.jboss.arquillian.selenium > selenium-bom > 2.41.0 > pom > import > > > > > > junit > junit > 4.11 > test > > > org.jboss.arquillian.junit > arquillian-junit-container > test > > > org.hibernate > hibernate-jpamodelgen > 4.3.5.Final > provided > > > org.jboss.arquillian.graphene > graphene-webdriver > 2.0.2.Final > pom > test > > > org.jboss.arquillian.extension > arquillian-persistence-core > 1.0.0.Alpha7 > > > org.jboss.arquillian.extension > arquillian-persistence-dbunit > 1.0.0.Alpha7 > > > > > arq-wildfly > > > org.jboss.spec > jboss-javaee-7.0 > 1.0.0.Final > pom > provided > > > org.wildfly > wildfly-arquillian-container-remote > 8.1.0.CR2 > test > > > org.jboss.arquillian.protocol > arquillian-protocol-servlet > test > > > > > > > > maven-compiler-plugin > 2.3.2 > > 1.7 > 1.7 > > > > > > src/test/resources > true > > > > > {code} > {code:java} > package fi.affecto.marela.test; > import javax.inject.Inject; > import javax.persistence.EntityManager; > import javax.persistence.PersistenceContext; > import javax.transaction.UserTransaction; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.arquillian.persistence.ShouldMatchDataSet; > import org.jboss.arquillian.persistence.UsingDataSet; > import org.jboss.arquillian.transaction.api.annotation.Transactional; > import org.jboss.shrinkwrap.api.Archive; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.WebArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > import fi.affecto.marela.jpa.Game; > @RunWith(Arquillian.class) > public class PersistenceExtensionTest > { > @Deployment > public static Archive createDeployment() > { > return ShrinkWrap.create(WebArchive.class, "test.war").addPackage(Game.class.getPackage()) > .addAsResource("persistence.xml", "META-INF/persistence.xml") > .addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml"); > } > @PersistenceContext > EntityManager em; > @Inject > UserTransaction utx; > @Test > public void testA() throws Exception > { > Assert.assertNotNull(em); > utx.begin(); > // em.joinTransaction(); > Game g = new Game(); > g.setId(666L); > g.setTitle("x"); > Assert.assertFalse(em.contains(g)); > g = em.merge(g); > Assert.assertTrue(em.contains(g)); > utx.rollback(); > } > > @Test > @Transactional > public void testB() throws Exception > { > Assert.assertNotNull(em); > Game g = new Game(); > g.setId(666L); > g.setTitle("x"); > Assert.assertFalse(em.contains(g)); > g = em.merge(g); > Assert.assertTrue(em.contains(g)); > } > @Test > // @UsingDataSet("games.yml") > // @ShouldMatchDataSet("games-check.yml") > @Transactional > public void testC() throws Exception > { > Assert.assertTrue(false); > } > } > {code} > testC succeeds if the annotations are uncommented. > Furthermore, there is something strange with the em/transactions, the persistence works even if the em doesn't join the transaction and the em complains of a detached instance if merge() is switched for persist() -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 07:19:57 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Tue, 27 May 2014 07:19:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1778) Add OSGi container support for bundle autostart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1778: --------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/arquillian/arquillian-container-osgi/pull/16, https://github.com/arquillian/arquillian-container-osgi/pull/21 (was: https://github.com/arquillian/arquillian-container-osgi/pull/16) > Add OSGi container support for bundle autostart > ----------------------------------------------- > > Key: ARQ-1778 > URL: https://issues.jboss.org/browse/ARQ-1778 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Add OSGi container support for bundle autostart. > Container configuration will contain new property *autostartBundle*. This will cause autostart of every deployed bundle. Property type will be {{boolean}} and default value {{false}}. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 07:49:56 2014 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Tue, 27 May 2014 07:49:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1786) Implement remote container adapter for Karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler updated ARQ-1786: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Done in 2.2.0.CR1 > Implement remote container adapter for Karaf > -------------------------------------------- > > Key: ARQ-1786 > URL: https://issues.jboss.org/browse/ARQ-1786 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Stefan Bunciak > Assignee: Thomas Diesler > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 08:17:56 2014 From: issues at jboss.org (William Crowell (JIRA)) Date: Tue, 27 May 2014 08:17:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1769) org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970782#comment-12970782 ] William Crowell commented on ARQ-1769: -------------------------------------- Lukas, Any workarounds for this? You guys have done outstanding work on this. I really want to try to get this to work. I had to switch back to JSFUnit for the time being. Thank you, William Crowell > org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > -------------------------------------------------------------------------- > > Key: ARQ-1769 > URL: https://issues.jboss.org/browse/ARQ-1769 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, 1.1.3.Final, 1.1.4.Final > Environment: Windows 7 Enterprise SP1 64-bit > Reporter: William Crowell > > I am using the following: > Arquillian Core: 1.1.4.Final (as well as 1.1.3.Final) > Arquillian Drone: 1.2.4.Final (I've tried Drone 2 as well) > Arquillian Warp: 1.0.0.Alpha7 (as well as 1.0.0.Beta1-SNAPSHOT) > Arquillian Transaction: 1.0.1.Final > Arquillian Tomcat 7 Embedded Container using Tomcat 7.0.27: 1.0.0.Final-SNAPSHOT > Spring: 3.2.4.RELEASE > Spring Web: 3.2.2.RELEASE > Spring Security: 3.1.4.RELEASE > Spring WebFlow: 2.4.0.RC1 > PrimeFaces 3.4.2 > JUnit: 4.8.2 > Mojarra 2.1.17 > I am receiving this exception: > {code} > java.lang.IllegalStateException: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:69) > ... > 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.LifecycleTestClassExecutor.afterRequest(LifecycleTestClassExecutor.java:78) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.request.RequestContextHandler.handleRequestContext(RequestContextHandler.java:93) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:151) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:120) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:93) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:183) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192) > at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160) > at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) > at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) > at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > ... > Caused by: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl.checkUnbound(LifecycleManagerStoreImpl.java:126) > at org.jboss.arquillian.warp.spi.LifecycleManager.checkUnbound(LifecycleManager.java:158) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:67) > ... 74 more > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 08:29:59 2014 From: issues at jboss.org (Sona Jamborova (JIRA)) Date: Tue, 27 May 2014 08:29:59 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-442) Graphene is not compatible with selenium 2.42.0 In-Reply-To: References: Message-ID: Sona Jamborova created ARQGRA-442: ------------------------------------- Summary: Graphene is not compatible with selenium 2.42.0 Key: ARQGRA-442 URL: https://issues.jboss.org/browse/ARQGRA-442 Project: Arquillian Graphene Issue Type: Feature Request Affects Versions: 2.0.2.Final Reporter: Sona Jamborova The update of version of selenium-bom to 2.42.0 cause problems in my test suite which uses Arquillian Graphene. It seems that Graphene expected class org.openqa.selenium.html5.BrowserConnection which was deleted by this commit http://code.google.com/p/selenium/source/detail?r=8629dc6ec6ddd96bbe0975ee86d0c4c2f4b9ebb2 Exception is here: http://pastebin.test.redhat.com/211410 Selenium 2.42.0 contains some fixes which blocks our test suite: - Fixing interactions API in Firefox to be able to move mouse to elements in frames using native events. Fixes issue 7253 - Click after move with offset should use last mouse position - Fixing IE driver crash when clicking on link that opens a new window. - etc. I will appreciate a quick fix (minor release). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 02:31:56 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 02:31:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1769) org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971052#comment-12971052 ] Luk?? Fry? commented on ARQ-1769: --------------------------------- Willian, I have noticed the code you have provided do not have any Inspection specified: you have: {code} Warp.initiatiate(Activity) {code} but you should have: {code} Warp.initiative(Activity).inspect(Inspection) {code} Could you please specify the actual Inspection code? I'm sure you had to have some inspection specified, since Warp won't execute activity unless you specified some inspection. ;-) ---- You are also using HtmlUnit as a client-side code runner. I would really like to discourage that, since you will often find it doesn't work as expected. You can configure Drone for browser=phantomjs. PhantomJS simulates Chrome browser behavior very closely (in fact they share the WebKit/Blink core). > org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > -------------------------------------------------------------------------- > > Key: ARQ-1769 > URL: https://issues.jboss.org/browse/ARQ-1769 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, 1.1.3.Final, 1.1.4.Final > Environment: Windows 7 Enterprise SP1 64-bit > Reporter: William Crowell > > I am using the following: > Arquillian Core: 1.1.4.Final (as well as 1.1.3.Final) > Arquillian Drone: 1.2.4.Final (I've tried Drone 2 as well) > Arquillian Warp: 1.0.0.Alpha7 (as well as 1.0.0.Beta1-SNAPSHOT) > Arquillian Transaction: 1.0.1.Final > Arquillian Tomcat 7 Embedded Container using Tomcat 7.0.27: 1.0.0.Final-SNAPSHOT > Spring: 3.2.4.RELEASE > Spring Web: 3.2.2.RELEASE > Spring Security: 3.1.4.RELEASE > Spring WebFlow: 2.4.0.RC1 > PrimeFaces 3.4.2 > JUnit: 4.8.2 > Mojarra 2.1.17 > I am receiving this exception: > {code} > java.lang.IllegalStateException: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:69) > ... > 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.LifecycleTestClassExecutor.afterRequest(LifecycleTestClassExecutor.java:78) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.request.RequestContextHandler.handleRequestContext(RequestContextHandler.java:93) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:151) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:120) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:93) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:183) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192) > at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160) > at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) > at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) > at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > ... > Caused by: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl.checkUnbound(LifecycleManagerStoreImpl.java:126) > at org.jboss.arquillian.warp.spi.LifecycleManager.checkUnbound(LifecycleManager.java:158) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:67) > ... 74 more > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 02:33:57 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 02:33:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-442) Graphene is not compatible with selenium 2.42.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-442: ------------------------------ Fix Version/s: 2.0.3.Final > Graphene is not compatible with selenium 2.42.0 > ----------------------------------------------- > > Key: ARQGRA-442 > URL: https://issues.jboss.org/browse/ARQGRA-442 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.2.Final > Reporter: Sona Jamborova > Fix For: 2.0.3.Final > > > The update of version of selenium-bom to 2.42.0 cause problems in my test suite which uses Arquillian Graphene. It seems that Graphene expected class org.openqa.selenium.html5.BrowserConnection which was deleted by this commit http://code.google.com/p/selenium/source/detail?r=8629dc6ec6ddd96bbe0975ee86d0c4c2f4b9ebb2 > Exception is here: http://pastebin.test.redhat.com/211410 > Selenium 2.42.0 contains some fixes which blocks our test suite: > - Fixing interactions API in Firefox to be able to move mouse to elements in frames using native events. Fixes issue 7253 > - Click after move with offset should use last mouse position > - Fixing IE driver crash when clicking on link that opens a new window. > - etc. > I will appreciate a quick fix (minor release). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 02:35:57 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 02:35:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-442) Graphene is not compatible with selenium 2.42.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971053#comment-12971053 ] Luk?? Fry? commented on ARQGRA-442: ----------------------------------- We need to refactor SeleniumResourceProvider [1] in a way which will be future-proof, i.e. we won't compile this class against Selenium API, we should rather leverage a list of class names and iterate over them. If class won't be find, it will be simply skipped. > Graphene is not compatible with selenium 2.42.0 > ----------------------------------------------- > > Key: ARQGRA-442 > URL: https://issues.jboss.org/browse/ARQGRA-442 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.2.Final > Reporter: Sona Jamborova > Fix For: 2.0.3.Final > > > The update of version of selenium-bom to 2.42.0 cause problems in my test suite which uses Arquillian Graphene. It seems that Graphene expected class org.openqa.selenium.html5.BrowserConnection which was deleted by this commit http://code.google.com/p/selenium/source/detail?r=8629dc6ec6ddd96bbe0975ee86d0c4c2f4b9ebb2 > Exception is here: http://pastebin.test.redhat.com/211410 > Selenium 2.42.0 contains some fixes which blocks our test suite: > - Fixing interactions API in Firefox to be able to move mouse to elements in frames using native events. Fixes issue 7253 > - Click after move with offset should use last mouse position > - Fixing IE driver crash when clicking on link that opens a new window. > - etc. > I will appreciate a quick fix (minor release). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 02:37:56 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 02:37:56 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-442) Graphene is not compatible with selenium 2.42.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971054#comment-12971054 ] Luk?? Fry? commented on ARQGRA-442: ----------------------------------- Sona, any chance your team could look at it? > Graphene is not compatible with selenium 2.42.0 > ----------------------------------------------- > > Key: ARQGRA-442 > URL: https://issues.jboss.org/browse/ARQGRA-442 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.2.Final > Reporter: Sona Jamborova > Fix For: 2.0.3.Final > > > The update of version of selenium-bom to 2.42.0 cause problems in my test suite which uses Arquillian Graphene. It seems that Graphene expected class org.openqa.selenium.html5.BrowserConnection which was deleted by this commit http://code.google.com/p/selenium/source/detail?r=8629dc6ec6ddd96bbe0975ee86d0c4c2f4b9ebb2 > Exception is here: http://pastebin.test.redhat.com/211410 > Selenium 2.42.0 contains some fixes which blocks our test suite: > - Fixing interactions API in Firefox to be able to move mouse to elements in frames using native events. Fixes issue 7253 > - Click after move with offset should use last mouse position > - Fixing IE driver crash when clicking on link that opens a new window. > - etc. > I will appreciate a quick fix (minor release). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 02:37:57 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 02:37:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-442) Graphene is not compatible with selenium 2.42.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971053#comment-12971053 ] Luk?? Fry? edited comment on ARQGRA-442 at 5/28/14 2:36 AM: ------------------------------------------------------------ We need to refactor SeleniumResourceProvider [1] in a way which will be future-proof, i.e. we won't compile this class against Selenium API, we should rather leverage a list of class names and iterate over them. If class won't be find, it will be simply skipped. [1] https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/enricher/SeleniumResourceProvider.java was (Author: lfryc): We need to refactor SeleniumResourceProvider [1] in a way which will be future-proof, i.e. we won't compile this class against Selenium API, we should rather leverage a list of class names and iterate over them. If class won't be find, it will be simply skipped. > Graphene is not compatible with selenium 2.42.0 > ----------------------------------------------- > > Key: ARQGRA-442 > URL: https://issues.jboss.org/browse/ARQGRA-442 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.2.Final > Reporter: Sona Jamborova > Fix For: 2.0.3.Final > > > The update of version of selenium-bom to 2.42.0 cause problems in my test suite which uses Arquillian Graphene. It seems that Graphene expected class org.openqa.selenium.html5.BrowserConnection which was deleted by this commit http://code.google.com/p/selenium/source/detail?r=8629dc6ec6ddd96bbe0975ee86d0c4c2f4b9ebb2 > Exception is here: http://pastebin.test.redhat.com/211410 > Selenium 2.42.0 contains some fixes which blocks our test suite: > - Fixing interactions API in Firefox to be able to move mouse to elements in frames using native events. Fixes issue 7253 > - Click after move with offset should use last mouse position > - Fixing IE driver crash when clicking on link that opens a new window. > - etc. > I will appreciate a quick fix (minor release). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 04:01:57 2014 From: issues at jboss.org (Stefan Bunciak (JIRA)) Date: Wed, 28 May 2014 04:01:57 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1787) Move tests to separate maven module In-Reply-To: References: Message-ID: Stefan Bunciak created ARQ-1787: ----------------------------------- Summary: Move tests to separate maven module Key: ARQ-1787 URL: https://issues.jboss.org/browse/ARQ-1787 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Stefan Bunciak Assignee: Thomas Diesler Move tests to separate maven module, so that all container adapter share the same set of tests. Container-specific tests can still reside with the container adapter implementation -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 08:01:19 2014 From: issues at jboss.org (William Crowell (JIRA)) Date: Wed, 28 May 2014 08:01:19 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1769) org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971195#comment-12971195 ] William Crowell commented on ARQ-1769: -------------------------------------- Lukas, For some reason when I posted the code I left out the inspection. My apologies. Here it is: > org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > -------------------------------------------------------------------------- > > Key: ARQ-1769 > URL: https://issues.jboss.org/browse/ARQ-1769 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, 1.1.3.Final, 1.1.4.Final > Environment: Windows 7 Enterprise SP1 64-bit > Reporter: William Crowell > > I am using the following: > Arquillian Core: 1.1.4.Final (as well as 1.1.3.Final) > Arquillian Drone: 1.2.4.Final (I've tried Drone 2 as well) > Arquillian Warp: 1.0.0.Alpha7 (as well as 1.0.0.Beta1-SNAPSHOT) > Arquillian Transaction: 1.0.1.Final > Arquillian Tomcat 7 Embedded Container using Tomcat 7.0.27: 1.0.0.Final-SNAPSHOT > Spring: 3.2.4.RELEASE > Spring Web: 3.2.2.RELEASE > Spring Security: 3.1.4.RELEASE > Spring WebFlow: 2.4.0.RC1 > PrimeFaces 3.4.2 > JUnit: 4.8.2 > Mojarra 2.1.17 > I am receiving this exception: > {code} > java.lang.IllegalStateException: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:69) > ... > 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.LifecycleTestClassExecutor.afterRequest(LifecycleTestClassExecutor.java:78) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.request.RequestContextHandler.handleRequestContext(RequestContextHandler.java:93) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:151) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:120) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:93) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:183) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192) > at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160) > at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) > at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) > at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > ... > Caused by: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl.checkUnbound(LifecycleManagerStoreImpl.java:126) > at org.jboss.arquillian.warp.spi.LifecycleManager.checkUnbound(LifecycleManager.java:158) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:67) > ... 74 more > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 08:01:19 2014 From: issues at jboss.org (William Crowell (JIRA)) Date: Wed, 28 May 2014 08:01:19 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1769) org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971195#comment-12971195 ] William Crowell edited comment on ARQ-1769 at 5/28/14 8:00 AM: --------------------------------------------------------------- Lukas, For some reason when I posted the code I left out the inspection. My apologies. Here it is: browser.navigate().to("http://localhost:8080/test/" + INITIAL_PAGE); Warp.initiate(new Activity() { public void perform() { WebElement element = browser.findElement(By.name("f")); element.submit(); } }).group().observe(request()).inspect(new Inspection() { private static final long serialVersionUID = -5222424427892601639L; @ArquillianResource private HttpServletResponse response; @AfterPhase(Phase.RESTORE_VIEW) public void verify_that_the_appropriate_page_is_requested(@ArquillianResource FacesContext facesContext) { Assert.assertEquals(INITIAL_PAGE, facesContext.getViewRoot().getViewId()); } @AfterServlet public void verify_that_response_is_redirected() { Assert.assertTrue(response.getHeader("Location").contains(AFTER_LOGIN_PAGE)); } }) .execute(); was (Author: bcrowell2): Lukas, For some reason when I posted the code I left out the inspection. My apologies. Here it is: > org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > -------------------------------------------------------------------------- > > Key: ARQ-1769 > URL: https://issues.jboss.org/browse/ARQ-1769 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, 1.1.3.Final, 1.1.4.Final > Environment: Windows 7 Enterprise SP1 64-bit > Reporter: William Crowell > > I am using the following: > Arquillian Core: 1.1.4.Final (as well as 1.1.3.Final) > Arquillian Drone: 1.2.4.Final (I've tried Drone 2 as well) > Arquillian Warp: 1.0.0.Alpha7 (as well as 1.0.0.Beta1-SNAPSHOT) > Arquillian Transaction: 1.0.1.Final > Arquillian Tomcat 7 Embedded Container using Tomcat 7.0.27: 1.0.0.Final-SNAPSHOT > Spring: 3.2.4.RELEASE > Spring Web: 3.2.2.RELEASE > Spring Security: 3.1.4.RELEASE > Spring WebFlow: 2.4.0.RC1 > PrimeFaces 3.4.2 > JUnit: 4.8.2 > Mojarra 2.1.17 > I am receiving this exception: > {code} > java.lang.IllegalStateException: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:69) > ... > 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.LifecycleTestClassExecutor.afterRequest(LifecycleTestClassExecutor.java:78) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.request.RequestContextHandler.handleRequestContext(RequestContextHandler.java:93) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:151) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:120) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:93) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:183) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192) > at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160) > at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) > at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) > at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > ... > Caused by: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl.checkUnbound(LifecycleManagerStoreImpl.java:126) > at org.jboss.arquillian.warp.spi.LifecycleManager.checkUnbound(LifecycleManager.java:158) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:67) > ... 74 more > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 10:37:16 2014 From: issues at jboss.org (Sona Jamborova (JIRA)) Date: Wed, 28 May 2014 10:37:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-442) Graphene is not compatible with selenium 2.42.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sona Jamborova updated ARQGRA-442: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/105 There is a pull reguest. It was tested with drone 1.3.0 and 1.3.1. Arquillian Graphene was compiled without any problems on both versions. Arquillian Graphene was tested by ftest on drone 1.3.1. > Graphene is not compatible with selenium 2.42.0 > ----------------------------------------------- > > Key: ARQGRA-442 > URL: https://issues.jboss.org/browse/ARQGRA-442 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.2.Final > Reporter: Sona Jamborova > Fix For: 2.0.3.Final > > > The update of version of selenium-bom to 2.42.0 cause problems in my test suite which uses Arquillian Graphene. It seems that Graphene expected class org.openqa.selenium.html5.BrowserConnection which was deleted by this commit http://code.google.com/p/selenium/source/detail?r=8629dc6ec6ddd96bbe0975ee86d0c4c2f4b9ebb2 > Exception is here: http://pastebin.test.redhat.com/211410 > Selenium 2.42.0 contains some fixes which blocks our test suite: > - Fixing interactions API in Firefox to be able to move mouse to elements in frames using native events. Fixes issue 7253 > - Click after move with offset should use last mouse position > - Fixing IE driver crash when clicking on link that opens a new window. > - etc. > I will appreciate a quick fix (minor release). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 10:53:16 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Wed, 28 May 2014 10:53:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1788) containers - code refactoring In-Reply-To: References: Message-ID: Martin Basovnik created ARQ-1788: ------------------------------------ Summary: containers - code refactoring Key: ARQ-1788 URL: https://issues.jboss.org/browse/ARQ-1788 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Martin Basovnik Assignee: Thomas Diesler *Code refactoring* - Create an ancestor for managed/remote containers using JMX - Rename class OSGiContainerConfiguration to EmbeddedContainerConfiguration - bootstrapCompleteServices - ... -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 11:15:18 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 11:15:18 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-443) Upgrade to Core 1.1.4, Drone 1.3.1 In-Reply-To: References: Message-ID: Luk?? Fry? created ARQGRA-443: --------------------------------- Summary: Upgrade to Core 1.1.4, Drone 1.3.1 Key: ARQGRA-443 URL: https://issues.jboss.org/browse/ARQGRA-443 Project: Arquillian Graphene Issue Type: Component Upgrade Reporter: Luk?? Fry? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 11:29:16 2014 From: issues at jboss.org (Cesar Ricardez (JIRA)) Date: Wed, 28 May 2014 11:29:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1770) Root.war deployed to Wildfly gives wrong @ArquillianResource URL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969214#comment-12969214 ] Cesar Ricardez edited comment on ARQ-1770 at 5/28/14 11:28 AM: --------------------------------------------------------------- Also, this bug is affecting when using managed: Caused by: java.lang.IllegalStateException: Error launching request at http://127.0.0.1:8080/ROOT/ArquillianServletRunner?outputMode=serializedObject&className=se.shouldfailtest.ShouldFailTest&methodName=shouldFail. No result returned at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.executeWithRetry(ServletMethodExecutor.java:139) at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.invoke(ServletMethodExecutor.java:99) at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) 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:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) 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.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) was (Author: xiumeteo): Also, this bus is affecting when using managed: Caused by: java.lang.IllegalStateException: Error launching request at http://127.0.0.1:8080/ROOT/ArquillianServletRunner?outputMode=serializedObject&className=se.shouldfailtest.ShouldFailTest&methodName=shouldFail. No result returned at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.executeWithRetry(ServletMethodExecutor.java:139) at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.invoke(ServletMethodExecutor.java:99) at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) 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:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) 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.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > Root.war deployed to Wildfly gives wrong @ArquillianResource URL > ---------------------------------------------------------------- > > Key: ARQ-1770 > URL: https://issues.jboss.org/browse/ARQ-1770 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Matej Briskar > Attachments: arquillian_test_should_fail.zip > > > This bug is a small one and had easy workaround, but it happens. > When I deploy a ROOT.war to the Wildfly embedded container, the returned @ArquillianResource Url url gives localhost:8080/ROOT instead of the correct localhost:8080/. Tested with wildfly 8.1.0.CR1 dependency version. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 11:33:16 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 11:33:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-444) Functional tests fail to run due to surefire plugin failure In-Reply-To: References: Message-ID: Luk?? Fry? created ARQGRA-444: --------------------------------- Summary: Functional tests fail to run due to surefire plugin failure Key: ARQGRA-444 URL: https://issues.jboss.org/browse/ARQGRA-444 Project: Arquillian Graphene Issue Type: Bug Environment: {code} $ mvn -v Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Maven home: /home/lfryc/Apps/apache-maven-3.0.4 Java version: 1.7.0_51, vendor: Oracle Corporation Java home: /usr/java/jdk1.7.0_51/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.14.4-200.fc20.x86_64", arch: "amd64", family: "unix" {code} Reporter: Luk?? Fry? {code} [INFO] --- maven-surefire-plugin:2.9:test (default-test) @ graphene-webdriver-ftest --- [INFO] Surefire report directory: /mnt/workspace/workspaces/arquillian/arquillian-graphene/ftest/target/surefire-reports [INFO] Using configured provider org.apache.maven.surefire.junitcore.JUnitCoreProvider ------------------------------------------------------- T E S T S ------------------------------------------------------- Concurrency config is parallel='none', perCoreThreadCount=true, threadCount=2, useUnlimitedThreads=false Running org.jboss.arquillian.graphene.ftest.intercept.TestInterceptorRegistration Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec Running org.jboss.arquillian.graphene.ftest.element.TestGrapheneElementAsPageFragmentRoot Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec Running org.jboss.arquillian.graphene.ftest.enricher.hierarchy.SomeAbstractTest Exception in thread "ThreadedStreamConsumer" java.lang.NoSuchMethodError: org.apache.maven.surefire.report.StackTraceWriter.getThrowable()Ljava/lang/Throwable; at org.apache.maven.surefire.report.XMLReporter.writeTestProblems(XMLReporter.java:238) at org.apache.maven.surefire.report.XMLReporter.testError(XMLReporter.java:208) at org.apache.maven.surefire.report.MulticastingReporter.testError(MulticastingReporter.java:73) at org.apache.maven.surefire.report.TestSetRunListener.testError(TestSetRunListener.java:139) at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:112) at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:67) at java.lang.Thread.run(Thread.java:744) Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 11:33:16 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 11:33:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-444) Functional tests fail to run due to surefire plugin failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-444: ------------------------------ Environment: $ mvn -v Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Maven home: /home/lfryc/Apps/apache-maven-3.0.4 Java version: 1.7.0_51, vendor: Oracle Corporation Java home: /usr/java/jdk1.7.0_51/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.14.4-200.fc20.x86_64", arch: "amd64", family: "unix" was: {code} $ mvn -v Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Maven home: /home/lfryc/Apps/apache-maven-3.0.4 Java version: 1.7.0_51, vendor: Oracle Corporation Java home: /usr/java/jdk1.7.0_51/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.14.4-200.fc20.x86_64", arch: "amd64", family: "unix" {code} > Functional tests fail to run due to surefire plugin failure > ----------------------------------------------------------- > > Key: ARQGRA-444 > URL: https://issues.jboss.org/browse/ARQGRA-444 > Project: Arquillian Graphene > Issue Type: Bug > Environment: $ mvn -v > Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) > Maven home: /home/lfryc/Apps/apache-maven-3.0.4 > Java version: 1.7.0_51, vendor: Oracle Corporation > Java home: /usr/java/jdk1.7.0_51/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "3.14.4-200.fc20.x86_64", arch: "amd64", family: "unix" > Reporter: Luk?? Fry? > > {code} > [INFO] --- maven-surefire-plugin:2.9:test (default-test) @ graphene-webdriver-ftest --- > [INFO] Surefire report directory: /mnt/workspace/workspaces/arquillian/arquillian-graphene/ftest/target/surefire-reports > [INFO] Using configured provider org.apache.maven.surefire.junitcore.JUnitCoreProvider > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Concurrency config is parallel='none', perCoreThreadCount=true, threadCount=2, useUnlimitedThreads=false > Running org.jboss.arquillian.graphene.ftest.intercept.TestInterceptorRegistration > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec > Running org.jboss.arquillian.graphene.ftest.element.TestGrapheneElementAsPageFragmentRoot > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec > Running org.jboss.arquillian.graphene.ftest.enricher.hierarchy.SomeAbstractTest > Exception in thread "ThreadedStreamConsumer" java.lang.NoSuchMethodError: org.apache.maven.surefire.report.StackTraceWriter.getThrowable()Ljava/lang/Throwable; > at org.apache.maven.surefire.report.XMLReporter.writeTestProblems(XMLReporter.java:238) > at org.apache.maven.surefire.report.XMLReporter.testError(XMLReporter.java:208) > at org.apache.maven.surefire.report.MulticastingReporter.testError(MulticastingReporter.java:73) > at org.apache.maven.surefire.report.TestSetRunListener.testError(TestSetRunListener.java:139) > at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:112) > at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:67) > at java.lang.Thread.run(Thread.java:744) > Results : > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 14:13:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 14:13:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-445) Wrong classes are injected to PageObject injection points in abstract test basis In-Reply-To: References: Message-ID: Luk?? Fry? created ARQGRA-445: --------------------------------- Summary: Wrong classes are injected to PageObject injection points in abstract test basis Key: ARQGRA-445 URL: https://issues.jboss.org/browse/ARQGRA-445 Project: Arquillian Graphene Issue Type: Bug Reporter: Luk?? Fry? These tests fails because wrong instances are injected into abstract test basis: {code} Results : Tests in error: testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects2): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects1): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3$InnerTestPage testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4$InnerTestPage {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 14:15:17 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 14:15:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-445) Wrong classes are injected to PageObject injection points in abstract test basis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971392#comment-12971392 ] Luk?? Fry? commented on ARQGRA-445: ----------------------------------- There parametrized test basis behavior could be potentially JDK-dependent, I have used following configuration to run these tests: {code} Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Maven home: /home/lfryc/Apps/apache-maven-3.0.4 Java version: 1.7.0_55, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.0.fc20.x86_64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.14.4-200.fc20.x86_64", arch: "amd64", family: "unix" {code} > Wrong classes are injected to PageObject injection points in abstract test basis > -------------------------------------------------------------------------------- > > Key: ARQGRA-445 > URL: https://issues.jboss.org/browse/ARQGRA-445 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.3.Final > Reporter: Luk?? Fry? > Fix For: 2.0.3.Final > > > These tests fails because wrong instances are injected into abstract test basis: > {code} > Results : > Tests in error: > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects2): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects1): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3$InnerTestPage > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4$InnerTestPage > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 14:15:17 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 14:15:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-445) Wrong classes are injected to PageObject injection points in abstract test basis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971393#comment-12971393 ] Luk?? Fry? commented on ARQGRA-445: ----------------------------------- [~jhuska] are you able to reproduce this issue? > Wrong classes are injected to PageObject injection points in abstract test basis > -------------------------------------------------------------------------------- > > Key: ARQGRA-445 > URL: https://issues.jboss.org/browse/ARQGRA-445 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.3.Final > Reporter: Luk?? Fry? > Fix For: 2.0.3.Final > > > These tests fails because wrong instances are injected into abstract test basis: > {code} > Results : > Tests in error: > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects2): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects1): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3$InnerTestPage > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4$InnerTestPage > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 14:15:17 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 14:15:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-445) Wrong classes are injected to PageObject injection points in abstract test basis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-445: ------------------------------ Affects Version/s: 2.0.3.Final > Wrong classes are injected to PageObject injection points in abstract test basis > -------------------------------------------------------------------------------- > > Key: ARQGRA-445 > URL: https://issues.jboss.org/browse/ARQGRA-445 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.3.Final > Reporter: Luk?? Fry? > > These tests fails because wrong instances are injected into abstract test basis: > {code} > Results : > Tests in error: > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects2): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects1): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3$InnerTestPage > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4$InnerTestPage > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 14:15:17 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 14:15:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-445) Wrong classes are injected to PageObject injection points in abstract test basis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-445: ------------------------------ Fix Version/s: 2.0.3.Final > Wrong classes are injected to PageObject injection points in abstract test basis > -------------------------------------------------------------------------------- > > Key: ARQGRA-445 > URL: https://issues.jboss.org/browse/ARQGRA-445 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.3.Final > Reporter: Luk?? Fry? > Fix For: 2.0.3.Final > > > These tests fails because wrong instances are injected into abstract test basis: > {code} > Results : > Tests in error: > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects2): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects1): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3$InnerTestPage > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4$InnerTestPage > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 14:15:17 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 14:15:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-444) Functional tests fail to run due to surefire plugin failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-444: ------------------------------ Fix Version/s: 2.0.3.Final > Functional tests fail to run due to surefire plugin failure > ----------------------------------------------------------- > > Key: ARQGRA-444 > URL: https://issues.jboss.org/browse/ARQGRA-444 > Project: Arquillian Graphene > Issue Type: Bug > Environment: $ mvn -v > Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) > Maven home: /home/lfryc/Apps/apache-maven-3.0.4 > Java version: 1.7.0_51, vendor: Oracle Corporation > Java home: /usr/java/jdk1.7.0_51/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "3.14.4-200.fc20.x86_64", arch: "amd64", family: "unix" > Reporter: Luk?? Fry? > Fix For: 2.0.3.Final > > > {code} > [INFO] --- maven-surefire-plugin:2.9:test (default-test) @ graphene-webdriver-ftest --- > [INFO] Surefire report directory: /mnt/workspace/workspaces/arquillian/arquillian-graphene/ftest/target/surefire-reports > [INFO] Using configured provider org.apache.maven.surefire.junitcore.JUnitCoreProvider > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Concurrency config is parallel='none', perCoreThreadCount=true, threadCount=2, useUnlimitedThreads=false > Running org.jboss.arquillian.graphene.ftest.intercept.TestInterceptorRegistration > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec > Running org.jboss.arquillian.graphene.ftest.element.TestGrapheneElementAsPageFragmentRoot > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec > Running org.jboss.arquillian.graphene.ftest.enricher.hierarchy.SomeAbstractTest > Exception in thread "ThreadedStreamConsumer" java.lang.NoSuchMethodError: org.apache.maven.surefire.report.StackTraceWriter.getThrowable()Ljava/lang/Throwable; > at org.apache.maven.surefire.report.XMLReporter.writeTestProblems(XMLReporter.java:238) > at org.apache.maven.surefire.report.XMLReporter.testError(XMLReporter.java:208) > at org.apache.maven.surefire.report.MulticastingReporter.testError(MulticastingReporter.java:73) > at org.apache.maven.surefire.report.TestSetRunListener.testError(TestSetRunListener.java:139) > at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:112) > at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:67) > at java.lang.Thread.run(Thread.java:744) > Results : > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 14:17:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 14:17:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-444) Functional tests fail to run due to surefire plugin failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971394#comment-12971394 ] Luk?? Fry? commented on ARQGRA-444: ----------------------------------- Upgrade to maven-surefire-plugin 2.17 helped (in fact 2.12 is a first one in serioes which addresses this issue). > Functional tests fail to run due to surefire plugin failure > ----------------------------------------------------------- > > Key: ARQGRA-444 > URL: https://issues.jboss.org/browse/ARQGRA-444 > Project: Arquillian Graphene > Issue Type: Bug > Environment: $ mvn -v > Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) > Maven home: /home/lfryc/Apps/apache-maven-3.0.4 > Java version: 1.7.0_51, vendor: Oracle Corporation > Java home: /usr/java/jdk1.7.0_51/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "3.14.4-200.fc20.x86_64", arch: "amd64", family: "unix" > Reporter: Luk?? Fry? > Fix For: 2.0.3.Final > > > {code} > [INFO] --- maven-surefire-plugin:2.9:test (default-test) @ graphene-webdriver-ftest --- > [INFO] Surefire report directory: /mnt/workspace/workspaces/arquillian/arquillian-graphene/ftest/target/surefire-reports > [INFO] Using configured provider org.apache.maven.surefire.junitcore.JUnitCoreProvider > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Concurrency config is parallel='none', perCoreThreadCount=true, threadCount=2, useUnlimitedThreads=false > Running org.jboss.arquillian.graphene.ftest.intercept.TestInterceptorRegistration > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec > Running org.jboss.arquillian.graphene.ftest.element.TestGrapheneElementAsPageFragmentRoot > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec > Running org.jboss.arquillian.graphene.ftest.enricher.hierarchy.SomeAbstractTest > Exception in thread "ThreadedStreamConsumer" java.lang.NoSuchMethodError: org.apache.maven.surefire.report.StackTraceWriter.getThrowable()Ljava/lang/Throwable; > at org.apache.maven.surefire.report.XMLReporter.writeTestProblems(XMLReporter.java:238) > at org.apache.maven.surefire.report.XMLReporter.testError(XMLReporter.java:208) > at org.apache.maven.surefire.report.MulticastingReporter.testError(MulticastingReporter.java:73) > at org.apache.maven.surefire.report.TestSetRunListener.testError(TestSetRunListener.java:139) > at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:112) > at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:67) > at java.lang.Thread.run(Thread.java:744) > Results : > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 14:17:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 14:17:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-444) Functional tests fail to run due to surefire plugin failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQGRA-444. ------------------------------- Assignee: Luk?? Fry? Resolution: Done > Functional tests fail to run due to surefire plugin failure > ----------------------------------------------------------- > > Key: ARQGRA-444 > URL: https://issues.jboss.org/browse/ARQGRA-444 > Project: Arquillian Graphene > Issue Type: Bug > Environment: $ mvn -v > Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) > Maven home: /home/lfryc/Apps/apache-maven-3.0.4 > Java version: 1.7.0_51, vendor: Oracle Corporation > Java home: /usr/java/jdk1.7.0_51/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "3.14.4-200.fc20.x86_64", arch: "amd64", family: "unix" > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 2.0.3.Final > > > {code} > [INFO] --- maven-surefire-plugin:2.9:test (default-test) @ graphene-webdriver-ftest --- > [INFO] Surefire report directory: /mnt/workspace/workspaces/arquillian/arquillian-graphene/ftest/target/surefire-reports > [INFO] Using configured provider org.apache.maven.surefire.junitcore.JUnitCoreProvider > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Concurrency config is parallel='none', perCoreThreadCount=true, threadCount=2, useUnlimitedThreads=false > Running org.jboss.arquillian.graphene.ftest.intercept.TestInterceptorRegistration > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec > Running org.jboss.arquillian.graphene.ftest.element.TestGrapheneElementAsPageFragmentRoot > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec > Running org.jboss.arquillian.graphene.ftest.enricher.hierarchy.SomeAbstractTest > Exception in thread "ThreadedStreamConsumer" java.lang.NoSuchMethodError: org.apache.maven.surefire.report.StackTraceWriter.getThrowable()Ljava/lang/Throwable; > at org.apache.maven.surefire.report.XMLReporter.writeTestProblems(XMLReporter.java:238) > at org.apache.maven.surefire.report.XMLReporter.testError(XMLReporter.java:208) > at org.apache.maven.surefire.report.MulticastingReporter.testError(MulticastingReporter.java:73) > at org.apache.maven.surefire.report.TestSetRunListener.testError(TestSetRunListener.java:139) > at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:112) > at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:67) > at java.lang.Thread.run(Thread.java:744) > Results : > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 14:19:16 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 14:19:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-435) Graphene wait does not find @Qualified browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-435: ------------------------------ Fix Version/s: (was: 2.0.3.Final) > Graphene wait does not find @Qualified browser > ---------------------------------------------- > > Key: ARQGRA-435 > URL: https://issues.jboss.org/browse/ARQGRA-435 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Karel Piwko > Assignee: Juraj H?ska > Priority: Critical > > It is not possible to wait when browser is qualifiered: > {code} > package com.acme.example.test; > import java.lang.annotation.Retention; > import java.lang.annotation.RetentionPolicy; > import java.net.URL; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.drone.api.annotation.Drone; > import org.jboss.arquillian.drone.api.annotation.Qualifier; > import org.jboss.arquillian.graphene.Graphene; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.arquillian.test.api.ArquillianResource; > import org.jboss.shrinkwrap.api.Archive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > import org.openqa.selenium.WebDriver; > import org.openqa.selenium.WebElement; > import org.openqa.selenium.support.FindBy; > @RunWith(Arquillian.class) > public class GrapheneBugDroneTest { > @Drone > @BugReport > WebDriver driver; > @Deployment(testable = false) > public static Archive deployHtml5DemoApp() { > return Deployments.createDeployment(); > } > @ArquillianResource > URL url; > @FindBy(id = "name") > WebElement nameField; > @Test > public void addUser() throws Exception { > driver.get(url.toString()); > Graphene.waitGui(driver).until().element(nameField).is().present(); > Assert.assertTrue(true); > } > @Qualifier > @Retention(RetentionPolicy.RUNTIME) > public static @interface BugReport { > } > } > {code} > Wait *Graphene.waitGui(driver).until().element(nameField).is().present();* > fails with > {code} > java.lang.IllegalStateException: There is no context available for qualifier org.jboss.arquillian.drone.api.annotation.Default. Available contexts are [interface com.acme.example.test.GrapheneBugDroneTest$BugReport]. > at org.jboss.arquillian.graphene.context.GrapheneContextImpl$LazyContext.getContext(GrapheneContextImpl.java:302) > at org.jboss.arquillian.graphene.context.GrapheneContextImpl$LazyContext.getConfiguration(GrapheneContextImpl.java:234) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.waitGui(DefaultGrapheneRuntime.java:104) > at org.jboss.arquillian.graphene.Graphene.waitGui(Graphene.java:216) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy28.isDisplayed(Unknown Source) > at org.jboss.arquillian.graphene.condition.element.ElementIsPresent.check(ElementIsPresent.java:44) > at org.jboss.arquillian.graphene.condition.element.ElementIsPresent.check(ElementIsPresent.java:31) > at org.jboss.arquillian.graphene.condition.element.AbstractElementBooleanCondition.apply(AbstractElementBooleanCondition.java:52) > at org.jboss.arquillian.graphene.condition.element.AbstractElementBooleanCondition.apply(AbstractElementBooleanCondition.java:33) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:102) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.commit(WebDriverWaitImpl.java:110) > at org.jboss.arquillian.graphene.wait.IsNotElementBuilderImpl.present(IsNotElementBuilderImpl.java:47) > at com.acme.example.test.GrapheneBugDroneTest.addUser(GrapheneBugDroneTest.java:42) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:273) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:266) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:229) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:243) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:188) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:202) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:150) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) > {code} > Arquillian configuration: > * Core 1.1.4.Final > * Graphene 2.0.2.Final > * Drone 2.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 14:19:16 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 14:19:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-441) xhrInterception breaks applications using jQuery 2.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-441: ------------------------------ Assignee: Oliver Ki?? > xhrInterception breaks applications using jQuery 2.x > ---------------------------------------------------- > > Key: ARQGRA-441 > URL: https://issues.jboss.org/browse/ARQGRA-441 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final, 2.0.2.Final > Environment: Firefox 29, Chrome 34 > Reporter: Oliver Ki?? > Assignee: Oliver Ki?? > Priority: Critical > Fix For: 2.0.3.Final > > > After {{[kitchensink-backbone|https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.6.x-develop/kitchensink-backbone]}} and {{[contacts-mobile-basic|https://github.com/jboss-developer/jboss-wfk-quickstarts/pull/154]}} quickstarts were updated to use jQuery 2.0.3, Graphene guards no longer work properly in their functional tests. > After {{window.Graphene.xhrInterception.install()}}, the quickstarts do not react to responses to ajax requests they make (server side validation messages are not shown, member list is not displayed, no feedback is shown after a new member is registered). > When {{window.Graphene.xhrInterception.uninstall()}} is run, the quickstarts start behaving normally again. > I tried reproducing the issue with different versions of javascript libraries used in the quickstarts and could reproduce it if jQuery 2.x was used (tested 2.0.3 and 2.1.0). Other libraries do not seem to have an effect on the issue. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 14:21:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 14:21:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-433) FieldAccessValidatorEnricher checks access to fields uniformly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971395#comment-12971395 ] Luk?? Fry? commented on ARQGRA-433: ----------------------------------- [~jhuska], [~smikloso] any chance you could you into the changes this week? We need to release 2.0.3 by friday. > FieldAccessValidatorEnricher checks access to fields uniformly > -------------------------------------------------------------- > > Key: ARQGRA-433 > URL: https://issues.jboss.org/browse/ARQGRA-433 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Stefan Miklosovic > Priority: Optional > Fix For: 2.0.3.Final > > > I have this test > {code} > @Rule > public ExpectedException expectedException = ExpectedException.none(); > @Test > @InSequence(2) > @ReportMessage("This method should pass.") > public void testWithExpectedExceptionRule() { > expectedException.expect(RuntimeException.class); > throw new RuntimeException("this exception is expected"); > } > {code} > Logger writes this out: > WARNING: Public field 'expectedException' found in org.arquillian.droidium.devconf.AeroGearTestCase. Direct access to fields outside of the declaring class is not allowed. > Apr 01, 2014 11:50:27 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > However that @Rule field _has to be_ public > {quote} > A field must be public, not static, and a subtype of TestRule > {quote} > So in this case validation does not make sense. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 14:30:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 14:30:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-442) Graphene is not compatible with selenium 2.42.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-442: ------------------------------ Assignee: Sona Jamborova > Graphene is not compatible with selenium 2.42.0 > ----------------------------------------------- > > Key: ARQGRA-442 > URL: https://issues.jboss.org/browse/ARQGRA-442 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.2.Final > Reporter: Sona Jamborova > Assignee: Sona Jamborova > Fix For: 2.0.3.Final > > > The update of version of selenium-bom to 2.42.0 cause problems in my test suite which uses Arquillian Graphene. It seems that Graphene expected class org.openqa.selenium.html5.BrowserConnection which was deleted by this commit http://code.google.com/p/selenium/source/detail?r=8629dc6ec6ddd96bbe0975ee86d0c4c2f4b9ebb2 > Exception is here: http://pastebin.test.redhat.com/211410 > Selenium 2.42.0 contains some fixes which blocks our test suite: > - Fixing interactions API in Firefox to be able to move mouse to elements in frames using native events. Fixes issue 7253 > - Click after move with offset should use last mouse position > - Fixing IE driver crash when clicking on link that opens a new window. > - etc. > I will appreciate a quick fix (minor release). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 14:32:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 14:32:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-442) Graphene is not compatible with selenium 2.42.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971400#comment-12971400 ] Luk?? Fry? commented on ARQGRA-442: ----------------------------------- Thanks Sona! Reviewed the patch and it's good to go! Let's get it merged. > Graphene is not compatible with selenium 2.42.0 > ----------------------------------------------- > > Key: ARQGRA-442 > URL: https://issues.jboss.org/browse/ARQGRA-442 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.2.Final > Reporter: Sona Jamborova > Assignee: Sona Jamborova > Fix For: 2.0.3.Final > > > The update of version of selenium-bom to 2.42.0 cause problems in my test suite which uses Arquillian Graphene. It seems that Graphene expected class org.openqa.selenium.html5.BrowserConnection which was deleted by this commit http://code.google.com/p/selenium/source/detail?r=8629dc6ec6ddd96bbe0975ee86d0c4c2f4b9ebb2 > Exception is here: http://pastebin.test.redhat.com/211410 > Selenium 2.42.0 contains some fixes which blocks our test suite: > - Fixing interactions API in Firefox to be able to move mouse to elements in frames using native events. Fixes issue 7253 > - Click after move with offset should use last mouse position > - Fixing IE driver crash when clicking on link that opens a new window. > - etc. > I will appreciate a quick fix (minor release). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 14:34:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 28 May 2014 14:34:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-442) Graphene is not compatible with selenium 2.42.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-442: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Graphene is not compatible with selenium 2.42.0 > ----------------------------------------------- > > Key: ARQGRA-442 > URL: https://issues.jboss.org/browse/ARQGRA-442 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.2.Final > Reporter: Sona Jamborova > Assignee: Sona Jamborova > Fix For: 2.0.3.Final > > > The update of version of selenium-bom to 2.42.0 cause problems in my test suite which uses Arquillian Graphene. It seems that Graphene expected class org.openqa.selenium.html5.BrowserConnection which was deleted by this commit http://code.google.com/p/selenium/source/detail?r=8629dc6ec6ddd96bbe0975ee86d0c4c2f4b9ebb2 > Exception is here: http://pastebin.test.redhat.com/211410 > Selenium 2.42.0 contains some fixes which blocks our test suite: > - Fixing interactions API in Firefox to be able to move mouse to elements in frames using native events. Fixes issue 7253 > - Click after move with offset should use last mouse position > - Fixing IE driver crash when clicking on link that opens a new window. > - etc. > I will appreciate a quick fix (minor release). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 16:43:15 2014 From: issues at jboss.org (William Crowell (JIRA)) Date: Wed, 28 May 2014 16:43:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1769) org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971427#comment-12971427 ] William Crowell commented on ARQ-1769: -------------------------------------- I moved to phantomjs but I still have the issue. I don't think it is an issue with the client-side code runner but I will still move to phantomjs regardless. Using 1.0.0.Alpha7, the test WAR application starts up; however, the first request (using the driver.navigate().to("http://localhost:8080...") to the application gives the org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException. If I set a breakpoint in the test case and open a browser and hit the URL directly I get the same StoreHasAssociatedObjectsException. In org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl on line 126 I see this check in checkUnbound(LifecycleManager): @Override protected void checkUnbound(LifecycleManager manager) throws StoreHasAssociatedObjectsException { Tracking tracking = TRACK.get(manager); if (tracking != null) { if (!tracking.isEmpty()) { throw new StoreHasAssociatedObjectsException(); } TRACK.remove(manager); } } The tracking HashMap has an object with the key name "class javax.faces.context.FacesContext". However, 1.0.0.Alpha6, has different behavior. The first request works and the Activity inner classes' perform() method gets called, but the inspect inner class never gets called even though we match for all requests: group().observe(request()).inspect(new Inspection()... Then org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint.awaitResponses() just sits until the arquillian.warp.synchronization.timeout (default of 5 seconds) expires: ... (E) PassivateManager (I) ManagerActivationObserver.deactivateApplicationContext (E) AfterRequest (I) LifecycleTestClassExecutor.afterRequest (E) PassivateManager (I) ManagerActivationObserver.deactivateApplicationContext (E) AwaitResponse (O) WarpExecutionObserver.awaitResponse ... I looked at the jsf-ftest sample code on github to see if I was missing something. I see some archives like arquillian-warp-jsf that contain a fragment for faces-config.xml. It defines a WarpPhaseListener and a FacesContextFactoryWrapper. I included arquillian-warp-jsf in my pom.xml but the problem remained. I have one of two possible theories here: 1) I am missing a dependency which binds/unbinds the FacesContext. 2) Is it possible that Arquillian Warp does not support PrimeFaces and/or Spring WebFlow? I see quite a bit of support for RichFaces. Maybe an adapter needs to be written for PrimeFaces. Not sure. > org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > -------------------------------------------------------------------------- > > Key: ARQ-1769 > URL: https://issues.jboss.org/browse/ARQ-1769 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, 1.1.3.Final, 1.1.4.Final > Environment: Windows 7 Enterprise SP1 64-bit > Reporter: William Crowell > > I am using the following: > Arquillian Core: 1.1.4.Final (as well as 1.1.3.Final) > Arquillian Drone: 1.2.4.Final (I've tried Drone 2 as well) > Arquillian Warp: 1.0.0.Alpha7 (as well as 1.0.0.Beta1-SNAPSHOT) > Arquillian Transaction: 1.0.1.Final > Arquillian Tomcat 7 Embedded Container using Tomcat 7.0.27: 1.0.0.Final-SNAPSHOT > Spring: 3.2.4.RELEASE > Spring Web: 3.2.2.RELEASE > Spring Security: 3.1.4.RELEASE > Spring WebFlow: 2.4.0.RC1 > PrimeFaces 3.4.2 > JUnit: 4.8.2 > Mojarra 2.1.17 > I am receiving this exception: > {code} > java.lang.IllegalStateException: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:69) > ... > 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.LifecycleTestClassExecutor.afterRequest(LifecycleTestClassExecutor.java:78) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.request.RequestContextHandler.handleRequestContext(RequestContextHandler.java:93) > ... > 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:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:151) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:120) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:93) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:183) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87) > at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192) > at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160) > at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) > at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) > at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > ... > Caused by: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl.checkUnbound(LifecycleManagerStoreImpl.java:126) > at org.jboss.arquillian.warp.spi.LifecycleManager.checkUnbound(LifecycleManager.java:158) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:67) > ... 74 more > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 03:59:15 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 29 May 2014 03:59:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-445) Wrong classes are injected to PageObject injection points in abstract test basis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971492#comment-12971492 ] Juraj H?ska commented on ARQGRA-445: ------------------------------------ I can reproduce it with different JDK & Maven: {code} Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T18:37:52+01:00) Maven home: /opt/apache-maven-3.2.1 Java version: 1.7.0_51, vendor: Oracle Corporation Java home: /usr/java/jdk1.7.0_51/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.14.4-200.fc20.x86_64", arch: "amd64", family: "unix" {code} > Wrong classes are injected to PageObject injection points in abstract test basis > -------------------------------------------------------------------------------- > > Key: ARQGRA-445 > URL: https://issues.jboss.org/browse/ARQGRA-445 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.3.Final > Reporter: Luk?? Fry? > Fix For: 2.0.3.Final > > > These tests fails because wrong instances are injected into abstract test basis: > {code} > Results : > Tests in error: > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects2): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects1): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3$InnerTestPage > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4$InnerTestPage > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 05:04:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 29 May 2014 05:04:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-445) Wrong classes are injected to PageObject injection points in abstract test basis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971515#comment-12971515 ] Luk?? Fry? commented on ARQGRA-445: ----------------------------------- Do you believe this needs to be fixed in 2.0.3? > Wrong classes are injected to PageObject injection points in abstract test basis > -------------------------------------------------------------------------------- > > Key: ARQGRA-445 > URL: https://issues.jboss.org/browse/ARQGRA-445 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.3.Final > Reporter: Luk?? Fry? > Fix For: 2.0.3.Final > > > These tests fails because wrong instances are injected into abstract test basis: > {code} > Results : > Tests in error: > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects2): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects1): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3$InnerTestPage > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4$InnerTestPage > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 05:08:17 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 29 May 2014 05:08:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-445) Wrong classes are injected to PageObject injection points in abstract test basis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971520#comment-12971520 ] Juraj H?ska commented on ARQGRA-445: ------------------------------------ IMHO we should have stable tests at what ever price. This issue is introduced with upgrading of surefire plugin. We can either * resolve it * downgrade surefire plugin > Wrong classes are injected to PageObject injection points in abstract test basis > -------------------------------------------------------------------------------- > > Key: ARQGRA-445 > URL: https://issues.jboss.org/browse/ARQGRA-445 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.3.Final > Reporter: Luk?? Fry? > Fix For: 2.0.3.Final > > > These tests fails because wrong instances are injected into abstract test basis: > {code} > Results : > Tests in error: > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects2): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects1): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3$InnerTestPage > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4$InnerTestPage > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 05:35:17 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 29 May 2014 05:35:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-433) FieldAccessValidatorEnricher checks access to fields uniformly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971535#comment-12971535 ] Stefan Miklosovic commented on ARQGRA-433: ------------------------------------------ [~lfryc] According to irc communication we have come to solution however before implementing it, lets see if it is worth of it. You have to make difference between test case and bean in order to take (1) into account or not. Enrich method of enricher is called here (2). You would basically add a flag to enrichRecursively method - when set to true, if enricher you want to use is FieldAccessValidator, it would not be skipped, if false, it would be skipped. However it means you would have to break interface (3) and "repair it" in these cases (4) I would personaly remove that FieldAccessEnricherValidator from Graphene completely when you are considering to remove it in the future, why not to remove it now ... (1) https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/enricher/FieldAccessValidatorEnricher.java (2) https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/enricher/AbstractSearchContextEnricher.java#L74 (3) https://github.com/arquillian/arquillian-graphene/blob/master/spi/src/main/java/org/jboss/arquillian/graphene/spi/enricher/SearchContextTestEnricher.java (4) https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/GrapheneExtension.java#L67-L74 > FieldAccessValidatorEnricher checks access to fields uniformly > -------------------------------------------------------------- > > Key: ARQGRA-433 > URL: https://issues.jboss.org/browse/ARQGRA-433 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Stefan Miklosovic > Priority: Optional > Fix For: 2.0.3.Final > > > I have this test > {code} > @Rule > public ExpectedException expectedException = ExpectedException.none(); > @Test > @InSequence(2) > @ReportMessage("This method should pass.") > public void testWithExpectedExceptionRule() { > expectedException.expect(RuntimeException.class); > throw new RuntimeException("this exception is expected"); > } > {code} > Logger writes this out: > WARNING: Public field 'expectedException' found in org.arquillian.droidium.devconf.AeroGearTestCase. Direct access to fields outside of the declaring class is not allowed. > Apr 01, 2014 11:50:27 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > However that @Rule field _has to be_ public > {quote} > A field must be public, not static, and a subtype of TestRule > {quote} > So in this case validation does not make sense. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 05:39:16 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 29 May 2014 05:39:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-433) FieldAccessValidatorEnricher checks access to fields uniformly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971535#comment-12971535 ] Stefan Miklosovic edited comment on ARQGRA-433 at 5/29/14 5:37 AM: ------------------------------------------------------------------- [~lfryc] According to irc communication we have come to solution however before implementing it, lets see if it is worth of it. You have to make difference between test case and bean in order to take (1) into account or not. Enrich method of enricher is called here (2). You would basically add a flag to enrichRecursively method - when set to true, if enricher you want to use is FieldAccessValidator, it would not be skipped, if false, it would be skipped. However it means you would have to break interface (3) and "repair it" in these cases (4) Another solution is to check if class is annotated with RunWith (junit case) or extends Arquillian (in case of TestNG) however I am against this solution, you are becoming dependent on specific test runner which is really bad way to do deal with this for various reasons. Additionally, I think you can not even do it, I was trying to do this "runner resolution" in Arquillian Reporter and I didnt work. I would personaly remove that FieldAccessEnricherValidator from Graphene completely when you are considering to remove it in the future, why not to remove it now ... (1) https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/enricher/FieldAccessValidatorEnricher.java (2) https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/enricher/AbstractSearchContextEnricher.java#L74 (3) https://github.com/arquillian/arquillian-graphene/blob/master/spi/src/main/java/org/jboss/arquillian/graphene/spi/enricher/SearchContextTestEnricher.java (4) https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/GrapheneExtension.java#L67-L74 was (Author: smikloso): [~lfryc] According to irc communication we have come to solution however before implementing it, lets see if it is worth of it. You have to make difference between test case and bean in order to take (1) into account or not. Enrich method of enricher is called here (2). You would basically add a flag to enrichRecursively method - when set to true, if enricher you want to use is FieldAccessValidator, it would not be skipped, if false, it would be skipped. However it means you would have to break interface (3) and "repair it" in these cases (4) I would personaly remove that FieldAccessEnricherValidator from Graphene completely when you are considering to remove it in the future, why not to remove it now ... (1) https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/enricher/FieldAccessValidatorEnricher.java (2) https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/enricher/AbstractSearchContextEnricher.java#L74 (3) https://github.com/arquillian/arquillian-graphene/blob/master/spi/src/main/java/org/jboss/arquillian/graphene/spi/enricher/SearchContextTestEnricher.java (4) https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/GrapheneExtension.java#L67-L74 > FieldAccessValidatorEnricher checks access to fields uniformly > -------------------------------------------------------------- > > Key: ARQGRA-433 > URL: https://issues.jboss.org/browse/ARQGRA-433 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Stefan Miklosovic > Priority: Optional > Fix For: 2.0.3.Final > > > I have this test > {code} > @Rule > public ExpectedException expectedException = ExpectedException.none(); > @Test > @InSequence(2) > @ReportMessage("This method should pass.") > public void testWithExpectedExceptionRule() { > expectedException.expect(RuntimeException.class); > throw new RuntimeException("this exception is expected"); > } > {code} > Logger writes this out: > WARNING: Public field 'expectedException' found in org.arquillian.droidium.devconf.AeroGearTestCase. Direct access to fields outside of the declaring class is not allowed. > Apr 01, 2014 11:50:27 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > However that @Rule field _has to be_ public > {quote} > A field must be public, not static, and a subtype of TestRule > {quote} > So in this case validation does not make sense. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 05:45:17 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 29 May 2014 05:45:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-445) Wrong classes are injected to PageObject injection points in abstract test basis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971545#comment-12971545 ] Luk?? Fry? edited comment on ARQGRA-445 at 5/29/14 5:43 AM: ------------------------------------------------------------ I had to upgrade surefire plugin because of its failure in previous versions, ARQGRA-444. I have also verified that all the plugin versions that fixes original failure introduces this failure. Graphene should be definitely independent on what JDK and plugin versions you use, so I don't believe downgrading is a correct approach. > Wrong classes are injected to PageObject injection points in abstract test basis > -------------------------------------------------------------------------------- > > Key: ARQGRA-445 > URL: https://issues.jboss.org/browse/ARQGRA-445 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.3.Final > Reporter: Luk?? Fry? > Fix For: 2.0.3.Final > > > These tests fails because wrong instances are injected into abstract test basis: > {code} > Results : > Tests in error: > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects2): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testPageObjectWithGenericTypeIsInitialized2(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects1): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.page.TestPage2 > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects3$InnerTestPage > testInitializingPageObjectsDeclaredAsInnerClassesGeneric(org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4): org.jboss.arquillian.graphene.ftest.enricher.page.TestPage$$EnhancerByGraphene$$841cfb04 cannot be cast to org.jboss.arquillian.graphene.ftest.enricher.TestInitializingGenericPageObjects4$InnerTestPage > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 05:49:16 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 29 May 2014 05:49:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-433) FieldAccessValidatorEnricher checks access to fields uniformly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971550#comment-12971550 ] Karel Piwko commented on ARQGRA-433: ------------------------------------ +1 on not relying on {{@RunWith}} or {{extends Arquillian}}. I still miss why FieldAccessEnricher can't trigger only for enrichers defined at https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/GrapheneExtension.java#L67-L74 , e.g. moving FieldAccessValidatorEnricher functionality into AbstractSeachContextEnricher. > FieldAccessValidatorEnricher checks access to fields uniformly > -------------------------------------------------------------- > > Key: ARQGRA-433 > URL: https://issues.jboss.org/browse/ARQGRA-433 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Stefan Miklosovic > Priority: Optional > Fix For: 2.0.3.Final > > > I have this test > {code} > @Rule > public ExpectedException expectedException = ExpectedException.none(); > @Test > @InSequence(2) > @ReportMessage("This method should pass.") > public void testWithExpectedExceptionRule() { > expectedException.expect(RuntimeException.class); > throw new RuntimeException("this exception is expected"); > } > {code} > Logger writes this out: > WARNING: Public field 'expectedException' found in org.arquillian.droidium.devconf.AeroGearTestCase. Direct access to fields outside of the declaring class is not allowed. > Apr 01, 2014 11:50:27 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > However that @Rule field _has to be_ public > {quote} > A field must be public, not static, and a subtype of TestRule > {quote} > So in this case validation does not make sense. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 05:59:17 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 29 May 2014 05:59:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-433) FieldAccessValidatorEnricher checks access to fields uniformly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971555#comment-12971555 ] Juraj H?ska commented on ARQGRA-433: ------------------------------------ What about excluding that particular enricher just here: https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/enricher/GrapheneEnricher.java#L51 > FieldAccessValidatorEnricher checks access to fields uniformly > -------------------------------------------------------------- > > Key: ARQGRA-433 > URL: https://issues.jboss.org/browse/ARQGRA-433 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Stefan Miklosovic > Priority: Optional > Fix For: 2.0.3.Final > > > I have this test > {code} > @Rule > public ExpectedException expectedException = ExpectedException.none(); > @Test > @InSequence(2) > @ReportMessage("This method should pass.") > public void testWithExpectedExceptionRule() { > expectedException.expect(RuntimeException.class); > throw new RuntimeException("this exception is expected"); > } > {code} > Logger writes this out: > WARNING: Public field 'expectedException' found in org.arquillian.droidium.devconf.AeroGearTestCase. Direct access to fields outside of the declaring class is not allowed. > Apr 01, 2014 11:50:27 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > However that @Rule field _has to be_ public > {quote} > A field must be public, not static, and a subtype of TestRule > {quote} > So in this case validation does not make sense. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 06:01:19 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 29 May 2014 06:01:19 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-433) FieldAccessValidatorEnricher checks access to fields uniformly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971555#comment-12971555 ] Juraj H?ska edited comment on ARQGRA-433 at 5/29/14 6:00 AM: ------------------------------------------------------------- What about excluding that particular enricher just here: https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/enricher/GrapheneEnricher.java#L51 That is the place where enrichers are called over Test Case Object. was (Author: jhuska): What about excluding that particular enricher just here: https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/enricher/GrapheneEnricher.java#L51 > FieldAccessValidatorEnricher checks access to fields uniformly > -------------------------------------------------------------- > > Key: ARQGRA-433 > URL: https://issues.jboss.org/browse/ARQGRA-433 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Stefan Miklosovic > Priority: Optional > Fix For: 2.0.3.Final > > > I have this test > {code} > @Rule > public ExpectedException expectedException = ExpectedException.none(); > @Test > @InSequence(2) > @ReportMessage("This method should pass.") > public void testWithExpectedExceptionRule() { > expectedException.expect(RuntimeException.class); > throw new RuntimeException("this exception is expected"); > } > {code} > Logger writes this out: > WARNING: Public field 'expectedException' found in org.arquillian.droidium.devconf.AeroGearTestCase. Direct access to fields outside of the declaring class is not allowed. > Apr 01, 2014 11:50:27 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > However that @Rule field _has to be_ public > {quote} > A field must be public, not static, and a subtype of TestRule > {quote} > So in this case validation does not make sense. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 06:03:16 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 29 May 2014 06:03:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-433) FieldAccessValidatorEnricher checks access to fields uniformly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971556#comment-12971556 ] Luk?? Fry? commented on ARQGRA-433: ----------------------------------- {quote} I would personaly remove that FieldAccessEnricherValidator from Graphene completely when you are considering to remove it in the future, why not to remove it now ... {quote} [As I have pointed out|https://issues.jboss.org/browse/ARQGRA-433?focusedCommentId=12963482&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12963482], there are two reasons why using publicly accessible fields can't be recommended. We either need to fix the approach how proxies are used for interception of calls and injections or we should keep warning user that his usage can has unexpected consequences. ---- One approach that could work without checking test class annotations is leveraging Arquillian BeforeClass event, that contain a type of the test class. When stored properly, you can access it during injection time. > FieldAccessValidatorEnricher checks access to fields uniformly > -------------------------------------------------------------- > > Key: ARQGRA-433 > URL: https://issues.jboss.org/browse/ARQGRA-433 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Stefan Miklosovic > Priority: Optional > Fix For: 2.0.3.Final > > > I have this test > {code} > @Rule > public ExpectedException expectedException = ExpectedException.none(); > @Test > @InSequence(2) > @ReportMessage("This method should pass.") > public void testWithExpectedExceptionRule() { > expectedException.expect(RuntimeException.class); > throw new RuntimeException("this exception is expected"); > } > {code} > Logger writes this out: > WARNING: Public field 'expectedException' found in org.arquillian.droidium.devconf.AeroGearTestCase. Direct access to fields outside of the declaring class is not allowed. > Apr 01, 2014 11:50:27 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > However that @Rule field _has to be_ public > {quote} > A field must be public, not static, and a subtype of TestRule > {quote} > So in this case validation does not make sense. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 06:05:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 29 May 2014 06:05:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-433) FieldAccessValidatorEnricher checks access to fields uniformly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971556#comment-12971556 ] Luk?? Fry? edited comment on ARQGRA-433 at 5/29/14 6:03 AM: ------------------------------------------------------------ {quote} I would personaly remove that FieldAccessEnricherValidator from Graphene completely when you are considering to remove it in the future, why not to remove it now ... {quote} [As I have pointed out|https://issues.jboss.org/browse/ARQGRA-433?focusedCommentId=12963482&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12963482], there are two reasons why using publicly accessible fields can't be recommended. We either need to fix the approach how proxies are used for interception of calls and injections or we should keep warning user that his usage can has unexpected consequences. ---- One approach that could work without checking test class annotations is leveraging Arquillian BeforeClass event, that contain a type of the test class. When stored properly, you can access it during injection time and check whether enriched object is type of test being ran at the moment. was (Author: lfryc): {quote} I would personaly remove that FieldAccessEnricherValidator from Graphene completely when you are considering to remove it in the future, why not to remove it now ... {quote} [As I have pointed out|https://issues.jboss.org/browse/ARQGRA-433?focusedCommentId=12963482&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12963482], there are two reasons why using publicly accessible fields can't be recommended. We either need to fix the approach how proxies are used for interception of calls and injections or we should keep warning user that his usage can has unexpected consequences. ---- One approach that could work without checking test class annotations is leveraging Arquillian BeforeClass event, that contain a type of the test class. When stored properly, you can access it during injection time. > FieldAccessValidatorEnricher checks access to fields uniformly > -------------------------------------------------------------- > > Key: ARQGRA-433 > URL: https://issues.jboss.org/browse/ARQGRA-433 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Stefan Miklosovic > Priority: Optional > Fix For: 2.0.3.Final > > > I have this test > {code} > @Rule > public ExpectedException expectedException = ExpectedException.none(); > @Test > @InSequence(2) > @ReportMessage("This method should pass.") > public void testWithExpectedExceptionRule() { > expectedException.expect(RuntimeException.class); > throw new RuntimeException("this exception is expected"); > } > {code} > Logger writes this out: > WARNING: Public field 'expectedException' found in org.arquillian.droidium.devconf.AeroGearTestCase. Direct access to fields outside of the declaring class is not allowed. > Apr 01, 2014 11:50:27 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > However that @Rule field _has to be_ public > {quote} > A field must be public, not static, and a subtype of TestRule > {quote} > So in this case validation does not make sense. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 06:11:16 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 29 May 2014 06:11:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-433) FieldAccessValidatorEnricher checks access to fields uniformly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971558#comment-12971558 ] Luk?? Fry? commented on ARQGRA-433: ----------------------------------- +1, Juraj's solution seems to be most viable :-) > FieldAccessValidatorEnricher checks access to fields uniformly > -------------------------------------------------------------- > > Key: ARQGRA-433 > URL: https://issues.jboss.org/browse/ARQGRA-433 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Stefan Miklosovic > Priority: Optional > Fix For: 2.0.3.Final > > > I have this test > {code} > @Rule > public ExpectedException expectedException = ExpectedException.none(); > @Test > @InSequence(2) > @ReportMessage("This method should pass.") > public void testWithExpectedExceptionRule() { > expectedException.expect(RuntimeException.class); > throw new RuntimeException("this exception is expected"); > } > {code} > Logger writes this out: > WARNING: Public field 'expectedException' found in org.arquillian.droidium.devconf.AeroGearTestCase. Direct access to fields outside of the declaring class is not allowed. > Apr 01, 2014 11:50:27 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > However that @Rule field _has to be_ public > {quote} > A field must be public, not static, and a subtype of TestRule > {quote} > So in this case validation does not make sense. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 06:13:15 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 29 May 2014 06:13:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-433) FieldAccessValidatorEnricher checks access to fields uniformly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971556#comment-12971556 ] Luk?? Fry? edited comment on ARQGRA-433 at 5/29/14 6:11 AM: ------------------------------------------------------------ {quote} I would personaly remove that FieldAccessEnricherValidator from Graphene completely when you are considering to remove it in the future, why not to remove it now ... {quote} [As I have pointed out|https://issues.jboss.org/browse/ARQGRA-433?focusedCommentId=12963482&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12963482], there are two reasons why using publicly accessible fields can't be recommended. We either need to fix the approach how proxies are used for interception of calls and injections or we should keep warning user that his usage can has unexpected consequences. ---- -One approach that could work without checking test class annotations is leveraging Arquillian BeforeClass event, that contain a type of the test class. When stored properly, you can access it during injection time and check whether enriched object is type of test being ran at the moment.- was (Author: lfryc): {quote} I would personaly remove that FieldAccessEnricherValidator from Graphene completely when you are considering to remove it in the future, why not to remove it now ... {quote} [As I have pointed out|https://issues.jboss.org/browse/ARQGRA-433?focusedCommentId=12963482&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12963482], there are two reasons why using publicly accessible fields can't be recommended. We either need to fix the approach how proxies are used for interception of calls and injections or we should keep warning user that his usage can has unexpected consequences. ---- One approach that could work without checking test class annotations is leveraging Arquillian BeforeClass event, that contain a type of the test class. When stored properly, you can access it during injection time and check whether enriched object is type of test being ran at the moment. > FieldAccessValidatorEnricher checks access to fields uniformly > -------------------------------------------------------------- > > Key: ARQGRA-433 > URL: https://issues.jboss.org/browse/ARQGRA-433 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Stefan Miklosovic > Priority: Optional > Fix For: 2.0.3.Final > > > I have this test > {code} > @Rule > public ExpectedException expectedException = ExpectedException.none(); > @Test > @InSequence(2) > @ReportMessage("This method should pass.") > public void testWithExpectedExceptionRule() { > expectedException.expect(RuntimeException.class); > throw new RuntimeException("this exception is expected"); > } > {code} > Logger writes this out: > WARNING: Public field 'expectedException' found in org.arquillian.droidium.devconf.AeroGearTestCase. Direct access to fields outside of the declaring class is not allowed. > Apr 01, 2014 11:50:27 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > However that @Rule field _has to be_ public > {quote} > A field must be public, not static, and a subtype of TestRule > {quote} > So in this case validation does not make sense. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 06:25:18 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 29 May 2014 06:25:18 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-433) FieldAccessValidatorEnricher checks access to fields uniformly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-433: ------------------------------- Assignee: Juraj H?ska > FieldAccessValidatorEnricher checks access to fields uniformly > -------------------------------------------------------------- > > Key: ARQGRA-433 > URL: https://issues.jboss.org/browse/ARQGRA-433 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Stefan Miklosovic > Assignee: Juraj H?ska > Priority: Optional > Fix For: 2.0.3.Final > > > I have this test > {code} > @Rule > public ExpectedException expectedException = ExpectedException.none(); > @Test > @InSequence(2) > @ReportMessage("This method should pass.") > public void testWithExpectedExceptionRule() { > expectedException.expect(RuntimeException.class); > throw new RuntimeException("this exception is expected"); > } > {code} > Logger writes this out: > WARNING: Public field 'expectedException' found in org.arquillian.droidium.devconf.AeroGearTestCase. Direct access to fields outside of the declaring class is not allowed. > Apr 01, 2014 11:50:27 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > However that @Rule field _has to be_ public > {quote} > A field must be public, not static, and a subtype of TestRule > {quote} > So in this case validation does not make sense. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 06:29:15 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 29 May 2014 06:29:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-436) @FindByJQuery reference from root does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971563#comment-12971563 ] Juraj H?ska commented on ARQGRA-436: ------------------------------------ Sorry it was my misunderstanding of the implementation & doc issue. I have corrected the docs: https://docs.jboss.org/author/display/ARQGRA2/FindByJQuery+annotation Closing this issues as it is not a bug. > @FindByJQuery reference from root does not work > ----------------------------------------------- > > Key: ARQGRA-436 > URL: https://issues.jboss.org/browse/ARQGRA-436 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > Referencing of the elements annotated with {{@FindByJQuery}} from the root does not work. > It is not working because we are searching for an element with the user submitted locator, e.g. {{html:div:visible}}. We should cut the {{html}}, {{body}} or {{head}} from the user defined selector. > It should be done on [this|https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/findby/ByJQueryImpl.java#L65] line. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 06:29:16 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 29 May 2014 06:29:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-436) @FindByJQuery reference from root does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska resolved ARQGRA-436. -------------------------------- Fix Version/s: (was: 2.0-Tracking) Resolution: Rejected > @FindByJQuery reference from root does not work > ----------------------------------------------- > > Key: ARQGRA-436 > URL: https://issues.jboss.org/browse/ARQGRA-436 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > Referencing of the elements annotated with {{@FindByJQuery}} from the root does not work. > It is not working because we are searching for an element with the user submitted locator, e.g. {{html:div:visible}}. We should cut the {{html}}, {{body}} or {{head}} from the user defined selector. > It should be done on [this|https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/findby/ByJQueryImpl.java#L65] line. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 06:29:16 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 29 May 2014 06:29:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-436) @FindByJQuery reference from root does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed ARQGRA-436. ------------------------------ > @FindByJQuery reference from root does not work > ----------------------------------------------- > > Key: ARQGRA-436 > URL: https://issues.jboss.org/browse/ARQGRA-436 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > Referencing of the elements annotated with {{@FindByJQuery}} from the root does not work. > It is not working because we are searching for an element with the user submitted locator, e.g. {{html:div:visible}}. We should cut the {{html}}, {{body}} or {{head}} from the user defined selector. > It should be done on [this|https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/findby/ByJQueryImpl.java#L65] line. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 07:29:16 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 29 May 2014 07:29:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-436) @FindByJQuery reference from root does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971595#comment-12971595 ] Luk?? Fry? commented on ARQGRA-436: ----------------------------------- Thanks Juraj! > @FindByJQuery reference from root does not work > ----------------------------------------------- > > Key: ARQGRA-436 > URL: https://issues.jboss.org/browse/ARQGRA-436 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > Referencing of the elements annotated with {{@FindByJQuery}} from the root does not work. > It is not working because we are searching for an element with the user submitted locator, e.g. {{html:div:visible}}. We should cut the {{html}}, {{body}} or {{head}} from the user defined selector. > It should be done on [this|https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/findby/ByJQueryImpl.java#L65] line. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 07:35:16 2014 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Thu, 29 May 2014 07:35:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1788) containers - code refactoring In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-1788: --------------------------------- Description: *Code refactoring* - Create an ancestor for managed/remote containers using JMX - Rename class OSGiContainerConfiguration to EmbeddedContainerConfiguration - Process bootstrapCompleteServices in CommonDeployableContainer was: *Code refactoring* - Create an ancestor for managed/remote containers using JMX - Rename class OSGiContainerConfiguration to EmbeddedContainerConfiguration - bootstrapCompleteServices - ... > containers - code refactoring > ----------------------------- > > Key: ARQ-1788 > URL: https://issues.jboss.org/browse/ARQ-1788 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > *Code refactoring* > - Create an ancestor for managed/remote containers using JMX > - Rename class OSGiContainerConfiguration to EmbeddedContainerConfiguration > - Process bootstrapCompleteServices in CommonDeployableContainer -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 10:01:16 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 29 May 2014 10:01:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-433) FieldAccessValidatorEnricher checks access to fields uniformly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-433: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/106 > FieldAccessValidatorEnricher checks access to fields uniformly > -------------------------------------------------------------- > > Key: ARQGRA-433 > URL: https://issues.jboss.org/browse/ARQGRA-433 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Stefan Miklosovic > Assignee: Juraj H?ska > Priority: Optional > Fix For: 2.0.3.Final > > > I have this test > {code} > @Rule > public ExpectedException expectedException = ExpectedException.none(); > @Test > @InSequence(2) > @ReportMessage("This method should pass.") > public void testWithExpectedExceptionRule() { > expectedException.expect(RuntimeException.class); > throw new RuntimeException("this exception is expected"); > } > {code} > Logger writes this out: > WARNING: Public field 'expectedException' found in org.arquillian.droidium.devconf.AeroGearTestCase. Direct access to fields outside of the declaring class is not allowed. > Apr 01, 2014 11:50:27 AM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > However that @Rule field _has to be_ public > {quote} > A field must be public, not static, and a subtype of TestRule > {quote} > So in this case validation does not make sense. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 11:01:17 2014 From: issues at jboss.org (Stefan Bunciak (JIRA)) Date: Thu, 29 May 2014 11:01:17 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1787) Move tests to separate maven module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bunciak updated ARQ-1787: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-osgi/pull/23 > Move tests to separate maven module > ----------------------------------- > > Key: ARQ-1787 > URL: https://issues.jboss.org/browse/ARQ-1787 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Stefan Bunciak > Assignee: Thomas Diesler > > Move tests to separate maven module, so that all container adapter share the same set of tests. Container-specific tests can still reside with the container adapter implementation -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 30 03:39:15 2014 From: issues at jboss.org (Peter Butkovic (JIRA)) Date: Fri, 30 May 2014 03:39:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1789) add tomcat 8 managed and/or remote container adapters In-Reply-To: References: Message-ID: Peter Butkovic created ARQ-1789: ----------------------------------- Summary: add tomcat 8 managed and/or remote container adapters Key: ARQ-1789 URL: https://issues.jboss.org/browse/ARQ-1789 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Peter Butkovic I'd like to see managed and/or remote support for tomcat 8 available in arquillian. As I need to do some container pre-configuration/patching before the run as well as to have clear classpath separation. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 30 03:49:15 2014 From: issues at jboss.org (Peter Butkovic (JIRA)) Date: Fri, 30 May 2014 03:49:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1790) add Jetty managed and/or remote container adapters In-Reply-To: References: Message-ID: Peter Butkovic created ARQ-1790: ----------------------------------- Summary: add Jetty managed and/or remote container adapters Key: ARQ-1790 URL: https://issues.jboss.org/browse/ARQ-1790 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Peter Butkovic I'd like to see managed and/or remote support for jetty available in arquillian. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 30 03:59:16 2014 From: issues at jboss.org (Peter Butkovic (JIRA)) Date: Fri, 30 May 2014 03:59:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1791) add geronimo managed and/or remote addapters In-Reply-To: References: Message-ID: Peter Butkovic created ARQ-1791: ----------------------------------- Summary: add geronimo managed and/or remote addapters Key: ARQ-1791 URL: https://issues.jboss.org/browse/ARQ-1791 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Peter Butkovic -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 30 03:59:16 2014 From: issues at jboss.org (Peter Butkovic (JIRA)) Date: Fri, 30 May 2014 03:59:16 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1791) add geronimo managed and/or remote adapters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Butkovic updated ARQ-1791: -------------------------------- Summary: add geronimo managed and/or remote adapters (was: add geronimo managed and/or remote addapters) > add geronimo managed and/or remote adapters > ------------------------------------------- > > Key: ARQ-1791 > URL: https://issues.jboss.org/browse/ARQ-1791 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Peter Butkovic > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sat May 31 11:53:15 2014 From: issues at jboss.org (Caleb Cushing (JIRA)) Date: Sat, 31 May 2014 11:53:15 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1792) allow deployment with default interfaces instead of static methods In-Reply-To: References: Message-ID: Caleb Cushing created ARQ-1792: ---------------------------------- Summary: allow deployment with default interfaces instead of static methods Key: ARQ-1792 URL: https://issues.jboss.org/browse/ARQ-1792 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Caleb Cushing I'd like to be able to do an {code:java} @Deployment default Archive createDeployment() { ... } {code} and then just apply the interface to my test class -- This message was sent by Atlassian JIRA (v6.2.3#6260)