AbstractTypeHierarchyTraversingFilter should be more lenient when loading types [SPR-12042] #16658
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
type: enhancement
A general enhancement
Milestone
Oliver Drotbohm opened SPR-12042 and commented
When traversing type hierarchies
AbstractTypeHierarchyTraversingFilter
creates newMetadataReader
instances on the way through them. If a supertype of a type inspected is not even on the classpath, this will cause aFileNotFoundException
whenSimpleMetadataReader
wants to access theInputStream
of theClassPathResource
.I suggest to consider these cases equivalent to the core inspected type not being loadable and thus a simple non-match.
Affects: 4.0.6
The text was updated successfully, but these errors were encountered: