Thanks David, good to work with you too and thanks for the feedback. This is specifically for MP JARs in tomee/lib folder. I've run through app startups with a debugger and it is behaving as intended. Also, actively seen it work well against some apps I have here.
I believe the use case is that MP JAR's should be excluded completely from scanning and their active elements via the tomee.mp.scan setting. This is to prevent risk of interfering with existing Plus/Plume based apps/cdi functionality for people that do not want MP in their Plus/Plume. So could be seen as a backwards compat switch. Secondly, reduces the loading time when tomee.mp.scan = none because previously everything was being scanned all the time. MP adds some start up time for openapi scans, etc. There is still work to be done to make a setting per-context but that is not the scope of this PR. I see JarLocation utility takes a class param. I could just replace the whole previous approach and my approach by simply importing the classes and adding the JarLocations to the scannableUrl. I was just intending to fix the filename dependency but am happy to do that too. It's pretty straight forward. Let me know what you think (modularization may make either approach change anyway). Thanks again! -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
