Uses of Class
com.ultikits.ultitools.utils.ModuleFileTransactions.RecordRefused

Packages that use ModuleFileTransactions.RecordRefused

Package	Description
com.ultikits.ultitools.utils

Uses of ModuleFileTransactions.RecordRefused in com.ultikits.ultitools.utils

Subclasses of ModuleFileTransactions.RecordRefused in com.ultikits.ultitools.utils

Modifier and Type	Class	Description
(package private) static final class	ModuleFileTransactions.NeedsOperator	A step found a file the transaction cannot identify; the record is held for the operator.

Methods in com.ultikits.ultitools.utils that throw ModuleFileTransactions.RecordRefused

Modifier and Type	Method	Description
private void	ModuleFileTransactions.applyRecord(ModuleFileTransactions.Record record)
private void	ModuleFileTransactions.applyRemoval(ModuleFileTransactions.Record record)	Deletes the JARs an uninstall recorded, before any module loads: each only if it is confirmed to still be the file that was recorded.
private void	ModuleFileTransactions.applyUpdate(ModuleFileTransactions.Record record)
private File	ModuleFileTransactions.backupOf(ModuleFileTransactions.Record record)
(package private) static File	ModuleFileTransactions.confined(File folder, String name)	Resolves a file name a record carries against the one folder it belongs to, refusing any name that would leave it.
private void	ModuleFileTransactions.failApply(ModuleFileTransactions.Record record, File file, Throwable error)	The apply could not be made.
private void	ModuleFileTransactions.failApply(ModuleFileTransactions.Record record, File file, Throwable error, ModuleFileTransactions.Report specific)	ModuleFileTransactions.failApply(Record, File, Throwable) with the line to log, when the old JAR is back in place, given by the caller instead of the generic one.
private void	ModuleFileTransactions.failStagedIdentity(ModuleFileTransactions.Record record, File staged, String actual)	The staged JAR is not the file recorded at staging (changed, or gone): the apply fails through ModuleFileTransactions.failApply(com.ultikits.ultitools.utils.ModuleFileTransactions.Record, java.io.File, java.lang.Throwable), so a kept old JAR goes back and the record is FAILED; the line names the staged path and both hashes.
private void	ModuleFileTransactions.finishCommit(ModuleFileTransactions.Record record)
private void	ModuleFileTransactions.finishRollback(ModuleFileTransactions.Record record, ModuleFileTransactions.RollbackPhase phase)	Removes the new JAR -- recognised by content, so nothing else is ever deleted -- and puts the old JAR back.
private void	ModuleFileTransactions.refuseLinkedFolders(ModuleFileTransactions.Record record)	The working folder and its two subfolders are this class's own; one that is a symbolic link would take every name confined to it somewhere else, so the record is refused.
private void	ModuleFileTransactions.restoreAfterFailure(ModuleFileTransactions.Record record)	A failed apply found at a later start: make sure it is undone -- the new JAR out of the modules folder and the old JAR back (ModuleFileTransactions.undoApply(com.ultikits.ultitools.utils.ModuleFileTransactions.Record)) -- and say so if it cannot be.
private String	ModuleFileTransactions.restoreBackup(ModuleFileTransactions.Record record)	Moves the kept old JAR back into the modules folder when it is not there.
private void	ModuleFileTransactions.resumeWithoutStagedJar(ModuleFileTransactions.Record record, File target, File staged)	The staged JAR is not in its folder: either the new JAR was moved in and the start ended before APPLIED was recorded, or the staged JAR is gone.
private String	ModuleFileTransactions.returnStagedJar(ModuleFileTransactions.Record record)	Moves the new JAR back to the staged folder when it was already moved into the modules folder -- recognised by its recorded hash, so nothing else is ever moved.
private File	ModuleFileTransactions.stagedOf(ModuleFileTransactions.Record record)
private boolean	ModuleFileTransactions.stoppedBeforeMoving(ModuleFileTransactions.Record record, File work, File old, File target, File backup, File staged)	The checks an apply makes before it moves anything; each that fails ends the transaction.
private String	ModuleFileTransactions.undoApply(ModuleFileTransactions.Record record)	Undoes whatever part of an apply happened: the new JAR goes back to the staged folder if it is in the modules folder (ModuleFileTransactions.returnStagedJar(com.ultikits.ultitools.utils.ModuleFileTransactions.Record), by its recorded hash), then the kept old JAR goes back (ModuleFileTransactions.restoreBackup(com.ultikits.ultitools.utils.ModuleFileTransactions.Record)) -- in that order, and the second only once the first is done, so the modules folder never holds both.