April 2017 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-2107) ResourceInjectionEnricher doesn't consult the @Resource(lookup = "...") value

by Ladislav Thon (JIRA)

Ladislav Thon created ARQ-2107: ---------------------------------- Summary: ResourceInjectionEnricher doesn't consult the @Resource(lookup = "...") value Key: ARQ-2107 URL: https://issues.jboss.org/browse/ARQ-2107 Project: Arquillian Issue Type: Bug Components: Runtime Enricher SPI Reporter: Ladislav Thon The {{ResourceInjectionEnricher}} supports injecting the test instance fields annotated with {{javax.annotation.Resource}}. However, looking at the {{ResourceInjectionEnricher.getResourceName}} method, it only consults the annotation's {{name}} and {{mappedName}} attributes, falling back to some default afterward. The annotation's {{lookup}} attribute isn't considered at all. This might be because the {{lookup}} attribute was only added in Java EE 6 / Java SE 7, and Arquillian still supports Java 6, but that can be solved with a little bit of reflection. I don't know if this omission was intentional or not, but it could have easily gone unnoticed for a long while, because if CDI is present, the {{CDIInjectionEnricher}} will inject such field. However, CDI doesn't necessarily have to be present -- for example with WildFly Swarm. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-503) Update Arquillian Drone to 2.1.0

by Matous Jobanek (JIRA)

Matous Jobanek created ARQGRA-503: ------------------------------------- Summary: Update Arquillian Drone to 2.1.0 Key: ARQGRA-503 URL: https://issues.jboss.org/browse/ARQGRA-503 Project: Arquillian Graphene Issue Type: Component Upgrade Affects Versions: 2.2.0 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: 2.2.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-502) Update Arquillian-core to 1.1.13.Final

by Matous Jobanek (JIRA)

Matous Jobanek created ARQGRA-502: ------------------------------------- Summary: Update Arquillian-core to 1.1.13.Final Key: ARQGRA-502 URL: https://issues.jboss.org/browse/ARQGRA-502 Project: Arquillian Graphene Issue Type: Component Upgrade Affects Versions: 2.2.0 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: 2.2.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 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 resolved ARQ-814. ----------------------------- Resolution: Won't Fix We don't plan to support EJBs in arquillian-container-weld. I think the proposed pull request is not 100% solution to this problem (as Aslak stated - injection points in EJB class wouldn't work) and IMO brings just possible confusion. This would require to introduce some embedded EJB container integration which wouldn't be so trivial I guess. I think it's still better to use some real EJB container (WFLY, GlassFish, etc) to test such testcases. > 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 (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1875) JaCoCo extension only works for simple use cases

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1875?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak closed ARQ-1875. ------------------------------- Resolution: Won't Fix Solution from JaCoCo team provided as mentioned n the PR comment > JaCoCo extension only works for simple use cases > ------------------------------------------------ > > Key: ARQ-1875 > URL: https://issues.jboss.org/browse/ARQ-1875 > Project: Arquillian > Issue Type: Bug > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha7 > Reporter: John Ament > > In JaCoCo Alpha 7, the tests pass on the build, however the extension itself only works if you have a very small use case. If you have a more robust test that uses database connections, external modules, you get ASM conflicts. > Here's an example output: > {quote} > Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label) > at java.lang.Class.getMethod(Class.java:1773) [rt.jar:1.8.0_20] > at org.apache.cxf.common.util.ReflectionInvokationHandler.invoke(ReflectionInvokationHandler.java:85) > ... 28 more > 13:34:21,040 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "api-webapp.war")]) - failure description: { > "JBAS014671: Failed services" => {"jboss.deployment.unit.\"api-webapp.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"api-webapp.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"api-webapp.war\" > Caused by: javax.xml.ws.WebServiceException: java.lang.reflect.UndeclaredThrowableException > Caused by: java.lang.reflect.UndeclaredThrowableException > Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label)"}, > "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"api-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"api-webapp.war\".beanmanager]"] > {quote} > My jboss-deployment-structure.xml looks like this: > {code} > <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1"> >  > <deployment> > <exclusions> > <module name="org.jboss.resteasy.resteasy-jackson2-provider"/> > </exclusions> > <dependencies> > <module name="com.private" services="import"/> > <module name="org.bouncycastle" services="import"/> > <module name="org.picketlink" services="import"/> > <module name="org.apache.james.mime4j" services="import"/> > <module name="org.hibernate.validator" services="import"/> > <module name="org.hibernate.validator.cdi" services="import"/> > <module name="org.hibernate" services="import"/> > <module name="org.javassist" services="import"/> > <module name="org.apache.commons.http" services="import"/> > <module name="org.apache.commons.email" services="import"/> > <module name="org.apache.commons.lang" services="import"/> > <module name="org.apache.commons.codec" services="import"/> > <module name="org.apache.commons.io" services="import"/> > <module name="org.apache.xerces" services="import"/> > <module name="org.apache.tika" services="import"/> > <module name="org.json" services="import"/> > <module name="org.apache.velocity" services="import"/> > <module name="org.apache.httpcomponents" services="import"/> > <module name="org.apache.log4j" services="import"/> > <module name="org.jboss.logmanager" services="import"/> > <module name="com.google.guava" services="import"/> > <module name="org.codehaus.jackson.jackson-mapper-asl" services="import"/> > <module name="org.codehaus.jackson.jackson-jaxrs" services="import"/> > <module name="org.bouncycastle.bcpg" services="import"/> > <module name="org.jboss.resteasy.resteasy-jackson-provider" services="import"/> > <module name="org.jboss.resteasy.resteasy-multipart-provider" services="import"/> > <module name="org.quartzscheduler" services="import"/> > <module name="org.joda.time" services="import"/> > <module name="org.codehaus.jackson.jackson-core-asl" services="import" /> >  > <module name="org.apache.cxf" services="import"/> > <module name="org.apache.cxf.impl" services="import"/> > <module name="org.picketlink"/> > <module name="org.picketbox"/> > <module name="javax.security.auth.message.api" /> > <module name="javax.security.jacc.api" /> > <module name="org.apache.ws.security"/> > <module name="org.elasticsearch" services="import" meta-inf="import"/> > <module name="org.camunda"/> > </dependencies> > </deployment> > </jboss-deployment-structure> > {code} > Some of these are custom modules, usually just wrapping open source libraries. There's one private one I hid, but it doesn't have any ASM. It seems like hibernate's the culprit here. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1212) Add support for GlassFish 2.x containers

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1212?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak closed ARQ-1212. ------------------------------- Resolution: Out of Date > Add support for GlassFish 2.x containers > ---------------------------------------- > > Key: ARQ-1212 > URL: https://issues.jboss.org/browse/ARQ-1212 > Project: Arquillian > Issue Type: Feature Request > Components: GlassFish Containers > Reporter: Vineet Reynolds > Priority: Minor > > There has been atleast one request to support the GlassFish 2.x container. Since the RESTful admin API used by the current GlassFish adapter is available only since 3.0, we'll need to implement support for 2.x using a different mechanism (possibly using JSR-88 APIs). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1383) Support deployment of container wide resource.xml in GlassFish Managed and Remote

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1383?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak reassigned ARQ-1383: ----------------------------------- Assignee: (was: Bartosz Majsak) > Support deployment of container wide resource.xml in GlassFish Managed and Remote > ---------------------------------------------------------------------------------- > > Key: ARQ-1383 > URL: https://issues.jboss.org/browse/ARQ-1383 > Project: Arquillian > Issue Type: Feature Request > Components: GlassFish Containers > Affects Versions: glassfish_1.0.0.CR4 > Reporter: Aslak Knutsen > Fix For: glassfish_1.0.0.Final > > > As a User I would like to deploy Container wide resources > Given a Reference to a resource.xml file in ContainerConfiguration > When the Container starts up > Then the resource.xml should be deployed > When the Container shuts down > Then the resource.xml should be undeployed > This is similar to how GlassFish Embedded works. > Configuration: https://github.com/arquillian/arquillian-container-glassfish/blob/master/... > Container Impl: https://github.com/arquillian/arquillian-container-glassfish/blob/master/... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1213) Add support for GlassFish 3.0 container

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1213?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak closed ARQ-1213. ------------------------------- Resolution: Out of Date > Add support for GlassFish 3.0 container > --------------------------------------- > > Key: ARQ-1213 > URL: https://issues.jboss.org/browse/ARQ-1213 > Project: Arquillian > Issue Type: Feature Request > Components: GlassFish Containers > Reporter: Vineet Reynolds > Priority: Minor > > The RESTful admin API provided by GlassFish 3.0 does not provide all the REST resources that are currently used by the GlassFish 3.1 adapter. Hence, the 3.1 adapter is not backward compatible with a GlassFish 3.0 instance. > Additionally, the message formats returned by the REST resources of GF 3.0 are different from the ones returned by GF 3.1, hence requiring different parsing semantics. > We must therefore implement a separate adapter to support GlassFish 3.0, that either uses the RESTful Admin APIs available in 3.0, or a supported API like JSR-88. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2066) Support for JUnit 5

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2066?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-2066: -------------------------------- Summary: Support for JUnit 5 (was: Supprt for JUnit 5) > Support for JUnit 5 > ------------------- > > Key: ARQ-2066 > URL: https://issues.jboss.org/browse/ARQ-2066 > Project: Arquillian > Issue Type: Feature Request > Reporter: Tobias Stadler > > The final relase of JUnit 5 is scheduled for Q1 2017. It would be nice if Arquillian would support it then. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2059) Arquillian Governor Jira get Value from properties

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2059?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak commented on ARQ-2059: ------------------------------------- I believe it's not available in the current version. If you are still interested in this feature let us know. > Arquillian Governor Jira get Value from properties > --------------------------------------------------- > > Key: ARQ-2059 > URL: https://issues.jboss.org/browse/ARQ-2059 > Project: Arquillian > Issue Type: Feature Request > Components: Configuration > Environment: In Arquillian Governor Jira, how set I issues from properties fiel in value field?? > Reporter: Rafael Garcia > Priority: Minor > > Hi, > In Arquillian Governor Jira, how set I issues from properties fiel in value field?? > For example: > In properties file > {noformat} > key.issue=PBT-2 > {noformat} > In test.java > @Jira(value = "*{color:red}${key.issue}{color}*") > public void exampleTest() {...} > Thanks in advance -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues April 2017