I never understood why the default is to write changes to disc. I'd prefer the default to leave the document unchanged and only write the changes when commit() is called. close() should be callable in any case, possibly throwing away any temporary objects - and it should be ok, to call it again.
As mentioned, harmonizing the various modules should be part of the change. To stick with our deprecation policy, I would deprecate revert() and after two releases change the handling completely :P So what to do with the in-place write functionality? The default is to open documents read-only - for read/write we would work on a copy and overwrite the original file when commit() is called. Andi --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
