We introduced a couple of new properties to allows additional jars to be added in the DeploymentLoader, so they can be scanned.
This was done here: https://github.com/apache/tomee/commit/021b9ca8d01a78f5b7ee3438f30fd8901ff60d5b <https://github.com/apache/tomee/commit/021b9ca8d01a78f5b7ee3438f30fd8901ff60d5b> What you probably need to do is have your custom classloader to also load the mp specific libraries, so they can be also scanned. Yes, I’ve run into multiple other issues. I’m going to send an email about it, next. I think we can make it, we just need to validate if these changes make sense and if they are right. Thank you, Roberto > On 23 Jan 2019, at 10:55, j4fm <[email protected]> wrote: > > 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
