Package org.springframework.data.neo4j.core.mapping.callback
@NonNullApi
package org.springframework.data.neo4j.core.mapping.callback
This package contains the callback API. There are both imperative and reactive callbacks available that get invoked
just before an entity is bound to a statement. These can be implemented by client code. For further convenience,
both imperative and reactive auditing callbacks are available. The config package contains a registrar and an
annotation to enable those without having to provide the beans manually.
The event system comes in two flavours: Events that are based on Spring's application event system and callbacks that
are based on Spring Data's callback system. Application events can be configured to run asynchronously, which make
them a bad fit in transactional workloads.
As a rule of thumb, use Entity callbacks for modifying entities before persisting and application events otherwise.
The best option however to react in a transactional way to changes of an entity is to implement
DomainEvents on an aggregate root.
- Author:
- Michael J. Simons
-
ClassDescriptionA callback that can be used to modify an instance of a
Neo4jPersistentEntityafter it has been converted: That is, when a Neo4j record has been fully processed and the entity and all its associations have been processed.EntityCallbackto populate auditing related fields on an entity about to be bound to a record.Entity callback triggered before an Entity is bound to a record (represented by ajava.util.Map<String, Object>).Utility class that orchestratesEntityCallbacks.ReactiveEntityCallbackto populate auditing related fields on an entity about to be bound to a record.Entity callback triggered before an Entity is bound to a record (represented by ajava.util.Map<String, Object>).Utility class that orchestratesEntityCallbacks.