| Modifier and Type | Field and Description |
|---|---|
| protected ValueHolderInterface | unitOfWorkValueHolder
Stores the original uow clone's value holder. |
| Access | Constructor and Description |
|---|---|
| public |
| unitOfWorkValueHolder | back to summary |
|---|---|
| protected ValueHolderInterface<T> unitOfWorkValueHolder Stores the original uow clone's value holder. | |
| BackupValueHolder | back to summary |
|---|---|
| public BackupValueHolder(ValueHolderInterface<T> unitOfWorkValueHolder) | |
| getRow | back to summary |
|---|---|
| public AbstractRecord getRow() Overrides org. Doc from org. Return the row.
| |
| getSession | back to summary |
|---|---|
| public AbstractSession getSession() Overrides org. Doc from org. Return the session.
| |
| getUnitOfWorkValueHolder | back to summary |
|---|---|
| public ValueHolderInterface Return the original uow clone's value holder. | |
| instantiate | back to summary |
|---|---|
| public T instantiate() Implements abstract org. If the original value holder was not instantiated, then first instantiate it to obtain the backup value.
| |
| instantiateForUnitOfWorkValueHolder | back to summary |
|---|---|
| public T instantiateForUnitOfWorkValueHolder(UnitOfWorkValueHolder<T> unitOfWorkValueHolder) Implements abstract org. Doc from org. Triggers UnitOfWork valueholders directly without triggering the wrapped valueholder (this). When in transaction and/or for pessimistic locking the UnitOfWorkValueHolder needs to be triggered directly without triggering the wrapped valueholder. However only the wrapped valueholder knows how to trigger the indirection, i.e. it may be a batchValueHolder, and it stores all the info like the row and the query. Note Implementations of this method are not necessarily thread-safe. They must be used in a synchronized manner
| |
| isPessimisticLockingValueHolder | back to summary |
|---|---|
| public boolean isPessimisticLockingValueHolder() Implements abstract org. Doc from org. Answers if this valueholder is a pessimistic locking one. Such valueholders are special in that they can be triggered multiple times by different UnitsOfWork. Each time a lock query will be issued. Hence even if instantiated it may have to be instantiated again, and once instantiated all fields can not be reset. Note Implementations of this method are not necessarily thread-safe. They must be used in a synchronizaed manner
| |