@NonNullApi

Package org.springframework.data.neo4j.core.mapping.callback

This package contains the callback API.

See: Description

Interface Summary

Interface	Description
BeforeBindCallback<T>	Entity callback triggered before an Entity is bound to a record (represented by a java.util.Map<String, Object>).
ReactiveBeforeBindCallback<T>	Entity callback triggered before an Entity is bound to a record (represented by a java.util.Map<String, Object>).

Class Summary

Class	Description
AuditingBeforeBindCallback	EntityCallback to populate auditing related fields on an entity about to be bound to a record.
EventSupport	Utility class that orchestrates EntityCallbacks.
ReactiveAuditingBeforeBindCallback	Reactive EntityCallback to populate auditing related fields on an entity about to be bound to a record.
ReactiveEventSupport	Utility class that orchestrates EntityCallbacks.

Package org.springframework.data.neo4j.core.mapping.callback Description

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 convinience, 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