https://issues.apache.org/ooo/show_bug.cgi?id=121665
--- Comment #9 from ptoye <[email protected]> --- Firstly, I didn't realise that English was not your first language. You certainly write it very well. Far better than I could do in your language (whatever that is). I think that neither of us is quite understanding the other. And possibly we are both understanding different things from the same documentation! Exactly what does the Overwrite property mean when using StoreToURL or StoreAsURL? Is it intended to mean: A) (if TRUE) that even if the file exists, it will be overwritten, and (if FALSE), that it will never be overwritten and produce an error. That seems to be what your program demonstrates. Or B) is the value stored with the file, so that if it is FALSE the file cannot be overwritten? This seems to be the same as ReadOnly, and therefore redundant. So I have assumed that (A) is correct. But my original comment was about the behaviour of StoreAsURL when a null array is given as parameter. In this case, the definition in XMediaDescriptor says explicitly "For storing only: overwrite any existing file, default is false, so an error occurs if the target file already exists." But my program shows that this doesn't happen: the file is overwritten without an error. In my opinion, that is the correct behaviour: the default should never destroy information. That's why I think it's an OO bug. If the OO teams think that the current behaviour is correct, the documentation should be changed to reflect reality. Anyway, I now know that I should always set the Overwrite property as I want to, and trap the error if it's set to FALSE. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
