Skip to content

AbstractTypeHierarchyTraversingFilter should be more lenient when loading types [SPR-12042] #16658

@spring-projects-issues

Description

@spring-projects-issues

Oliver Drotbohm opened SPR-12042 and commented

When traversing type hierarchies AbstractTypeHierarchyTraversingFilter creates new MetadataReader instances on the way through them. If a supertype of a type inspected is not even on the classpath, this will cause a FileNotFoundException when SimpleMetadataReader wants to access the InputStream of the ClassPathResource.

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

Metadata

Metadata

Assignees

Labels

in: coreIssues in core modules (aop, beans, core, context, expression)type: enhancementA general enhancement

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions