org.azyva.dragom.model.config

Interface MutableConfig

All Superinterfaces:

Config

public interface MutableConfig
extends Config

Extension of Config that allows changing the configuration data.

The design orientation of the mutable extension to Config and child interfaces is to allow applying changes atomically to the various NodeConfig. That is why transfer objects are used.

The reason for implementing atomicity semantics are two-fold:

• If the configuration data is meant to be persisted, it is expected that persisting operations be performed for each mutation and mutating whole objects at a time provides more efficiency than persisting each individual change;
• We want to support configuration data undergoing changes while a Model is active and requiring the associated Model to react to whole object changes provides more efficiency than reacting to each individual change.

Runtime change events may eventually be supported so that the Model can adjust to configuration changes at runtime.

Method Summary

Modifier and Type	Method and Description
MutableClassificationNodeConfig	createMutableClassificationNodeConfigRoot() Creates a new uninitialized root MutableClassificationNodeConfig.

Methods inherited from interface org.azyva.dragom.model.config.Config

getClassificationNodeConfigRoot

Method Detail

createMutableClassificationNodeConfigRoot

MutableClassificationNodeConfig createMutableClassificationNodeConfigRoot()

Creates a new uninitialized root MutableClassificationNodeConfig.

Creation is finalized and visible only once MutableNodeConfig.setNodeConfigTransferObject(org.azyva.dragom.model.config.NodeConfigTransferObject, org.azyva.dragom.model.config.OptimisticLockHandle) is called, replacing any root MutableClassificationNodeConfig that may already be set.

Returns:

Root MutableClassificationNodeConfig.