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

["Romain Manni-Bucau (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MEECROWAVE-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243497#comment-16243497 ] 

Romain Manni-Bucau commented on MEECROWAVE-77:
----------------------------------------------

Please ensure it is a flag to activate (surely a system property to let it be global) and not on by default to run out of the box in the default surefire env

> Wrap MeecrowaveRule runs in a temporary URLClassLoader to force a unique BeanManager
> ------------------------------------------------------------------------------------
>
>                 Key: MEECROWAVE-77
>                 URL: https://issues.apache.org/jira/browse/MEECROWAVE-77
>             Project: Meecrowave
>          Issue Type: Improvement
>    Affects Versions: 1.1.0
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>             Fix For: 1.2.0
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)