[jboss-jira] [JBoss JIRA] (WFLY-4335) ArquillianService incorrectly sets TCCL

[Thomas Diesler (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044579#comment-13044579 ] 

Thomas Diesler commented on WFLY-4335:
--------------------------------------

I can't see how this can be true for all threads that execute a given functionality. IMHO the guarantees are weak. It may be true that all requests coming in on an undertow endpoint can be mapped to a war deployment, but is this generally true for all?

IMHO this shadows potential problems when the functionality under test is not called from an ARQ test case (i.e. from an normal javaee endpoint)

Anyway, we can probably make this configurable (see WFLY-4392) so the current behaviour does not change for the wildfly tests.

> ArquillianService incorrectly sets TCCL
> ---------------------------------------
>
>                 Key: WFLY-4335
>                 URL: https://issues.jboss.org/browse/WFLY-4335
>             Project: WildFly
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 8.2.0.Final
>            Reporter: Thomas Diesler
>            Assignee: Thomas Diesler
>
> While integrating Camel in WildFly 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.
> This shadows potential problems when TCCL is not set or set to something else.
> Related: https://github.com/wildfly-extras/wildfly-camel/issues/292



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)