]
Thomas Diesler commented on ARQ-1913:
-------------------------------------
This is a critical bug for us, because it effectively prevents meaningful Camel testing. I
see if I can provide a patch ...
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 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.