Fix bug: When renaming file, selected file was not updated, leading to a 404 error if user tried to view properties of renamed file. (Bug #752)
Fix bug introduced through stupid Eclipse cleanup.
- Check when renaming file that name doesn't already exist.- Add constraint to DB to ensure we don't get duplicate filenames.
Throw any exceptions thrown unwrapped. This way, the caller knows what it's dealing with in its try/catch block.(Previously, everything thrown was an Exception and most (all?) callers would simply turn this into a 500 error, since they don't check the cause.)
Make folder updates work with a single DB transaction (EJB call). Now the modification date on every child file is properly updated. Also rename modifyFolder() to updateFolder() for consistency with updateFile() and make setFilePermissions/setFolderPermissions private helper methods.
Make file updates work with a single DB transaction (EJB call). Besides the performance benefits, this change properly updates the modification date on every file update.
Requests without Authorization header should be rejected by isRequestValid().
Merge with 6e728a7cfa0b1004acb2613421e261890e560813
Double the retry attempts and the retry timeout in an attempt to better handle the load on the app servers. Also log the final failed retry so that it is greppable in the logs.
- Add constraint in order to avoid double entries due to concurrency. (Happened twice in production.)- Add versioning to avoid lost updates. (Impossible to tell if it has already happened.)
View revisions
Also available in: Atom