spring boot

🌱 Spring Boot starter

Build → register annotated singletons → start transport. Native annotation contracts live in declarative-configuration.

• tachyon.* → TachyonProperties record (enabled=true, name, version, host, port=8080) TachyonProperties.

• Builds server with properties, ordered extensions and customizers, then registers annotated beans after singleton initialization, before lifecycle startup (ServerConfiguration#tachyonServer, TachyonBeanRegistrar#afterSingletonsInstantiated). Annotated beans can inject TachyonServer.

• Discovery uses AopUtils.getTargetClass on initialized beans; JDK and class proxies retain advice. Unrelated lazy beans stay uninitialized; lazy annotated beans need discoverable declared types (TachyonBeanRegistrar#afterSingletonsInstantiated).

• User server ⇒ construction and registrar back off together; lifecycle still supplied (TachyonAutoConfiguration#TachyonAutoConfiguration, ServerConfiguration).

• Wire regression tests cover all three feature kinds through JDK proxy advice, server injection, custom codecs, lazy-bean isolation and user-server backoff (TachyonBeanRegistrationTest#jdkProxyUsesTargetAnnotationsAndPreservesAdviceForEveryFeature).

• Spring Boot 4.1.1 pinned in the root pom.xml; starter dependencies use that property, with no Boot BOM import in the module POM.

• Completion-only beans retain target parameter names and proxy advice (TachyonCompletionBeanTest#discoversCompletionOnlyProxyAndBindsTargetParameterNamesThroughAdvice).

• TachyonServerLifecycle starts/closes the server with the application context; lock serializes calls, running flips only after start/close succeeds (failure keeps prior state, retry allowed) (TachyonServerLifecycle#start).

• Actuator (all optional): HealthConfiguration needs HealthIndicator class, then management.health.tachyon.enabled ⇒ tachyon indicator, UP + host/port iff lifecycle running (TachyonHealthIndicator#health). MetricsConfiguration needs Micrometer class + MeterRegistry bean (auto-config ordered after Boot metrics) ⇒ customizer adds TachyonMetricsListener (timer mcp.server.operations, tags method + snake-case outcome; starter-built server only) and TachyonMeterBinder feature gauges (MetricsConfiguration, TachyonMetricsListener#complete, TachyonMeterBinder#bindTo). Listener uses @InternalApi ObservationListener → api-stability.

• Actuator conditions and backoff covered by TachyonActuatorAutoConfigurationTest.

• Feature gauges bind directly to the available registry; Boot's metrics module is optional (RegistryMetricsConfiguration#tachyonMeterBinder). Both classpaths exercise operation timing and all three gauges (TachyonActuatorAutoConfigurationTest#metricsWorkWithoutBootMetricsModule).

Related: configuration, extensions, integrations.

---

_{📄 source .llm-wiki/modules/spring-boot.md · updated 2026-09-15 · verified at 9eec1092 · tags [module, spring-boot, configuration]}