public static interface FileSystem.AtomicAction
no events about changes in filesystems are fired.
Nomenclature warning: the action is by no means "atomic" in the usual sense of the word, i.e. either running to completion or rolling back. There is no rollback support. The actual semantic property here is close to "isolation" - the action appears as a single operation as far as listeners are concerned - but not quite, since it is perfectly possible for some other thread to see half of the action if it happens to run during that time. Generally it is a mistake to assume that using AtomicAction gives you any kind of consistency guarantees; rather, it avoids producing change events too early and thus causing listener code to run before it should.