[MEECROWAVE-77] Wrap MeecrowaveRule runs in a temporary URLClassLoader to force a unique BeanManager

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.0
• Fix Version/s: 1.2.0
• Assignee: Mark Struberg
• Reporter: Mark Struberg
• Created: 08/Nov/17 07:57
• Updated: 25/Dec/17 10:37
• Resolved: 09/Nov/17 18:07

Description

Meecrowave uses standard OWB which binds the instance to the 'current' ClassLoader (TCCL mostly).

In unit tests this is almost always the same, the standard CL from the test classpath.

If one wants to run multiple Meecrowave tests in parallel or a MonoMeecrowave + MeecrowaveRule tests in the same suite, then the information in the BeanManager might get mixed up.

To solve this issue we should provide a distinct URLClassLoader (delegating to the standard CL as parent) for each test class.