@NonNullApi

Package org.springframework.data.neo4j.repository.event

Contains the infrastructure for the event system.

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.
IdGeneratingBeforeBindCallback	Callback used to call the ID generator configured for an entity just before binding.
OptimisticLockingBeforeBindCallback	Callback to increment the value of the version property for a given entity.
ReactiveAuditingBeforeBindCallback	Reactive EntityCallback to populate auditing related fields on an entity about to be bound to a record.
ReactiveIdGeneratingBeforeBindCallback	Callback used to call the ID generator configured for an entity just before binding.
ReactiveOptimisticLockingBeforeBindCallback	Callback to increment the value of the version property for a given entity.

Package org.springframework.data.neo4j.repository.event Description

Contains the infrastructure for the event system. 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.

Since:

6.0

Author:

Michael J. Simons