September 2016 - arquillian-issues

[JBoss JIRA] (ARQ-2043) Upgrade Selenium to 2.53.1

by Matous Jobanek (JIRA)

Matous Jobanek created ARQ-2043: ----------------------------------- Summary: Upgrade Selenium to 2.53.1 Key: ARQ-2043 URL: https://issues.jboss.org/browse/ARQ-2043 Project: Arquillian Issue Type: Component Upgrade Components: Extension - Drone Affects Versions: drone_2.0.0.Final Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: drone_2.0.1.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2042) Bridge methods treated as observer methods in JDK8

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2042?page=com.atlassian.jira.plugin.s... ] Work on ARQ-2042 started by Bartosz Majsak. ------------------------------------------- > Bridge methods treated as observer methods in JDK8 > -------------------------------------------------- > > Key: ARQ-2042 > URL: https://issues.jboss.org/browse/ARQ-2042 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Affects Versions: 1.1.11.Final > Environment: JDK 8 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > > The Java Compiler was changed with regards to synthetic methods and Annotations. > Before, annotations on parameters of the original generic methods were NOT copied on to the synthetic bridge method. > Now, the original annotation is present in 2 places: the generic method (with the actual type replaced in place of the type parameter) and the synthetic method. > When it comes to the @Observes annotation, Arquillian will try to call the synthetic method (which receives Object) with any kind of event, leading to a ClassCastException (because the bridge method does an implicit cast to the actual type and calls the real generic method) > The commit makes Arquillian ignore synthetic methods when searching for potential event listeners. > Discussion: > http://discuss.arquillian.org/t/moving-from-persistence-impl-to-persisten... > > See following bugs for details: > > * http://bugs.java.com/view_bug.do?bug_id=6695379 > * http://bugs.java.com/view_bug.do?bug_id=8072365 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2042) Bridge methods treated as observer methods in JDK8

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2042?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-2042: -------------------------------- Description: The Java Compiler was changed with regards to synthetic methods and Annotations. Before, annotations on parameters of the original generic methods were NOT copied on to the synthetic bridge method. Now, the original annotation is present in 2 places: the generic method (with the actual type replaced in place of the type parameter) and the synthetic method. When it comes to the @Observes annotation, Arquillian will try to call the synthetic method (which receives Object) with any kind of event, leading to a ClassCastException (because the bridge method does an implicit cast to the actual type and calls the real generic method) The commit makes Arquillian ignore synthetic methods when searching for potential event listeners. Discussion: http://discuss.arquillian.org/t/moving-from-persistence-impl-to-persisten... See following bugs for details: * http://bugs.java.com/view_bug.do?bug_id=6695379 * http://bugs.java.com/view_bug.do?bug_id=8072365 was: The Java Compiler was changed with regards to synthetic methods and Annotations. Before, annotations on parameters of the original generic methods were NOT copied on to the synthetic bridge method. Now, the original annotation is present in 2 places: the generic method (with the actual type replaced in place of the type parameter) and the synthetic method. When it comes to the @Observes annotation, Arquillian will try to call the synthetic method (which receives Object) with any kind of event, leading to a ClassCastException (because the bridge method does an implicit cast to the actual type and calls the real generic method) The commit makes Arquillian ignore synthetic methods when searching for potential event listeners. > Bridge methods treated as observer methods in JDK8 > -------------------------------------------------- > > Key: ARQ-2042 > URL: https://issues.jboss.org/browse/ARQ-2042 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Affects Versions: 1.1.11.Final > Environment: JDK 8 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > > The Java Compiler was changed with regards to synthetic methods and Annotations. > Before, annotations on parameters of the original generic methods were NOT copied on to the synthetic bridge method. > Now, the original annotation is present in 2 places: the generic method (with the actual type replaced in place of the type parameter) and the synthetic method. > When it comes to the @Observes annotation, Arquillian will try to call the synthetic method (which receives Object) with any kind of event, leading to a ClassCastException (because the bridge method does an implicit cast to the actual type and calls the real generic method) > The commit makes Arquillian ignore synthetic methods when searching for potential event listeners. > Discussion: > http://discuss.arquillian.org/t/moving-from-persistence-impl-to-persisten... > > See following bugs for details: > > * http://bugs.java.com/view_bug.do?bug_id=6695379 > * http://bugs.java.com/view_bug.do?bug_id=8072365 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2042) Bridge methods treated as observer methods in JDK8

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2042?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak reassigned ARQ-2042: ----------------------------------- Assignee: Bartosz Majsak > Bridge methods treated as observer methods in JDK8 > -------------------------------------------------- > > Key: ARQ-2042 > URL: https://issues.jboss.org/browse/ARQ-2042 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Affects Versions: 1.1.11.Final > Environment: JDK 8 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > > The Java Compiler was changed with regards to synthetic methods and Annotations. > Before, annotations on parameters of the original generic methods were NOT copied on to the synthetic bridge method. > Now, the original annotation is present in 2 places: the generic method (with the actual type replaced in place of the type parameter) and the synthetic method. > When it comes to the @Observes annotation, Arquillian will try to call the synthetic method (which receives Object) with any kind of event, leading to a ClassCastException (because the bridge method does an implicit cast to the actual type and calls the real generic method) > The commit makes Arquillian ignore synthetic methods when searching for potential event listeners. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2042) Bridge methods treated as observer methods in JDK8

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-2042: ----------------------------------- Summary: Bridge methods treated as observer methods in JDK8 Key: ARQ-2042 URL: https://issues.jboss.org/browse/ARQ-2042 Project: Arquillian Issue Type: Bug Components: Base Implementation Affects Versions: 1.1.11.Final Environment: JDK 8 Reporter: Bartosz Majsak The Java Compiler was changed with regards to synthetic methods and Annotations. Before, annotations on parameters of the original generic methods were NOT copied on to the synthetic bridge method. Now, the original annotation is present in 2 places: the generic method (with the actual type replaced in place of the type parameter) and the synthetic method. When it comes to the @Observes annotation, Arquillian will try to call the synthetic method (which receives Object) with any kind of event, leading to a ClassCastException (because the bridge method does an implicit cast to the actual type and calls the real generic method) The commit makes Arquillian ignore synthetic methods when searching for potential event listeners. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2027) JDK 8 with wildfly failing for integration tests

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2027?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak commented on ARQ-2027: ------------------------------------- It's the issue with bridge methods being treated as part of the observer, as explained here: http://discuss.arquillian.org/t/moving-from-persistence-impl-to-persisten... > JDK 8 with wildfly failing for integration tests > ------------------------------------------------ > > Key: ARQ-2027 > URL: https://issues.jboss.org/browse/ARQ-2027 > Project: Arquillian > Issue Type: Bug > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > > More details on discuss > http://discuss.arquillian.org/t/help-running-arquillian-persistence-int-t... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-358) Should be able to disable specific Enrichers

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-358?page=com.atlassian.jira.plugin.sy... ] Matous Jobanek commented on ARQ-358: ------------------------------------ I think that this is possible even with the current implementation - creating a dummy enricher and overwriting that one you want to disable with this new one. But I agree that this can be a little bit clumsy. > 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)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-814) Should support injection of EJBs (as CDI Beans) in Weld Embedded

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/ARQ-814?page=com.atlassian.jira.plugin.sy... ] Tomas Remes edited comment on ARQ-814 at 9/2/16 9:25 AM: --------------------------------------------------------- [~mjobanek] Someone needs to take a look at the ancient PR and rebase it to current master then we can likely proceeed but as stated by Aslak it seems that the PR is not working correctly in all cases. Hopefully I can take a look sometimes.... was (Author: tremes): [~mjobanek] Someone needs to take a look at the ancient PR and rebase it to current master then we can likely proceeed. > 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)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-814) Should support injection of EJBs (as CDI Beans) in Weld Embedded

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/ARQ-814?page=com.atlassian.jira.plugin.sy... ] Tomas Remes commented on ARQ-814: --------------------------------- [~mjobanek] Someone needs to take a look at the ancient PR and rebase it to current master then we can likely proceeed. > 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)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-814) Should support injection of EJBs (as CDI Beans) in Weld Embedded

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-814?page=com.atlassian.jira.plugin.sy... ] Matous Jobanek commented on ARQ-814: ------------------------------------ WDYT [~tremes]? > 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)

8 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2016