From issues at jboss.org Tue Aug 2 10:40:00 2016 From: issues at jboss.org (Standa Opichal (JIRA)) Date: Tue, 2 Aug 2016 10:40:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2037) Support additional browser capabilities for Chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274043#comment-13274043 ] Standa Opichal commented on ARQ-2037: ------------------------------------- An example I have put to github issues not knowing the primary tracking system is here https://github.com/arquillian/arquillian-extension-drone/issues/64 > Support additional browser capabilities for Chrome > --------------------------------------------------- > > Key: ARQ-2037 > URL: https://issues.jboss.org/browse/ARQ-2037 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.0.0.Final > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.1.0.Final > > > Support additional browser capabilities for Chrome & remove obsolete solution that uses chrome.switches https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/factory/ChromeDriverFactory.java#L86 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Aug 5 14:06:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Fri, 5 Aug 2016 14:06:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2028) The precedence of ScreenshooterLifecycleObserver should be increased In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2028: -------------------------------- Fix Version/s: recorder_1.1.1.Final > The precedence of ScreenshooterLifecycleObserver should be increased > -------------------------------------------------------------------- > > Key: ARQ-2028 > URL: https://issues.jboss.org/browse/ARQ-2028 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Recorder > Affects Versions: recorder_1.1.0.Final > Reporter: Christian Schulz > Fix For: recorder_1.1.1.Final > > > Some people does cleanup after executing a test case which can lead into a blank page or similar, increasing the observer should prevent it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Aug 9 12:42:00 2016 From: issues at jboss.org (Chris Dollar (JIRA)) Date: Tue, 9 Aug 2016 12:42:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1282) TestNG @DataProvider is fully invoked for each record In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276933#comment-13276933 ] Chris Dollar commented on ARQ-1282: ----------------------------------- Thanks for looking into this, Bartosz. Were you able to make any progress? Are there any other workarounds for using TestNG data providers with arquillian? > TestNG @DataProvider is fully invoked for each record > ----------------------------------------------------- > > Key: ARQ-1282 > URL: https://issues.jboss.org/browse/ARQ-1282 > Project: Arquillian > Issue Type: Bug > Components: JBoss AS Containers > Affects Versions: 1.0.3.Final > Reporter: Karel Cemus > Assignee: Bartosz Majsak > Attachments: ArquillianDataProvider.java, FlightServiceTest.java > > > h2. Expected behavior > TestNG defines @DataProvider annotation to allow single method to perform multiple test cases. Provider method annotated with @DataProvider returns an array of arrays, each containing one test case. These parameters are given to the target method as input parameters. By the definition, the total count of performed test by single method is equal to number of test cases in related data provider. > h2. Actual behavior > Using TestNG under Arquillian framework makes this functionality buggy. Although the client (maven, IDE, etc.) thinks, that the total number of invoked test is correct, it is not. When we take a look into server's log, we can see that for each single test case it invoked full set of all test cases. It means, that in the end the amount of performed tests is equal to expected count squared. Such behaviour is not only slow but also in some cases it doesn't work and it makes tests to fail. > h2. Example > {code:java} > @DataProvider > public Object[][] sumProvider() { > return new Object[][]{ > new Object[]{ 0, 0, 0 }, > new Object[]{ 1, 1, 2 }, > new Object[]{ 1, 5, 6 }, > new Object[]{ 5, 1, 6 } > }; > } > {code} > h3. Expected output in server log > {quote} > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > {quote} > h3. Actual output > {quote} > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > Execution of sum: 0 + 0 = 0 > Execution of sum: 1 + 1 = 2 > Execution of sum: 1 + 5 = 6 > Execution of sum: 5 + 1 = 6 > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Aug 18 09:17:01 2016 From: issues at jboss.org (Antonin Stefanutti (JIRA)) Date: Thu, 18 Aug 2016 09:17:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2039) The Weld Arquillian embedded adapter should not load classes that are excluded in beans.xml In-Reply-To: References: Message-ID: Antonin Stefanutti created ARQ-2039: --------------------------------------- Summary: The Weld Arquillian embedded adapter should not load classes that are excluded in beans.xml Key: ARQ-2039 URL: https://issues.jboss.org/browse/ARQ-2039 Project: Arquillian Issue Type: Enhancement Components: Weld Containers Affects Versions: 2.0.0.Beta1 Reporter: Antonin Stefanutti In some use cases, like the Camel CDI extension, some classes are excluded in the beans.xml and may not be in the class path. In that case, that leads to having a {{ClassNotFoundException}} thrown by the adapter that tries to load the bean classes regardless the exclusions from the bean archive descriptor: https://github.com/arquillian/arquillian-container-weld/blob/d8f69bed899ed027ab271ba1c83a07ea51f58eb8/src/main/java/org/jboss/arquillian/container/weld/embedded/Utils.java#L151-L160 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Aug 18 09:21:00 2016 From: issues at jboss.org (Antonin Stefanutti (JIRA)) Date: Thu, 18 Aug 2016 09:21:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2040) The Weld Arquillian adapter should not require JTA dependency in SE environment In-Reply-To: References: Message-ID: Antonin Stefanutti created ARQ-2040: --------------------------------------- Summary: The Weld Arquillian adapter should not require JTA dependency in SE environment Key: ARQ-2040 URL: https://issues.jboss.org/browse/ARQ-2040 Project: Arquillian Issue Type: Feature Request Components: Weld Containers Affects Versions: 2.0.0.Beta1 Reporter: Antonin Stefanutti In a number of use cases, in the SE environment, CDI is used without JPA, while the adapter requires it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Aug 23 14:43:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 23 Aug 2016 14:43:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-358) Should be able to disable specific Enrichers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283009#comment-13283009 ] Bartosz Majsak commented on ARQ-358: ------------------------------------ Is it still something we would like to implement [~aslak]? > Should be able to disable specific Enrichers > -------------------------------------------- > > Key: ARQ-358 > URL: https://issues.jboss.org/browse/ARQ-358 > Project: Arquillian > Issue Type: Feature Request > Components: Runtime Enricher SPI > Affects Versions: 1.0.0.Alpha4 > Reporter: Aslak Knutsen > > In some cases you don't want the other enrichers to jump in and resolve things. > e.g. in a CDI test suite, @EJB injections should only be handled by CDI, not the EJBEnricher as well if CDI fails (that might be the test) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Aug 23 14:45:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 23 Aug 2016 14:45:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-414) Upgrade dependencies of examples (Arqullian 1.0.0.Alpha5, among others) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283012#comment-13283012 ] Bartosz Majsak commented on ARQ-414: ------------------------------------ I'm just wondering what shall we do with the showcase project. It seems rather outdated and most of the extensions have functional tests which are also quite good source of information. Any thoughts [~aslak] [~mjobanek] [~asotobu] > Upgrade dependencies of examples (Arqullian 1.0.0.Alpha5, among others) > ----------------------------------------------------------------------- > > Key: ARQ-414 > URL: https://issues.jboss.org/browse/ARQ-414 > Project: Arquillian > Issue Type: Component Upgrade > Components: Examples/Showcase > Affects Versions: 1.0.0.Alpha5 > Reporter: Hendy Irawan > > Upgrade dependencies, including but not limited to: > - Arquillian 1.0.0.Alpha5 > - JUnit 4.8.2 > - cdi-api 1.0-SP4 > - glassfish 3.1-b41 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Aug 23 14:47:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 23 Aug 2016 14:47:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-244) Create a DeployableContainer integration for Google App Engine In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283013#comment-13283013 ] Bartosz Majsak commented on ARQ-244: ------------------------------------ Spring cleaning - how relevant is this issue after 6y? Can we close it? > Create a DeployableContainer integration for Google App Engine > -------------------------------------------------------------- > > Key: ARQ-244 > URL: https://issues.jboss.org/browse/ARQ-244 > Project: Arquillian > Issue Type: Feature Request > Components: GAE Containers > Reporter: Aslak Knutsen > Assignee: Ales Justin > Priority: Optional > > Arquillian should support start/stop/deploy and undeploy to a Google App Engine container. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Aug 23 14:58:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 23 Aug 2016 14:58:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-638) Option to "clean" the container before running tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283015#comment-13283015 ] Bartosz Majsak commented on ARQ-638: ------------------------------------ I see there are some bits in WildFly about this functionality, but mainly around embedded container. Shall we keep the issue open? /cc [~aslak] > Option to "clean" the container before running tests > ---------------------------------------------------- > > Key: ARQ-638 > URL: https://issues.jboss.org/browse/ARQ-638 > Project: Arquillian > Issue Type: Feature Request > Components: Configuration, JBoss AS Containers > Affects Versions: 1.0.0.CR5 > Reporter: Ondrej Zizka > Assignee: Andrew Rubinger > Priority: Optional > > It would be nice to have an option to have the container cleaned before launching it. > For AS7 as an example, that would mean deleting > * standalone/log > * standalone/data > * standalone/tmp > * standalone/deployments (?) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Aug 23 15:08:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 23 Aug 2016 15:08:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-928) Automation Test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283016#comment-13283016 ] Bartosz Majsak commented on ARQ-928: ------------------------------------ What's this all about? :) > Automation Test > --------------- > > Key: ARQ-928 > URL: https://issues.jboss.org/browse/ARQ-928 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Aug 23 15:23:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 23 Aug 2016 15:23:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1833) Spring Boot Integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283020#comment-13283020 ] Bartosz Majsak commented on ARQ-1833: ------------------------------------- Any progress on it [~jmnarloch]? > Spring Boot Integration > ----------------------- > > Key: ARQ-1833 > URL: https://issues.jboss.org/browse/ARQ-1833 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Spring > Affects Versions: spring_1.0.0.Beta3 > Reporter: Jakub Narloch > Assignee: Jakub Narloch > > Spring Boot is the new hot feature in the Spring world allowing to configure/setup application based on the classpath scaning depedencies or extension, quite similary how the Arquillian load it's extensions. > We could add such support through enable to configure the application context through the SpringApplication similary as the SpringApplicationConfiguration does and by creating spring-boot-arquilian-starter module that would set up proper depedencies in the classpath. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Aug 24 02:30:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 24 Aug 2016 02:30:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-414) Upgrade dependencies of examples (Arqullian 1.0.0.Alpha5, among others) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283133#comment-13283133 ] Matous Jobanek commented on ARQ-414: ------------------------------------ Hi, yeah, I've been looking at this project thinking what to do with it several times recently. I was quite afraid of updating all the sub-projects, because some of them are quite complex and really old so I couldn't imagine how much time it will take. For example, jsf project is related to an extension that is not "alive" any more (jsfunit-arquillian), so what to do with it - move it to some "outdated" directory or remove it at all. On the other hand, I definitely agree that it is good source of information - I know that guys from Fuse QE team used the systemproperties extension in their test-suite recently. I also have my own examples that could be added there: https://github.com/MatousJobanek/examples as well as an example of an extension: https://github.com/MatousJobanek/arquillian-extension-producer Summing my opinion up: I would definitely keep the showcase project I would move completely outdated projects to one "outdated" directory (so do some cleanup) I would try to minimize stack of supported containers to the newest ones If this project was our main place for showing the usages, then it should be referenced from all relevant extensions I can definitely help with updating some of the sub-projects [~manovotn] [~tremes] what do you think about it and helping us with updating the CDI or EJB examples > Upgrade dependencies of examples (Arqullian 1.0.0.Alpha5, among others) > ----------------------------------------------------------------------- > > Key: ARQ-414 > URL: https://issues.jboss.org/browse/ARQ-414 > Project: Arquillian > Issue Type: Component Upgrade > Components: Examples/Showcase > Affects Versions: 1.0.0.Alpha5 > Reporter: Hendy Irawan > > Upgrade dependencies, including but not limited to: > - Arquillian 1.0.0.Alpha5 > - JUnit 4.8.2 > - cdi-api 1.0-SP4 > - glassfish 3.1-b41 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Aug 24 03:08:00 2016 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Wed, 24 Aug 2016 03:08:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-414) Upgrade dependencies of examples (Arqullian 1.0.0.Alpha5, among others) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283147#comment-13283147 ] Matej Novotny commented on ARQ-414: ----------------------------------- Hi, I am putting this into my TODO list. I'll take a look into the CDI/EJB examples soon? and try to help you as much as I can. > Upgrade dependencies of examples (Arqullian 1.0.0.Alpha5, among others) > ----------------------------------------------------------------------- > > Key: ARQ-414 > URL: https://issues.jboss.org/browse/ARQ-414 > Project: Arquillian > Issue Type: Component Upgrade > Components: Examples/Showcase > Affects Versions: 1.0.0.Alpha5 > Reporter: Hendy Irawan > > Upgrade dependencies, including but not limited to: > - Arquillian 1.0.0.Alpha5 > - JUnit 4.8.2 > - cdi-api 1.0-SP4 > - glassfish 3.1-b41 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Aug 25 07:13:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 25 Aug 2016 07:13:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1971) Start WildFly in domain mode via arquillian fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13284148#comment-13284148 ] Bartosz Majsak commented on ARQ-1971: ------------------------------------- Can this issue be closed then [~rhatlapa] [~jamezp]? > Start WildFly in domain mode via arquillian fails > ------------------------------------------------- > > Key: ARQ-1971 > URL: https://issues.jboss.org/browse/ARQ-1971 > Project: Arquillian > Issue Type: Bug > Components: JBoss AS Containers > Reporter: Radim Hatlapatka > Priority: Blocker > > Starting WildFly container in domain mode from arquillian fails with [1]. > Not sure what is causing the issue, it seems that it tries to read-resource in wrong time. If I put sleep before the read-resource is called [2], the server is correctly started (no exception is thrown) > I am using arquillian container for domain managed in version 1.0.1.Final, I have also tried it with latest code from git repository [https://github.com/wildfly/wildfly-arquillian/commit/9467473d8b440ad9d01f5b84ae8373a19cde9249] with the same result. > I tried it using WildFly 10.0.0.Beta1. > [1] > {noformat} > java.lang.RuntimeException: org.jboss.as.arquillian.container.domain.ManagementClient$UnSuccessfulOperationException: undefined > at org.jboss.as.arquillian.container.domain.ManagementClient.lazyLoadRootNode(ManagementClient.java:390) > at org.jboss.as.arquillian.container.domain.ManagementClient.createDomain(ManagementClient.java:115) > at org.jboss.as.arquillian.container.domain.CommonDomainDeployableContainer.start(CommonDomainDeployableContainer.java:131) > at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.client.ContainerEventController.execute(ContainerEventController.java:86) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > 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:497) > 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.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:75) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:115) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: org.jboss.as.arquillian.container.domain.ManagementClient$UnSuccessfulOperationException: undefined > at org.jboss.as.arquillian.container.domain.ManagementClient.checkSuccessful(ManagementClient.java:446) > at org.jboss.as.arquillian.container.domain.ManagementClient.executeForResult(ManagementClient.java:439) > at org.jboss.as.arquillian.container.domain.ManagementClient.readResource(ManagementClient.java:417) > at org.jboss.as.arquillian.container.domain.ManagementClient.readRootNode(ManagementClient.java:294) > at org.jboss.as.arquillian.container.domain.ManagementClient.lazyLoadRootNode(ManagementClient.java:387) > at org.jboss.as.arquillian.container.domain.ManagementClient.createDomain(ManagementClient.java:115) > at org.jboss.as.arquillian.container.domain.CommonDomainDeployableContainer.start(CommonDomainDeployableContainer.java:131) > at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.client.ContainerEventController.execute(ContainerEventController.java:86) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > 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:497) > 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.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:75) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:115) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {noformat} > [2] > `org.jboss.as.arquillian.container.domain.CommonDomainDeployableContainer` > {code} > Domain domain = managementClient.createDomain(containerNameMap); > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Aug 25 07:26:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 25 Aug 2016 07:26:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-517) Remove hack/copied classes introduced to protocol-servlet as part of ARQ-514 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13284157#comment-13284157 ] Bartosz Majsak commented on ARQ-517: ------------------------------------ [~alrubinger] [~aslak] Shall we pay this technical debt? Or is it already sorted out? :) > Remove hack/copied classes introduced to protocol-servlet as part of ARQ-514 > ---------------------------------------------------------------------------- > > Key: ARQ-517 > URL: https://issues.jboss.org/browse/ARQ-517 > Project: Arquillian > Issue Type: Task > Reporter: Andrew Rubinger > > ARQ-514 introduces a series of intentionally-copied code into the ARQ codebase in order to remove a compile-time dependency upon ShrinkWrap Descriptor internals. Once the API for SW-D becomes complete, these copies may be safely removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Aug 25 07:28:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 25 Aug 2016 07:28:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-414) Upgrade dependencies of examples (Arqullian 1.0.0.Alpha5, among others) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13284159#comment-13284159 ] Bartosz Majsak commented on ARQ-414: ------------------------------------ Thanks for your input guys! Shall we move issues to GitHub so that they are closer to the code and use this one as an umbrella? > Upgrade dependencies of examples (Arqullian 1.0.0.Alpha5, among others) > ----------------------------------------------------------------------- > > Key: ARQ-414 > URL: https://issues.jboss.org/browse/ARQ-414 > Project: Arquillian > Issue Type: Component Upgrade > Components: Examples/Showcase > Affects Versions: 1.0.0.Alpha5 > Reporter: Hendy Irawan > > Upgrade dependencies, including but not limited to: > - Arquillian 1.0.0.Alpha5 > - JUnit 4.8.2 > - cdi-api 1.0-SP4 > - glassfish 3.1-b41 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Aug 25 11:29:00 2016 From: issues at jboss.org (James Perkins (JIRA)) Date: Thu, 25 Aug 2016 11:29:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1971) Start WildFly in domain mode via arquillian fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13284366#comment-13284366 ] James Perkins commented on ARQ-1971: ------------------------------------ Yes I believe so [~bmajsak]. If you want, I don't seem to have the permissions to, you can move it to WFARQ and we can mark it as resolved there. > Start WildFly in domain mode via arquillian fails > ------------------------------------------------- > > Key: ARQ-1971 > URL: https://issues.jboss.org/browse/ARQ-1971 > Project: Arquillian > Issue Type: Bug > Components: JBoss AS Containers > Reporter: Radim Hatlapatka > Priority: Blocker > > Starting WildFly container in domain mode from arquillian fails with [1]. > Not sure what is causing the issue, it seems that it tries to read-resource in wrong time. If I put sleep before the read-resource is called [2], the server is correctly started (no exception is thrown) > I am using arquillian container for domain managed in version 1.0.1.Final, I have also tried it with latest code from git repository [https://github.com/wildfly/wildfly-arquillian/commit/9467473d8b440ad9d01f5b84ae8373a19cde9249] with the same result. > I tried it using WildFly 10.0.0.Beta1. > [1] > {noformat} > java.lang.RuntimeException: org.jboss.as.arquillian.container.domain.ManagementClient$UnSuccessfulOperationException: undefined > at org.jboss.as.arquillian.container.domain.ManagementClient.lazyLoadRootNode(ManagementClient.java:390) > at org.jboss.as.arquillian.container.domain.ManagementClient.createDomain(ManagementClient.java:115) > at org.jboss.as.arquillian.container.domain.CommonDomainDeployableContainer.start(CommonDomainDeployableContainer.java:131) > at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.client.ContainerEventController.execute(ContainerEventController.java:86) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > 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:497) > 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.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:75) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:115) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: org.jboss.as.arquillian.container.domain.ManagementClient$UnSuccessfulOperationException: undefined > at org.jboss.as.arquillian.container.domain.ManagementClient.checkSuccessful(ManagementClient.java:446) > at org.jboss.as.arquillian.container.domain.ManagementClient.executeForResult(ManagementClient.java:439) > at org.jboss.as.arquillian.container.domain.ManagementClient.readResource(ManagementClient.java:417) > at org.jboss.as.arquillian.container.domain.ManagementClient.readRootNode(ManagementClient.java:294) > at org.jboss.as.arquillian.container.domain.ManagementClient.lazyLoadRootNode(ManagementClient.java:387) > at org.jboss.as.arquillian.container.domain.ManagementClient.createDomain(ManagementClient.java:115) > at org.jboss.as.arquillian.container.domain.CommonDomainDeployableContainer.start(CommonDomainDeployableContainer.java:131) > at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.client.ContainerEventController.execute(ContainerEventController.java:86) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > 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:497) > 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.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:75) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:115) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {noformat} > [2] > `org.jboss.as.arquillian.container.domain.CommonDomainDeployableContainer` > {code} > Domain domain = managementClient.createDomain(containerNameMap); > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Aug 25 11:38:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Thu, 25 Aug 2016 11:38:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1971) Start WildFly in domain mode via arquillian fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1971: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Start WildFly in domain mode via arquillian fails > ------------------------------------------------- > > Key: ARQ-1971 > URL: https://issues.jboss.org/browse/ARQ-1971 > Project: Arquillian > Issue Type: Bug > Components: JBoss AS Containers > Reporter: Radim Hatlapatka > Priority: Blocker > > Starting WildFly container in domain mode from arquillian fails with [1]. > Not sure what is causing the issue, it seems that it tries to read-resource in wrong time. If I put sleep before the read-resource is called [2], the server is correctly started (no exception is thrown) > I am using arquillian container for domain managed in version 1.0.1.Final, I have also tried it with latest code from git repository [https://github.com/wildfly/wildfly-arquillian/commit/9467473d8b440ad9d01f5b84ae8373a19cde9249] with the same result. > I tried it using WildFly 10.0.0.Beta1. > [1] > {noformat} > java.lang.RuntimeException: org.jboss.as.arquillian.container.domain.ManagementClient$UnSuccessfulOperationException: undefined > at org.jboss.as.arquillian.container.domain.ManagementClient.lazyLoadRootNode(ManagementClient.java:390) > at org.jboss.as.arquillian.container.domain.ManagementClient.createDomain(ManagementClient.java:115) > at org.jboss.as.arquillian.container.domain.CommonDomainDeployableContainer.start(CommonDomainDeployableContainer.java:131) > at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.client.ContainerEventController.execute(ContainerEventController.java:86) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > 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:497) > 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.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:75) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:115) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: org.jboss.as.arquillian.container.domain.ManagementClient$UnSuccessfulOperationException: undefined > at org.jboss.as.arquillian.container.domain.ManagementClient.checkSuccessful(ManagementClient.java:446) > at org.jboss.as.arquillian.container.domain.ManagementClient.executeForResult(ManagementClient.java:439) > at org.jboss.as.arquillian.container.domain.ManagementClient.readResource(ManagementClient.java:417) > at org.jboss.as.arquillian.container.domain.ManagementClient.readRootNode(ManagementClient.java:294) > at org.jboss.as.arquillian.container.domain.ManagementClient.lazyLoadRootNode(ManagementClient.java:387) > at org.jboss.as.arquillian.container.domain.ManagementClient.createDomain(ManagementClient.java:115) > at org.jboss.as.arquillian.container.domain.CommonDomainDeployableContainer.start(CommonDomainDeployableContainer.java:131) > at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.client.ContainerEventController.execute(ContainerEventController.java:86) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > 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:497) > 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.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:75) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:115) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {noformat} > [2] > `org.jboss.as.arquillian.container.domain.CommonDomainDeployableContainer` > {code} > Domain domain = managementClient.createDomain(containerNameMap); > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Aug 29 06:18:00 2016 From: issues at jboss.org (Tomas Remes (JIRA)) Date: Mon, 29 Aug 2016 06:18:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2040) The Weld Arquillian adapter should not require JTA dependency in SE environment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285217#comment-13285217 ] Tomas Remes commented on ARQ-2040: ---------------------------------- [~stefanutti] Hi Antonin, if you really mean JTA then this has been already fixed in https://github.com/arquillian/arquillian-container-weld/issues/25 [~mjobanek] [~bmajsak] I can't assing issue to myself. Can you please update my permissions? > The Weld Arquillian adapter should not require JTA dependency in SE environment > ------------------------------------------------------------------------------- > > Key: ARQ-2040 > URL: https://issues.jboss.org/browse/ARQ-2040 > Project: Arquillian > Issue Type: Feature Request > Components: Weld Containers > Affects Versions: 2.0.0.Beta1 > Reporter: Antonin Stefanutti > > In a number of use cases, in the SE environment, CDI is used without JPA, while the adapter requires it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Aug 29 08:47:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Mon, 29 Aug 2016 08:47:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2040) The Weld Arquillian adapter should not require JTA dependency in SE environment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak reassigned ARQ-2040: ----------------------------------- Assignee: Tomas Remes > The Weld Arquillian adapter should not require JTA dependency in SE environment > ------------------------------------------------------------------------------- > > Key: ARQ-2040 > URL: https://issues.jboss.org/browse/ARQ-2040 > Project: Arquillian > Issue Type: Feature Request > Components: Weld Containers > Affects Versions: 2.0.0.Beta1 > Reporter: Antonin Stefanutti > Assignee: Tomas Remes > > In a number of use cases, in the SE environment, CDI is used without JPA, while the adapter requires it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Aug 29 08:47:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Mon, 29 Aug 2016 08:47:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2040) The Weld Arquillian adapter should not require JTA dependency in SE environment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285313#comment-13285313 ] Bartosz Majsak commented on ARQ-2040: ------------------------------------- [~tremes] Done, from now on you can do it yourself. Thanks for taking care of it! > The Weld Arquillian adapter should not require JTA dependency in SE environment > ------------------------------------------------------------------------------- > > Key: ARQ-2040 > URL: https://issues.jboss.org/browse/ARQ-2040 > Project: Arquillian > Issue Type: Feature Request > Components: Weld Containers > Affects Versions: 2.0.0.Beta1 > Reporter: Antonin Stefanutti > Assignee: Tomas Remes > > In a number of use cases, in the SE environment, CDI is used without JPA, while the adapter requires it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Aug 29 08:52:00 2016 From: issues at jboss.org (Antonin Stefanutti (JIRA)) Date: Mon, 29 Aug 2016 08:52:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2040) The Weld Arquillian adapter should not require JTA dependency in SE environment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285320#comment-13285320 ] Antonin Stefanutti commented on ARQ-2040: ----------------------------------------- [~tremes] yes, I meant JTA. > The Weld Arquillian adapter should not require JTA dependency in SE environment > ------------------------------------------------------------------------------- > > Key: ARQ-2040 > URL: https://issues.jboss.org/browse/ARQ-2040 > Project: Arquillian > Issue Type: Feature Request > Components: Weld Containers > Affects Versions: 2.0.0.Beta1 > Reporter: Antonin Stefanutti > Assignee: Tomas Remes > > In a number of use cases, in the SE environment, CDI is used without JPA, while the adapter requires it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Aug 29 09:22:00 2016 From: issues at jboss.org (Tomas Remes (JIRA)) Date: Mon, 29 Aug 2016 09:22:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2039) The Weld Arquillian embedded adapter should not load classes that are excluded in beans.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Remes reassigned ARQ-2039: -------------------------------- Assignee: Tomas Remes > The Weld Arquillian embedded adapter should not load classes that are excluded in beans.xml > ------------------------------------------------------------------------------------------- > > Key: ARQ-2039 > URL: https://issues.jboss.org/browse/ARQ-2039 > Project: Arquillian > Issue Type: Enhancement > Components: Weld Containers > Affects Versions: 2.0.0.Beta1 > Reporter: Antonin Stefanutti > Assignee: Tomas Remes > > In some use cases, like the Camel CDI extension, some classes are excluded in the beans.xml and may not be in the class path. In that case, that leads to having a {{ClassNotFoundException}} thrown by the adapter that tries to load the bean classes regardless the exclusions from the bean archive descriptor: > https://github.com/arquillian/arquillian-container-weld/blob/d8f69bed899ed027ab271ba1c83a07ea51f58eb8/src/main/java/org/jboss/arquillian/container/weld/embedded/Utils.java#L151-L160 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Aug 29 09:22:00 2016 From: issues at jboss.org (Tomas Remes (JIRA)) Date: Mon, 29 Aug 2016 09:22:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2040) The Weld Arquillian adapter should not require JTA dependency in SE environment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Remes resolved ARQ-2040. ------------------------------ Resolution: Duplicate Issue As mentioned above - fixed with https://github.com/arquillian/arquillian-container-weld/issues/25 [~bmajsak] thanks man! > The Weld Arquillian adapter should not require JTA dependency in SE environment > ------------------------------------------------------------------------------- > > Key: ARQ-2040 > URL: https://issues.jboss.org/browse/ARQ-2040 > Project: Arquillian > Issue Type: Feature Request > Components: Weld Containers > Affects Versions: 2.0.0.Beta1 > Reporter: Antonin Stefanutti > Assignee: Tomas Remes > > In a number of use cases, in the SE environment, CDI is used without JPA, while the adapter requires it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Aug 30 04:54:00 2016 From: issues at jboss.org (Martin Kouba (JIRA)) Date: Tue, 30 Aug 2016 04:54:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2041) Arquillian Weld container should not use org.jboss.weld.servlet.StaticWeldProvider In-Reply-To: References: Message-ID: Martin Kouba created ARQ-2041: --------------------------------- Summary: Arquillian Weld container should not use org.jboss.weld.servlet.StaticWeldProvider Key: ARQ-2041 URL: https://issues.jboss.org/browse/ARQ-2041 Project: Arquillian Issue Type: Bug Components: Weld Containers Reporter: Martin Kouba {{org.jboss.weld.servlet.StaticWeldProvider}} is not used in Weld since 2.2.5.Final. Actually, the class was removed from master branch (Weld 3) and 2.4 branch (soon current stable). The adapter should probably implement its own {{CDIProvider}} to support the simulated environments properly. Affects 2.0.0.Beta2 and 1.0.0.CR9. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Aug 30 04:55:00 2016 From: issues at jboss.org (Tomas Remes (JIRA)) Date: Tue, 30 Aug 2016 04:55:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2041) Arquillian Weld container should not use org.jboss.weld.servlet.StaticWeldProvider In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Remes reassigned ARQ-2041: -------------------------------- Assignee: Tomas Remes > Arquillian Weld container should not use org.jboss.weld.servlet.StaticWeldProvider > ---------------------------------------------------------------------------------- > > Key: ARQ-2041 > URL: https://issues.jboss.org/browse/ARQ-2041 > Project: Arquillian > Issue Type: Bug > Components: Weld Containers > Reporter: Martin Kouba > Assignee: Tomas Remes > > {{org.jboss.weld.servlet.StaticWeldProvider}} is not used in Weld since 2.2.5.Final. Actually, the class was removed from master branch (Weld 3) and 2.4 branch (soon current stable). > The adapter should probably implement its own {{CDIProvider}} to support the simulated environments properly. > Affects 2.0.0.Beta2 and 1.0.0.CR9. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Aug 30 06:48:00 2016 From: issues at jboss.org (Tomas Remes (JIRA)) Date: Tue, 30 Aug 2016 06:48:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2039) The Weld Arquillian embedded adapter should not load classes that are excluded in beans.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Remes updated ARQ-2039: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-weld/pull/29 > The Weld Arquillian embedded adapter should not load classes that are excluded in beans.xml > ------------------------------------------------------------------------------------------- > > Key: ARQ-2039 > URL: https://issues.jboss.org/browse/ARQ-2039 > Project: Arquillian > Issue Type: Enhancement > Components: Weld Containers > Affects Versions: 2.0.0.Beta1 > Reporter: Antonin Stefanutti > Assignee: Tomas Remes > > In some use cases, like the Camel CDI extension, some classes are excluded in the beans.xml and may not be in the class path. In that case, that leads to having a {{ClassNotFoundException}} thrown by the adapter that tries to load the bean classes regardless the exclusions from the bean archive descriptor: > https://github.com/arquillian/arquillian-container-weld/blob/d8f69bed899ed027ab271ba1c83a07ea51f58eb8/src/main/java/org/jboss/arquillian/container/weld/embedded/Utils.java#L151-L160 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Aug 31 07:04:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 31 Aug 2016 07:04:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-414) Upgrade dependencies of examples (Arqullian 1.0.0.Alpha5, among others) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286638#comment-13286638 ] Matous Jobanek commented on ARQ-414: ------------------------------------ For gathering opinions/requirements/proposals: https://docs.google.com/spreadsheets/d/1ORbjQ8-ijYmfKNY2hI7wYzKWnWGClLLvyo7B-36P8Ho/edit?usp=sharing > Upgrade dependencies of examples (Arqullian 1.0.0.Alpha5, among others) > ----------------------------------------------------------------------- > > Key: ARQ-414 > URL: https://issues.jboss.org/browse/ARQ-414 > Project: Arquillian > Issue Type: Component Upgrade > Components: Examples/Showcase > Affects Versions: 1.0.0.Alpha5 > Reporter: Hendy Irawan > > Upgrade dependencies, including but not limited to: > - Arquillian 1.0.0.Alpha5 > - JUnit 4.8.2 > - cdi-api 1.0-SP4 > - glassfish 3.1-b41 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Aug 31 08:28:00 2016 From: issues at jboss.org (Tomas Remes (JIRA)) Date: Wed, 31 Aug 2016 08:28:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2041) Arquillian Weld container should not use org.jboss.weld.servlet.StaticWeldProvider In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Remes updated ARQ-2041: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-weld/pull/30 > Arquillian Weld container should not use org.jboss.weld.servlet.StaticWeldProvider > ---------------------------------------------------------------------------------- > > Key: ARQ-2041 > URL: https://issues.jboss.org/browse/ARQ-2041 > Project: Arquillian > Issue Type: Bug > Components: Weld Containers > Reporter: Martin Kouba > Assignee: Tomas Remes > > {{org.jboss.weld.servlet.StaticWeldProvider}} is not used in Weld since 2.2.5.Final. Actually, the class was removed from master branch (Weld 3) and 2.4 branch (soon current stable). > The adapter should probably implement its own {{CDIProvider}} to support the simulated environments properly. > Affects 2.0.0.Beta2 and 1.0.0.CR9. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Aug 31 08:29:01 2016 From: issues at jboss.org (Rafael Garcia (JIRA)) Date: Wed, 31 Aug 2016 08:29:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-814) Should support injection of EJBs (as CDI Beans) in Weld Embedded In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286709#comment-13286709 ] Rafael Garcia commented on ARQ-814: ----------------------------------- Any chance of this issue getting any progress???? :'( > Should support injection of EJBs (as CDI Beans) in Weld Embedded > ---------------------------------------------------------------- > > Key: ARQ-814 > URL: https://issues.jboss.org/browse/ARQ-814 > Project: Arquillian > Issue Type: Bug > Components: Weld Containers > Affects Versions: weld_1.0.0.CR3 > Reporter: Anthony O. > Assignee: Marko Luk?a > Attachments: EJBTest.java > > > As seen in [this post on the Arquillian forum|https://community.jboss.org/message/723563], we cannot test that simple class as an NPE is thrown from {{org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.MockEjBServices}} which seems to be a copy of Weld code as [Aslak Knutsen|https://community.jboss.org/people/aslak] said. > {code} > @RunWith(Arquillian.class) > public class EJBTest { > @Deployment > public static JavaArchive createTestArchive() { > return ShrinkWrap > .create(JavaArchive.class, "test.jar") > .addAsManifestResource(EmptyAsset.INSTANCE, ArchivePaths.create("beans.xml")); > } > @Stateless > public static class SomeService { > public String someMethod() { > return "test"; > } > } > @Inject > SomeService someService; > @Test > public void testStatelessCall() { > Assert.assertEquals("test", someService.someMethod()); > } > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)