Auto-configuration conditions and ordering

Three configuration classes

AutoConfiguration.imports registers three classes:

1. LettuceNearCacheHibernateAutoConfiguration
2. LettuceNearCacheMetricsAutoConfiguration
3. LettuceNearCacheActuatorAutoConfiguration

The first creates a HibernatePropertiesCustomizer. The other two add observation after Hibernate setup. Metrics and Actuator also declare ordering after Spring Boot JPA auto-configuration.

Hibernate configuration conditions

The Hibernate configuration requires LettuceNearCacheRegionFactory and EntityManagerFactory on the classpath. bluetape4k.cache.lettuce-near.enabled must be true or absent.

It does not wait for an EntityManagerFactory bean because the customizer must contribute properties before that factory is created. ApplicationContextRunner proves that enabled=false removes the customizer.

bluetape4k:
  cache:
    lettuce-near:
      enabled: false

Metrics configuration conditions

The metrics binder requires the RegionFactory, EntityManagerFactory, and MeterRegistry classes plus actual EntityManagerFactory and MeterRegistry beans. bluetape4k.cache.lettuce-near.metrics.enabled must be true or absent.

If the application has no Actuator starter or creates no registry, the cache may still work while the binder backs off. That is an optional-feature condition, not a cache failure.

Actuator configuration conditions

The endpoint requires the Endpoint, RegionFactory, and EntityManagerFactory classes, an actual EntityManagerFactory bean, and the top-level enabled setting. It does not check the metrics setting. An endpoint bean may therefore exist while metrics are disabled, and its L2 fields may be null when Hibernate statistics are off.

HTTP exposure is separate from bean registration.

management:
  endpoints:
    web:
      exposure:
        include: health,info,nearcache

Diagnostic order

1. Find all three names in the Spring Boot condition evaluation report.
2. Check top-level enabled separately from metrics enabled.
3. Verify runtime presence of spring-boot-hibernate, the JPA starter, and Actuator.
4. Check the EntityManagerFactory and MeterRegistry beans.
5. If the bean exists but HTTP does not, check management exposure.

Executable evidence

• AutoConfiguration.imports
• LettuceNearCacheHibernateAutoConfiguration.kt
• LettuceNearCacheMetricsAutoConfiguration.kt
• LettuceNearCacheActuatorAutoConfiguration.kt
• LettuceNearCacheAutoConfigurationTest.kt