All Classes and Interfaces
Class
Description
A safe, intentional application failure with a stable client-visible code.
A successful authentication or account-operation message.
Shared superclass for managed domain entities.
Maps an aggregate between its persistence model and distinct create, patch,
and response transport models.
CRUD lifecycle with distinct create, PATCH, and response transport models.
CRUD lifecycle for one DTO shape used for both writes and responses.
Current and replacement credentials accepted by the default account endpoint.
New username accepted by the default account endpoint.
Minimal identity exposed by the default current-session endpoint.
Immutable per-entity configuration consumed by
BaseService.Turns a
QueryFilterCriteria into a JPA Specification.Produces the shared
ApiError wire contract for common HTTP failures.Transport-neutral identity attached to a history record.
Resolves the actor responsible for the operation currently being recorded.
Input presented to an application's History data-classification policy.
Persisted representation and lifecycle metadata selected by a History policy.
Identity- and payload-free lifecycle event suitable for metrics or audit sinks.
Raised when a safe History lifecycle decision cannot be enforced.
Application seam for classifying, partitioning, redacting, retaining, and
legally holding History records before persistence.
Enforces History retention, quota, purge, erasure, and legal-hold mechanics.
Identifies a kind of entity whose changes are recorded in the change-history
feature.
Records entity lifecycle snapshots for a history implementation.
Application-owned record-level authorization policy for the default History endpoint.
Immutable HTTP read model for one history event.
Raised when a history event cannot be recorded without losing information.
Credentials accepted by the default session login endpoint.
Result returned after the default endpoint establishes a session.
Announces entity changes to connected clients.
Command metadata presented to the application lifecycle policy before storage.
Redacted persisted payload and lifecycle metadata for one Offline command.
Identity- and payload-free Offline lifecycle event for metrics or audit sinks.
Raised when the Offline store cannot enforce its bounded lifecycle contract.
Application seam for Offline payload redaction, partitioning, retention, and legal hold.
Enforces Offline retention, quota, purge, erasure, and legal holds per partition.
Identity-, URL-, and payload-free Offline operational event.
Stable operation families.
Stable low-cardinality outcomes across Offline operations.
Tracks a monotonic revision number per entity kind so that offline clients
can tell whether their local copy is stale.
Resolves the opaque audience shared by an SSE connection and the changes it may receive.
Machine-readable outcome of a replayed offline command.
Marks a DTO field as output-only: it is serialized in responses but ignored
in request bodies.
Holds the entity-key to JPA-entity bindings the query engine filters over.
Identifies an entity the query engine can filter over.
Identity- and payload-free completion event for a paged repository query.
Bounded query completion states.
A filter payload that a
FilterSpecificationBuilder knows how to
compile.Immutable request context supplied to an application's relation-option policy.
Safe completion event for relation-option queries; it contains no entity, field, search, or actor value.
Bounded completion states suitable for low-cardinality tags.
Application-owned authorization and row-scope policy for relation-option queries.
Safe fallback: preserve event shape, discard snapshot fields, partition by
actor, retain for the configured bounded period, and create no legal hold.
Safe fallback that stores no request payload or headers and applies bounded retention.
Wraps a Spring Data Pageable with an optional search text parameter.
Authorization expressions the starter itself uses.
Wires the starter's default authentication stack from the dependency alone.
Configuration for the starter's default authentication stack.
Wires everything in
vireo-core from the dependency alone.Runs every library module's migrations, each into its own history table,
before handing over to the consumer's own Flyway.
BaseEntity carries @EntityListeners(AuditingEntityListener),
which silently records nothing unless auditing is enabled somewhere.Every starter module annotates its endpoints with
@PreAuthorize.Configuration for shared Core web and auditing behavior.
Runs one module's migrations into that module's own history table.
A module's claim on a set of database tables.
Wires audit history from the dependency alone.
Configuration for the default History HTTP read endpoint.
Lets a consumer add to the starter's default security chain without replacing
it.
Resolves the offline actor from the starter's default user model.
Wires the offline sync stack from the dependency alone.
Configuration for offline replay, hydration, and heartbeat transport.
Wires the query engine from the dependency alone.
Configuration for Query Engine metadata, relation-option, and saved-filter endpoints.
Builds Vireo's standard browser session-security chain for applications that
also declare narrower security chains.
Mutable JPA model for applications opting into Vireo's default user store.
Adapts an
StarterUser to Spring Security.Repository exposed only as part of the optional default database user model.
Current username returned after a successful rename.