Hi Jon,
The fix Thomas did is accurate and needed so think we should be fine like
that but I also agree the "pre-fix" implementation of TomEE never caught up
this change.
I guess the fix is to ensure the wrappers we have in TomEE also have this
kind of behavior but handling the cache for TomEE
Hey folks
I've run into an interesting problem on the TomEE-side, running an EAR
file. This seems to end up with 2 injection resolvers for the application:
one for the web part of the application, and a parent for the EAR.
When resolving by type at runtime, with large archives, we've seen a
