Loading...

XML

Word

Printable

Type: Feature Request
Resolution: Done
Priority: Major
Fix Version/s: 9.0.0.CR2, 10.0.0.Alpha1
Affects Version/s: None
Component/s: Test Suite
Labels:
None

Git Pull Request:
https://github.com/wildfly/wildfly-arquillian/pull/15

In WildFly it is considerred intended behaviour that test code gets called with the TCCL set to the test deployment. 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)

For Camel integration this behaviour is not acceptable.

CrossLink: https://github.com/wildfly-extras/wildfly-camel/issues/340

causes

WFARQ-153 JUnit 5 does not work with the jmx-as7 protocol if enableThreadContextClassLoader is set to false

Open

is blocked by

ARQ-1927 Make use of TCCL in ARQ ManagedContainer configurable

Resolved

is incorporated by

WFLY-4623 Upgrade WildFly Arquillian from 1.0.0.Alpha5 to 1.0.0.CR1

Closed

relates to

WFLY-4335 ArquillianService incorrectly sets TCCL

Closed

Assignee:: Thomas Diesler

Reporter:: Thomas Diesler

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2015/02/27 3:42 AM

Updated:: 2024/01/12 1:46 AM

Resolved:: 2015/05/17 10:26 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates