The article demonstrates how to let a system expose an interface, accept user‑written JARs that implement it, and hot‑replace the implementation at runtime using either Spring‑managed beans or pure reflection, including bean registration and cleanup.
This article shows how to let users upload a JAR that implements a predefined interface, then hot‑deploy the new implementation at runtime using either Spring annotation‑based registration or plain reflection, including bean registration, removal, and a test harness.
Explore 11 practical Spring Boot bean registration methods—from simple @Component scanning to advanced ImportSelector, FactoryBean, and runtime dynamic registration—detailing code examples, use cases, and configuration steps, enabling developers to choose the optimal approach for flexible, modular applications.
Spring Boot 4, built on Spring Framework 7, introduces elegant API versioning, streamlined Bean registration, null‑safety annotations, simplified HTTP proxy creation, upgraded SPEL, GraalVM native support, Jackson 3.x, newer Servlet/WebSocket versions, and numerous other enhancements, offering developers more powerful and convenient tools.
This article explains how to dynamically load JAR plugins in a Spring Boot application using URLClassLoader, share the class loader with the main context, and register plugin classes as Spring beans both at startup and at runtime, enabling seamless extension without server restarts.
This article explains five core techniques for adding beans to the Spring IoC container—including @Configuration with @Bean, @ComponentScan, various @Import strategies, FactoryBean, and BeanDefinitionRegistryPostProcessor—providing code examples and key considerations for each method.
This article explains various methods to add beans to the Spring IoC container, including @Configuration with @Bean, component scanning, @Import with selectors or registrars, FactoryBean usage, and BeanDefinitionRegistryPostProcessor, providing code examples and detailed explanations for each approach.
This article explains how to use Spring to hot‑load Groovy scripts stored in a database as beans, enabling on‑the‑fly data source access, RPC calls, and dependency injection without restarting the Java application.
