The runtime's header propagation: the application's MessagePropagator beans and the ServiceLoader contributions (a bean wins over a ServiceLoader propagator of the same class), ordered by Wow's @Order (me.ahoo.wow.api.annotation.Order), not Spring's. wow.messaging.propagation.request (default true) switches the request-header propagator here; MessagePropagators.DEFAULT does not read it.

recoverableExceptionRegistry

@Bean

@Lazy(value = false)

fun recoverableExceptionRegistry(providers: ObjectProvider<RecoverableExceptionProvider>): RecoverableExceptionRegistry

The process's recoverable-exception classification (RecoverableExceptionRegistry.DEFAULT, seeded by the ServiceLoader contributions), with the RecoverableExceptionProvider beans registered into it. Never lazy: the classification is read through RecoverableExceptionRegistry.DEFAULT, not by injection, so the providers must be registered at startup even under spring.main.lazy-initialization.

serviceProvider

@Bean

@ConditionalOnMissingBean

fun serviceProvider(beanFactory: ConfigurableBeanFactory): ServiceProvider

wowCurrentBoundedContext

@Primary

@Bean(value = ["wow.CurrentBoundedContext"])

fun wowCurrentBoundedContext(applicationContext: ApplicationContext): NamedBoundedContext

wowLifecycleProcessor

@Bean(value = ["lifecycleProcessor"])

@ConditionalOnMissingBean(name = ["lifecycleProcessor"], search = SearchStrategy.CURRENT)

fun wowLifecycleProcessor(lifecycleProperties: LifecycleProperties): DefaultLifecycleProcessor