Unlock Java’s Hidden Power: Mastering SPI and JAR Mechanics

SPI Overview

Java SPI is an API that allows third‑party implementations to extend frameworks. The ServiceLoader reads files under META-INF/services to load implementation classes at runtime.

Using SPI

Define an interface, provide an implementation, create a file named with the interface’s fully‑qualified name in META-INF/services containing the implementation class name, and load it via ServiceLoader.load.

public interface SpiTest { void test(); }
public class SpiTestImpl implements SpiTest { @Override public void test() { System.out.println("test"); } }
ServiceLoader<SpiTest> loader = ServiceLoader.load(SpiTest.class);
SpiTest spi = loader.iterator().next();
spi.test();

Applications of SPI

Common uses include JDBC driver loading, Dubbo extension points, and Spring Boot starter mechanisms where META-INF/spring.factories acts as a variant of SPI.

JAR Mechanism

A JAR’s META-INF/MANIFEST.MF defines metadata such as Manifest-Version, Main-Class, and class‑path. Commands like jar -cvf, jar -tvf, jar -xvf create, list, and extract JAR contents.

Class Loading Process

Java uses three class loaders: BootstrapClassLoader, ExtClassLoader, and AppClassLoader, following the parent‑delegation model. Classes are loaded on first use, via bytecode instructions, reflection, or when the JVM starts the main class.

Tomcat Class Loaders

Tomcat defines several loaders (Common, Catalina, Shared, WebApp, JSP) that deviate from strict parent delegation to isolate web applications.

Spring Boot JAR Structure

Spring Boot packages contain nested JARs and a launcher (JarLauncher, Launcher) that can load classes from embedded JARs using the stream mechanism.

Custom Class Loader

By extending ClassLoader and overriding findClass, developers can load classes from custom locations, then instantiate them via reflection.

Conclusion

The article demystifies SPI and JAR mechanisms, helping readers understand the “black magic” behind Spring Boot and related frameworks.