Okay, so digging into this loader, there is this line: SystemInstance.get().setComponent(ParentClassLoaderFinder.class, fallback -> MyClassLoader._getOrCreateInstance(parent));
Commenting it out seems to make it play nicely with MP but brakes the class loading of the webapps when openejb's scanning annotations. So am currently looking at other solutions to make both work. I think this is something that can be solved but am suspecting there is a chance there is a bug with openejb not using the correct class loaders for the webapps. Trying some things. Are you still finding issues with MP in Plus with the test cases failing? Is there anything else blocking having MP in Plus for M2 release? I don't want to become a blocker for that, will know today if this class loading issue can be solved or a bug. It would be really great if M2 could have MP in Plus but understand how tight it is. -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
