September 2011 - arquillian-issues

[JBoss JIRA] Created: (ARQ-593) glassfish-resources.xml (application scoped resources) not loaded with glassfish-remote

by F L (JIRA)

glassfish-resources.xml (application scoped resources) not loaded with glassfish-remote --------------------------------------------------------------------------------------- Key: ARQ-593 URL: https://issues.jboss.org/browse/ARQ-593 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: GlassFish Containers Affects Versions: 1.0.0.Alpha5 Environment: MacOSX Lion, Maven 3, arquillian 1.0.0.Alpha5, arquillian-glassfish-remote-3.1 1.0.0.Alpha5, Glassfish 3.1.1, Java 1.6.0_26 64bits Reporter: F L An EJB Jar with an glassfish-resources.xml references an jdbc/rt JNDI resource. It's correctly read as java:app/jdbc/rt by the EJB package generated by maven but failed with Arquillian/ShrinkWrap targeting glassfish-remote-3.1 ShrinkWrap : JavaArchive archive = ShrinkWrap.create(JavaArchive.class, "Project-ejb-1.0.0-SNAPSHOT.jar") .addPackages(true, "com.company.project.ejb.entities") .addPackages(true, "com.company.project.ejb.model") .addAsManifestResource("META-INF/ejb-jar.xml", ArchivePaths.create("ejb-jar.xml")) .addAsManifestResource("META-INF/sun-ejb-jar.xml", ArchivePaths.create("sun-ejb-jar.xml")) .addAsManifestResource("META-INF/glassfish-resources-test.xml", ArchivePaths.create("glassfish-resources.xml")) .addAsManifestResource("META-INF/persistence-test.xml", ArchivePaths.create("persistence.xml")); persistence.xml : <?xml version="1.0" encoding="UTF-8"?> <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"> <persistence-unit name="RTUnit" transaction-type="JTA"> <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider> <jta-data-source>java:app/jdbc/rt</jta-data-source> <exclude-unlisted-classes>false</exclude-unlisted-classes> </persistence-unit> </persistence> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (ARQAJO-81) support for configurating arquillian.xml during runtime for matrix browser compability jobs

by Juraj Huska (JIRA)

support for configurating arquillian.xml during runtime for matrix browser compability jobs ------------------------------------------------------------------------------------------- Key: ARQAJO-81 URL: https://issues.jboss.org/browse/ARQAJO-81 Project: Arquillian Ajocado Issue Type: Feature Request Components: configuration Affects Versions: 1.0.0.CR1 Reporter: Juraj Huska Assignee: Juraj Huska Fix For: 1.0.0.CR1 Create support for configurating arquillian.xml during runtime for matrix browser compability jobs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
12
0 / 0

[JBoss JIRA] Created: (ARQAJO-93) Update jboss-parent to version 6

by Lukáš Fryč (JIRA)

Update jboss-parent to version 6 -------------------------------- Key: ARQAJO-93 URL: https://issues.jboss.org/browse/ARQAJO-93 Project: Arquillian Ajocado Issue Type: Component Upgrade Components: build Affects Versions: 1.0.0.CR1 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 1.0.0.CR2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (ARQ-312) Add TabLibConfiguration to Jetty plus container

by Dan Allen (JIRA)

Add TabLibConfiguration to Jetty plus container ----------------------------------------------- Key: ARQ-312 URL: https://jira.jboss.org/browse/ARQ-312 Project: Arquillian Issue Type: Bug Components: Jetty Containers Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Assignee: Dan Allen The TagLibConfiguration was left out of the context configurations in the Jetty containers. This was done to speed up loading. However, some frameworks, such as JSF, use TLD files to register listeners. So those are broken as a result. The TagLibConfiguration needs to be added, or the user needs to be allow to configure this support via the container configuration. -- 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, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (ARQ-157) OpenEJB container needs CDI-API to run

by Aslak Knutsen (JIRA)

OpenEJB container needs CDI-API to run -------------------------------------- Key: ARQ-157 URL: https://jira.jboss.org/browse/ARQ-157 Project: Arquillian Issue Type: Bug Components: OpenEJB Containers Affects Versions: 1.0.0.Alpha2 Reporter: Aslak Knutsen Assignee: Andrew Lee Rubinger The OpenEJBTestEnricher needs CDI to run due to import of javax.inject.Inject -- 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, 7 months

4
9
0 / 0

[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, 7 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, 7 months

3
6
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, 7 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, 7 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, 7 months

5
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2011