asmhatreandClaude Opus 5
86246dc860
configuration-properties/ @ConfigurationProperties vs @Value on Spring Boot 4.1.1. The relaxed-binding matrix is generated by binding each spelling rather than transcribed, and re-checked against real processes -- the in-process probe was wrong twice before it was right. Records the three findings that came out of it: @Value does get relaxed resolution inside Spring Boot (Boot attaches ConfigurationPropertySources), the configuration processor silently stops generating metadata on JDK 23+ when declared as a plain dependency, and @Valid is not what makes nested constraints run. profiles-and-config/ Precedence, profiles, spring.config.import and config trees. /precedence reports every source holding a property in rank order with file and line, which turns "my profile file had no effect" into a two-line answer. Also pins the counterintuitive one: an imported file outranks the file that imported it. spring-aop/ Designators, proxy types, and aspects that do not fire. One advice per supported designator so the reference table is generated from real matches; all fourteen unsupported designators fed to the parser. Two corrections to the reference documentation: unsupported designators throw UnsupportedPointcutPrimitiveException (extends RuntimeException, not IllegalArgumentException), and spring-boot-starter-aop was renamed to spring-boot-starter-aspectj in Boot 4. 19 contract tests across the three modules, 15 captured transcripts, all regenerated by scripts/run-all.sh. Verified on Spring Boot 4.1.1, Spring Framework 7.0.9, JDK 25.0.4.1. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Gip4srpzMwjgoba6uEfbr5
24 lines
1018 B
Java
24 lines
1018 B
Java
package com.ankurm.configprops;
|
|
|
|
import org.springframework.boot.SpringApplication;
|
|
import org.springframework.boot.autoconfigure.SpringBootApplication;
|
|
import org.springframework.boot.context.properties.ConfigurationPropertiesScan;
|
|
|
|
/**
|
|
* Companion application for the ankurm.com article
|
|
* "@ConfigurationProperties vs @Value in Spring Boot 4".
|
|
*
|
|
* <p>{@code @ConfigurationPropertiesScan} is what registers the {@code @ConfigurationProperties}
|
|
* types in {@code com.ankurm.configprops.props} as beans. Without it — and without
|
|
* {@code @EnableConfigurationProperties} or a stereotype annotation on each type — the
|
|
* classes compile, the application starts, and the beans simply do not exist. That is the first
|
|
* entry in the failure gallery: see {@code docs/03-registration.md}.
|
|
*/
|
|
@SpringBootApplication
|
|
@ConfigurationPropertiesScan
|
|
public class ConfigBindingApplication {
|
|
public static void main(String[] args) {
|
|
SpringApplication.run(ConfigBindingApplication.class, args);
|
|
}
|
|
}
|