Issue #1800 - Fix generic class loading #1831
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I found out that for generic classes declared in nested jars of a Spring Boot application a class not found exception is thrown from the ClassReader constructor. The root cause was that the class ClassReader from ASM uses ClassLoader.getSystemResourceAsStream() method, which doesn't see the class file. A possible fix would be to load the class bytes independently and provide them to ClassReader.