Restoring bean registration while keeping the optional nature of AuditorAware in the Reactive-/AuditingHandler.
The changes done previously caused AOT code generation to fail with:
org.springframework.aot.generate.UnsupportedTypeValueCodeGenerationException: Code generation does not support org.springframework.beans.factory.config.AutowiredPropertyMarker
See: #3177
Spring Data provides sophisticated support to transparently keep track of who created or changed an entity and when the change happened.
To benefit from that functionality, you have to equip your entity classes with auditing metadata that can be defined either using annotations or by implementing an interface.
Spring Data provides sophisticated support to transparently keep track of who created or changed an entity and when the change happened.To benefit from that functionality, you have to equip your entity classes with auditing metadata that can be defined either using annotations or by implementing an interface.
Additionally, auditing has to be enabled either through Annotation configuration or XML configuration to register the required infrastructure components.
Please refer to the store-specific section for configuration samples.
[NOTE]
====
Applications that only track creation and modification dates are not required do make their entities implement <<auditing.auditor-aware,`AuditorAware`>>.
If no `AuditorAware` or `DateTimeProvider` bean is configured, `AuditingHandler` will use Spring's autowiring to detect a matching bean if beans of the corresponding type are available in the application context.
@ -116,13 +116,12 @@ public abstract class AuditingBeanDefinitionRegistrarSupport implements ImportBe
@@ -116,13 +116,12 @@ public abstract class AuditingBeanDefinitionRegistrarSupport implements ImportBe
@ -130,9 +129,6 @@ public abstract class AuditingBeanDefinitionRegistrarSupport implements ImportBe
@@ -130,9 +129,6 @@ public abstract class AuditingBeanDefinitionRegistrarSupport implements ImportBe