See: Description
Class | Description |
---|---|
CleanupFilter | |
HashBasedOptimisticLockingConfiguration |
Caution: persistNode should be called in a transaction to ensure consistent comparison between data from backend/data being persisted,
otherwise it's possible that another writer modifies something before this class obtains a lock and the changes by that writer will be lost
Edge cases:
If one deletes a node that is a root of olock, and another changes that node, it is NOT considered a conflict, regardless of operation order the node will be just deleted.
|
HashBasedOptimisticLockingConfiguration.HashMarkingTypesafeNodeFilter |
Inserts #hash props into node according to @ConfigurableProperty annotations
|
OLockCopyFilter | |
OLockHashCalcFilter |
Calculates and sets olock hashes for nodes that have the _.hash property (ignores the previous value)
|
OLockMergeDualFilter |
Performs hash-based optimistic locking logic that is
to detect conflicting changes an throw an exception if there are any
if there are none, make sure that all non-conflicting changes from both old and new nodes are preserved.
Merges old node and new node into a single resulting node.
|
This package is contained in the Maven module dcm4che-conf-core.
Copyright © 2017 dcm4che.org. All rights reserved.