October 2011 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-308) Patch to support OpenEJB 3.2 API change

by Dan Allen (JIRA)

Patch to support OpenEJB 3.2 API change --------------------------------------- Key: ARQ-308 URL: https://jira.jboss.org/browse/ARQ-308 Project: Arquillian Issue Type: Patch Components: OpenEJB Containers Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Fix For: 1.0.0.Beta1 The Arquillian Embedded OpenEJB 3.1 container adapter works with OpenEJB 3.2 with the exception of one field reference. The public field AppInfo#jarPath was renamed to AppInfo#path. Attached is a patch which will determine the correct field name through reflection so both APIs can be supported. Keep in mind that OpenEJB 3.2 is still unreleased, so this is an enabling change (enables people to use it), and may be unnecessary if we find out why the field name was change. Or, perhaps, this issue will lead to an upstream change that makes this patch unnecessary. Either way, it would be nice to be able to use OpenEJB 3.2 as it supports JPA 2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
11
0 / 0

[JBoss JIRA] Created: (ARQ-279) Weld SE should support nested Jars

by Aslak Knutsen (JIRA)

Weld SE should support nested Jars ---------------------------------- Key: ARQ-279 URL: https://jira.jboss.org/browse/ARQ-279 Project: Arquillian Issue Type: Feature Request Components: Weld Containers Reporter: Aslak Knutsen In any larger app, Libraries are needed. Weld SE container should support the notion of Nested JavaArchives in the @Deployment. Should work about the same as for Weld EE, scan through the Archives recursively looking for class/beans.xml/extensions etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
6
0 / 0

[JBoss JIRA] (ARQ-629) Tomcat6-managed container: running 39 testcase classes with n test methods each on hudson result in a crash on the 10th deployment

by Geoffrey De Smet (Created) (JIRA)

Tomcat6-managed container: running 39 testcase classes with n test methods each on hudson result in a crash on the 10th deployment ---------------------------------------------------------------------------------------------------------------------------------- Key: ARQ-629 URL: https://issues.jboss.org/browse/ARQ-629 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Tomcat Containers Affects Versions: 1.0.0.CR4 Reporter: Geoffrey De Smet Priority: Minor So it deploys 39 times, and after about the 10th or so it crashes because of perm gen space IIRC. My build was here, but on build 5 or so I switched it from tomcat to jboss7-managed: https://hudson.qa.jboss.com/hudson/view/Drools%20jBPM/job/guvnor-ge0ffrey... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

5
4
0 / 0

[JBoss JIRA] Created: (ARQ-286) Should support JUnit @Rules

by Aslak Knutsen (JIRA)

Should support JUnit @Rules --------------------------- Key: ARQ-286 URL: https://jira.jboss.org/browse/ARQ-286 Project: Arquillian Issue Type: Feature Request Components: Test Harness Integration Reporter: Aslak Knutsen Fix For: 1.0.0.Beta1 Using the JUnit feature @Rule becomes a problem when running against Remote servers since the @Rule is executed both on the Client and Container side. It works fine in Embedded Containers since the Test is executed in the same VM, but if the Rule is dependent on Container features, the @Test will fail. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (ARQ-53) Research possibility of redirecting log statements back to client

by Aslak Knutsen (JIRA)

Research possibility of redirecting log statements back to client ----------------------------------------------------------------- Key: ARQ-53 URL: https://jira.jboss.org/jira/browse/ARQ-53 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen When running in remote containers all system.out/err and log statements done in the testcase are written to the server log. It should be possible to catch this and redirect them back to the client.. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
7
0 / 0

[JBoss JIRA] Created: (ARQ-525) Tests fails when META-INF/validation.xml exist

by Liu Jianhong (JIRA)

Tests fails when META-INF/validation.xml exist ---------------------------------------------- Key: ARQ-525 URL: https://issues.jboss.org/browse/ARQ-525 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: GlassFish Containers Affects Versions: glassfish_1.0.0.CR1 Environment: arquillian-junit-container:1.0.0.CR2 arquillian-glassfish-embedded-3.1:1.0.0.CR1 glassfish-embedded-all:3.1 Reporter: Liu Jianhong Priority: Critical Tests success when no META-INF/validation.xml exist，when META-INF/validation.xml exist，produce the following information: 2011-7-25 6:49:06 org.jboss.arquillian.container.impl.client.container.ContainerRegistryCreator getActivatedConfiguration 信息: Could not read active container configuration: null 2011-7-25 6:49:07 com.sun.enterprise.v3.server.CommonClassLoaderServiceImpl findDerbyClient 信息: Cannot find javadb client jar file, derby jdbc driver will not be available by default. 2011-7-25 6:49:07 org.hibernate.validator.util.Version <clinit> 信息: Hibernate Validator null 2011-7-25 6:49:07 org.hibernate.validator.engine.resolver.DefaultTraversableResolver detectJPA 信息: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver. 2011-7-25 6:49:07 org.hibernate.validator.xml.ValidationXmlParser getValidationConfig 信息: META-INF/validation.xml found. 2011-7-25 6:49:07 org.hibernate.validator.xml.ValidationXmlParser getValidationConfig 严重: Error parsing validation.xml: null -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

5
11
0 / 0

[JBoss JIRA] Created: (ARQ-264) Create a DeployableContainer integration for remote WebSphere

by Aslak Knutsen (JIRA)

Create a DeployableContainer integration for remote WebSphere ------------------------------------------------------------- Key: ARQ-264 URL: https://jira.jboss.org/browse/ARQ-264 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen Priority: Minor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
16
0 / 0

[JBoss JIRA] Created: (ARQ-560) Support for collection of code coverage data of locally executed tests

by Vineet Reynolds (JIRA)

Support for collection of code coverage data of locally executed tests ---------------------------------------------------------------------- Key: ARQ-560 URL: https://issues.jboss.org/browse/ARQ-560 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Jacoco Affects Versions: 1.0.0.Alpha1 Reporter: Vineet Reynolds The Arquillian Jacoco extension v1.0.0.Alpha1 currently does not gather code coverage data, when the tests are executed locally (using @RunAsClient) against a remote deployment (created using @Deployment). The preferred behavior would be to allow for data to be gathered in remote deployments, and sent to the local client, so that the jacoco.exec file is created, just as it is done for in-container tests. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (ARQ-616) JBoss 7 embedded container (jboss-as-arquillian-container-embedded)

by Geoffrey De Smet (JIRA)

JBoss 7 embedded container (jboss-as-arquillian-container-embedded) ------------------------------------------------------------------- Key: ARQ-616 URL: https://issues.jboss.org/browse/ARQ-616 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBoss Containers Reporter: Geoffrey De Smet Priority: Critical There is no recent jboss-as-arquillian-container-embedded release. I've heard it's being worked on, but I didn't find an issue. So I created this one, to be able to track it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (ARQ-617) Make Tomcat 6 and Jetty 6 and 7 specific configuration obsolete

by Geoffrey De Smet (JIRA)

Make Tomcat 6 and Jetty 6 and 7 specific configuration obsolete --------------------------------------------------------------- Key: ARQ-617 URL: https://issues.jboss.org/browse/ARQ-617 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet According to the documentation: http://docs.jboss.org/weld/reference/1.1.0.Final/en-US/html_single/#d0e5286 We have to add extra configuration files to deploy to certain appservers and certain versions. But the existence of those files can sometimes create issues on other appservers. For example, jetty 6 needs an WEB-INF/jetty-env.xml file (and Jetty 7 needs another version of that file). "Maven profiles" are not a solution, see WELD-984. Since weld-servlet's bootstrap actually detects what appserver and what version is in play, it should be thoroughly investigated if weld can't do that for us and only configure the content of those extra files if the correct appserver/version is being used. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues October 2011