To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=97613 Issue #|97613 Summary|OOo file locking should forbid same user twice writing | on same system Component|framework Version|DEV300m37 Platform|PC URL| OS/Version|Windows XP Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|tm Reported by|bmarcelly
------- Additional comments from [email protected] Sun Dec 28 15:26:15 +0000 2008 ------- This report is related with Issue 95809. Writing macros I discovered this loophole of the OpenOffice file locking: - open a file by loadComponentFromURL without any particular option: the file opens in read/write mode. - while leaving the file open, the same macro opens again the same file by loadComponentFromURL Another window appears, also in read/write mode. You can change the contents and store the modified file. This is a regression from 2.4.2 and all older versions, and can lead to document destruction. In 2.4.2 and older, the second loadComponentFromURL will open the file in read-only mode. Apparently the new file-locking accepts to open again in read/write mode because it is the same user on the same system. I don't see why it should allow this. If system file locking is used, it will of course prevent this situation. Next attachment has a simple macro showing the problem. The case is not far-fetched: it could be two independent scripts from the same user opening the same file. Note that the bug does not appear with user interface File > Open because OpenOffice recognizes that the file is already open and does not open a new window. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
