Uses of Record Class
io.fluxzero.sdk.modeling.MutationPlan.Resolution

Packages that use MutationPlan.Resolution

Package	Description
io.fluxzero.sdk.modeling
io.fluxzero.sdk.persisting.repository

Uses of MutationPlan.Resolution in io.fluxzero.sdk.modeling

Methods in io.fluxzero.sdk.modeling that return MutationPlan.Resolution

Modifier and Type	Method	Description
MutationPlan.Resolution	MutationPlan.TargetPlan.resolve(Object input)	Resolves mutation targets from the input using the default resolution mode without an explicit message context.
MutationPlan.Resolution	MutationPlan.TargetPlan.resolveReplay(Object input, MutationPlan.ResolvedModel replayTarget)	Resolves replay inputs, binding a unique write ancestor to the authoritative stream identity.
MutationPlan.Resolution	MutationPlan.Resolution.withPrimaryOnly()
MutationPlan.Resolution	MutationPlan.Resolution.withResolvedModels(List<MutationPlan.ResolvedModel> resolvedModels)	Returns a resolution with the supplied Models, retaining deferred writes and references while clearing ancestor dependencies.

Methods in io.fluxzero.sdk.modeling with parameters of type MutationPlan.Resolution

Modifier and Type	Method	Description
static CommitAttempt	CommitAttempt.create(long readStateIndex, MutationPlan.Resolution resolution, Map<String, ? extends Entity<?>> loadedModels)	Creates a loaded begin-state for one resolved target set.
static Map<String,Object>	ModelBatchScope.currentValues(String namespace, MutationPlan.Resolution resolution)	Returns the pending values needed to reconstruct one resolved context, including ancestor dependencies.
static Map<String,Object>	ModelBatchScope.currentValues(String namespace, MutationPlan.Resolution resolution, Object repositoryOwner)	Resolves the pending context and ancestor dependencies within this repository family only.

Method parameters in io.fluxzero.sdk.modeling with type arguments of type MutationPlan.Resolution

Modifier and Type	Method	Description
static Object	ModelReducer.replay(MutationPlan plan, DeserializingMessage event, CommitAttempt context, String targetModelId, BiFunction<MutationPlan.Resolution, CommitAttempt, CommitAttempt> dependencies)	Replays with late-bound embedded dependencies at the stored event's historical boundary.

Uses of MutationPlan.Resolution in io.fluxzero.sdk.persisting.repository

Methods in io.fluxzero.sdk.persisting.repository with parameters of type MutationPlan.Resolution

Modifier and Type	Method	Description
CommitAttempt	DefaultModelRepository.loadContext(MutationPlan.Resolution resolution)	Loads all direct commit targets at one state boundary.
CommitAttempt	DefaultModelRepository.loadContext(MutationPlan.Resolution resolution, Long maxStateIndex, Map<String,Object> stagedValues, boolean includeMessageBatch)	Loads a commit context with an explicit choice whether pending values from the surrounding tracking batch should be overlaid.
CommitAttempt	DefaultModelRepository.loadContext(MutationPlan.Resolution resolution, Long maxStateIndex, Map<String,Object> stagedValues, boolean includeMessageBatch, boolean migration)	Loads a commit attempt for the resolved Models at the supplied maximum state index, with staged values and the requested message-batch and migration visibility.
default CommitAttempt	ModelRepository.loadContext(MutationPlan.Resolution resolution)	Loads all model parameters for one selected message handler at one repository boundary.
CommitAttempt	DefaultModelRepository.loadCurrentContext(MutationPlan.Resolution resolution, Map<String,Object> stagedValues, boolean includeMessageBatch)	Loads one transaction's initial context at a freshly observed storage boundary.
CommitAttempt	DefaultModelRepository.loadDeferredDocumentContext(MutationPlan.Resolution resolution)	Internal fast preparation for a direct DOCUMENT target; pending mutations retain eager preparation.
CommitAttempt	DefaultModelRepository.loadRebaseContext(MutationPlan.Resolution resolution, Long maxStateIndex, Map<String,Object> stagedValues, boolean includeMessageBatch, boolean migration)	Reloads a conflict retry or ACCEPT rebase, waiting for pending document materialization and allowing an incomplete authoritative document to advance the exact boundary before mutation evaluation.