Skip to content

Perform explicit class checks in ReactiveAdapterRegistry [SPR-17000] #21538

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.

Sign up for GitHub

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

Jump to bottom
Closed
spring-projects-issues opened this issue Jul 3, 2018 · 0 comments
Closed

Perform explicit class checks in ReactiveAdapterRegistry [SPR-17000] #21538

spring-projects-issues opened this issue Jul 3, 2018 · 0 comments
Assignees
@sdeleuze
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Milestone
5.1 RC1

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Jul 3, 2018 •
edited
Loading

Sébastien Deleuze opened SPR-17000 and commented

In order to allow Spring Framework applications running as GraalVM native images, we should perform explicit class checks instead of catching Throwable in order to avoid UnsupportedFeatureError: Unresolved element found errors.

Issue Links:

Referenced from: commits 9b7a492, dcbaece
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sdeleuze sdeleuze

Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Projects
None yet
Milestone
5.1 RC1
Development

No branches or pull requests
2 participants
@sdeleuze @spring-projects-issues