Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
spring-projects-issues opened this issue Jul 28, 2014 · 0 comments
Assignees
Labels
in: core type: enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Jul 28, 2014

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

@spring-projects-issues spring-projects-issues added type: enhancement in: core labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 4.0.7 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core type: enhancement
Projects
None yet
Development

No branches or pull requests

2 participants