Spring Boot依赖JAR加载主应用类路径资源失败的原因与解决求助

Let's break down exactly why this null pointer exception is happening, then walk through straightforward fixes you can implement right away.

The Core Problem #

When you call SSLSocketFactoryGenerator.class.getResourceAsStream("/subFolder/etc/test.xml") from your client JAR, you're tying resource lookup to the class loader that loaded the SSLSocketFactoryGenerator class. Here's why this fails:

• If your client JAR was packaged with the spring-boot-maven-plugin (making it an executable Spring Boot JAR), its internal structure is nested (classes/resources live inside BOOT-INF/classes). This creates a class loader isolation barrier—your client JAR's class loader can't reach resources in the parent Spring Boot app's classpath.
• Even for regular JARs, Class.getResourceAsStream() prioritizes the client JAR's own resources first, and may not reliably pick up resources from the parent app's src/main/resources directory in some runtime scenarios.

Fixes You Can Implement #

1. Repackage the Client JAR as a Regular JAR (Most Recommended) #

If your client JAR doesn't need to run as a standalone app, ditch the spring-boot-maven-plugin and use Maven's standard maven-jar-plugin instead. This ensures the client JAR's classes are loaded directly by the parent app's class loader, giving it full access to all classpath resources.

Update your client JAR's pom.xml:

<build>
    <plugins>
        <!-- Remove the spring-boot-maven-plugin if it's present -->
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-jar-plugin</artifactId>
            <version>3.3.0</version>
            <configuration>
                <!-- Optional: Add JAR metadata like a main class if needed (not required for dependencies) -->
            </configuration>
        </plugin>
    </plugins>
</build>

2. Use the Context Class Loader to Load Resources #

If you must keep the client JAR as a Spring Boot executable JAR (not ideal for dependencies), use the current thread's context class loader. This is almost always the parent Spring Boot app's class loader, which has access to every resource in the combined classpath.

Replace your existing code with this:

// Note: No leading slash in the path for ClassLoader.getResourceAsStream()
ClassLoader contextLoader = Thread.currentThread().getContextClassLoader();
InputStream fis = contextLoader.getResourceAsStream("subFolder/etc/test.xml");

3. Use Spring's ResourceLoader (Spring-Specific Approach) #

Since you're working in a Spring Boot environment, leveraging Spring's built-in resource handling is the cleanest, most maintainable option. Inject ResourceLoader into your client JAR's component to safely load resources from the parent app's classpath:

import org.springframework.core.io.Resource;
import org.springframework.core.io.ResourceLoader;
import org.springframework.stereotype.Component;
import java.io.IOException;
import java.io.InputStream;

@Component
public class SSLSocketFactoryGenerator {
    private final ResourceLoader resourceLoader;

    // Constructor injection (Spring will auto-wire this for you)
    public SSLSocketFactoryGenerator(ResourceLoader resourceLoader) {
        this.resourceLoader = resourceLoader;
    }

    public void loadTestXml() throws IOException {
        Resource resource = resourceLoader.getResource("classpath:subFolder/etc/test.xml");
        try (InputStream fis = resource.getInputStream()) {
            // Process your input stream here (try-with-resources ensures it's closed properly)
        }
    }
}

4. Validate IDE Configuration (For Development) #

If the issue only pops up in your IDE (not in a packaged JAR), make sure your parent app's src/main/resources directory is marked as a Resources Root:

• In IntelliJ IDEA: Right-click the directory → Mark Directory as → Resources Root
• In Eclipse: Right-click the directory → Build Path → Use as Source Folder

This ensures the IDE includes the directory's contents in the runtime classpath so your client JAR can see them.

Quick Validation Step #

To confirm the resource is actually present in the classpath, add this snippet to your parent app's main class:

public static void main(String[] args) {
    String resourcePath = "subFolder/etc/test.xml";
    URL resource = Thread.currentThread().getContextClassLoader().getResource(resourcePath);
    
    if (resource != null) {
        System.out.println("Resource found at: " + resource.getPath());
    } else {
        System.out.println("Resource is missing from classpath!");
    }
    
    SpringApplication.run(YourParentAppClass.class, args);
}

If this prints "Resource missing", double-check your resource directory structure and IDE/build configuration.

内容的提问来源于stack exchange，提问作者user898465