[arquillian-issues] [JBoss JIRA] (ARQ-1913) ARQ calls test methods with TCCL being set
Aslak Knutsen (JIRA)
issues at jboss.org
Tue Feb 10 06:14:48 EST 2015
[ https://issues.jboss.org/browse/ARQ-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039058#comment-13039058 ]
Aslak Knutsen commented on ARQ-1913:
------------------------------------
Sure, this happens by the JVM.
{code}
public class TCCL {
public static void main(String[] args) {
System.out.println(Thread.currentThread().getContextClassLoader());
}
}
{code}
{code}
sun.misc.Launcher$AppClassLoader at 73d16e93
{code}
> ARQ calls test methods with TCCL being set
> ------------------------------------------
>
> Key: ARQ-1913
> URL: https://issues.jboss.org/browse/ARQ-1913
> Project: Arquillian
> Issue Type: Bug
> Affects Versions: 1.1.6.Final
> Reporter: Thomas Diesler
>
> While integrating Camel in EAP I noticed that @BeforeClass, @Before and @Test methods are being called with the TCCL of the test deployment.
> Camel happens to rely on TCCL, which is of course questionable in a modular environment. As a result it uses the test deployment's CL for resource discovery. Tests pass in the context of ARQ, but would not in a normal usage scenario when TCCL is not set or set to something else.
> IMHO, ARQ should stay out of the business of setting TCCL. Ideally it would even reset the TCCL to null before calling test code. This would provide a portable known base line across various containers.
> Related: https://github.com/wildfly-extras/wildfly-camel/issues/292
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the arquillian-issues
mailing list