[JBoss JIRA] (ARQ-1914) Arquillian embedded tests do not support @Convert/@Converter (JPA 2.1)
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1914?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen commented on ARQ-1914:
------------------------------------
The file it's complaining about is beans.xml. You posted persistence.xml.
> Arquillian embedded tests do not support @Convert/@Converter (JPA 2.1)
> ----------------------------------------------------------------------
>
> Key: ARQ-1914
> URL: https://issues.jboss.org/browse/ARQ-1914
> Project: Arquillian
> Issue Type: Bug
> Components: GlassFish Containers
> Affects Versions: 1.1.6.Final
> Reporter: Constantin Weißer
>
> The arquillian glassfish embedded container (in the newest version 1.0.0.CR4) does simply ignore @Convert annotations (JPA 2.1) which leads to errors when running tests that use the persistence layer.
> The error output contains
> Internal Exception: Exception [EclipseLink-7155] (Eclipse Persistence Services - 2.2.0.v20110202-r8913)
> which would explain, why it does not work. JPA 2.1 features are not implemented in EclipseLink 2.2.0. Why does arquillian-glassfish-embedded use such an outdated version of the persistence service?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 9 months
[JBoss JIRA] (ARQ-1914) Arquillian embedded tests do not support @Convert/@Converter (JPA 2.1)
by Constantin Weißer (JIRA)
[ https://issues.jboss.org/browse/ARQ-1914?page=com.atlassian.jira.plugin.s... ]
Constantin Weißer commented on ARQ-1914:
----------------------------------------
Hi Aslak,
thanks for your quick response.
I changed this setting to 4.1. This does resolve the prior mentioned error but results in this:
SEVERE: Exception while loading the app : WELD-001202 Error parsing jar:file:/tmp/gfembed4868208385859575508tmp/applications/test/WEB-INF/lib/test.jar!/META-INF/beans.xml
org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 8; XML document structures must start and end within the same entity.
The respective file in the archive is:
https://gist.github.com/anonymous/703394b1d59dde7431a5
I ran a XML validator on it and it does not report any errors.
> Arquillian embedded tests do not support @Convert/@Converter (JPA 2.1)
> ----------------------------------------------------------------------
>
> Key: ARQ-1914
> URL: https://issues.jboss.org/browse/ARQ-1914
> Project: Arquillian
> Issue Type: Bug
> Components: GlassFish Containers
> Affects Versions: 1.1.6.Final
> Reporter: Constantin Weißer
>
> The arquillian glassfish embedded container (in the newest version 1.0.0.CR4) does simply ignore @Convert annotations (JPA 2.1) which leads to errors when running tests that use the persistence layer.
> The error output contains
> Internal Exception: Exception [EclipseLink-7155] (Eclipse Persistence Services - 2.2.0.v20110202-r8913)
> which would explain, why it does not work. JPA 2.1 features are not implemented in EclipseLink 2.2.0. Why does arquillian-glassfish-embedded use such an outdated version of the persistence service?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 9 months
[JBoss JIRA] (ARQ-1818) JUnit @Before/After phase is called after/before Arquillian's Before/After phase
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1818?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen closed ARQ-1818.
------------------------------
> JUnit @Before/After phase is called after/before Arquillian's Before/After phase
> --------------------------------------------------------------------------------
>
> Key: ARQ-1818
> URL: https://issues.jboss.org/browse/ARQ-1818
> Project: Arquillian
> Issue Type: Bug
> Components: Test Harness Integration
> Affects Versions: 1.1.5.Final, 1.1.6.Final
> Reporter: Aslak Knutsen
> Assignee: Aslak Knutsen
> Priority: Blocker
> Fix For: 1.1.7.Final
>
>
> In < 1.1.5.Final JUnit's @Before and @After was called by Arquillian as part of Arquillian's Before and After phases. This changed by accident during the JUnit Rule support rewrite and @Before is now called after Arquillian's Before and @After phase is now called Before Arquillian's After.
> This break down APIs like Deployer/ContainerController as non of the Suite/Class/Test Contexts are active at that point.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 9 months
[JBoss JIRA] (ARQ-1880) Arquillian core relies on TCCL to load infra
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1880?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen closed ARQ-1880.
------------------------------
> Arquillian core relies on TCCL to load infra
> --------------------------------------------
>
> Key: ARQ-1880
> URL: https://issues.jboss.org/browse/ARQ-1880
> Project: Arquillian
> Issue Type: Bug
> Affects Versions: 1.1.2.Final
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Fix For: 1.1.7.Final
>
>
> While testing FSW product stuff it turns out that test code is executed with a TCCL from the ARQ bundle. If ARQ does not set a TCCL we get
> {code}
> Caused by: java.lang.ClassNotFoundException: org/jboss/arquillian/test/impl/EventTestRunnerAdaptor
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:270)
> at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:105)
> at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:97)
> at org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder.build(TestRunnerAdaptorBuilder.java:52)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:93)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:138)
> at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65)
> at org.jboss.arquillian.osgi.JUnitBundleTestRunner.execute(JUnitBundleTestRunner.java:34)
> {code}
> Having a TCCL set is highly problematic in OSGi because it bypasses al user defined wiring rules. When test code calls into API that uses TCCL, that API will try to load types from the ARQ Bundle classloader, which of course has no visibility to the requested types/resources.
> The ARQ infra should ideally not have to depend on TCCL for loading its own types. Second best would be to reset the TCCL after all infra stuff is done and before the call into the test case.
> The TCCL association is part of the public API. From the perspective of the test case, it needs to be defined and ideally be guaranteed to be null.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 9 months