Skip to content

Likely issues of incorrect classloader being used #27134

Closed
@jaminh

Description

@jaminh

I found additional places in the code that look like they likely could cause issues when an alternate classloader is used for a SpringApplication, but I have not actually experienced an issue yet.

if (ClassUtils.isPresent("com.fasterxml.jackson.databind.ObjectMapper", null)) {

return ClassUtils.isPresent("org.eclipse.jetty.alpn.server.ALPNServerConnectionFactory", null);

return ClassUtils.resolveClassName(target, null).isAssignableFrom(type);

Class<?> interpolatorClass = ClassUtils.resolveClassName(fallback, null);

Class<?> initializerClass = ClassUtils.forName(className, ClassUtils.getDefaultClassLoader());

Class<?> clazz = ClassUtils.forName(className, ClassUtils.getDefaultClassLoader());

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: declinedA suggestion or change that we don't feel we should currently apply

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions