AtomicFile
instead. It would
be nice to update all existing uses of this to switch to AtomicFile, but since
their on-file semantics are slightly different that would run the risk of losing
data if at the point of the platform upgrade to the new code it would need to
roll back to the backup file. This can be solved... but is it worth it and
all of the testing needed to make sure it is correct?@Deprecated public class JournaledFile extends Object
Constructor and Description |
---|
JournaledFile(File real,
File temp)
Deprecated.
|
Modifier and Type | Method and Description |
---|---|
File |
chooseForRead()
Deprecated.
Returns the file for you to read.
|
File |
chooseForWrite()
Deprecated.
Returns a file for you to write.
|
void |
commit()
Deprecated.
Commit changes.
|
void |
rollback()
Deprecated.
Roll back changes.
|
public File chooseForRead()
public File chooseForWrite()
public void commit()
public void rollback()