Fix wrong encoding in new folder names, by returning the already constructed URI. This required that createFolder() returns the newly-created folder, which was always a good idea (builder pattern).
Retry transactions in the face of optimistic locking exceptions when creating folders or modifying resources. Also avoid an extra EJB call by returning the modified folder after the fact.
- Correctly check whether the group has already access to the resource- Check NPE (to be on the safe side & clear warning)- More appropriate messages
minor cosmetic change: appropriate button label
correctly refresh the OthersShared folder tree on folder renames
only sumbit changes to permissions if there are any
properly select and expand the tree item (group) that was previously "selected", upon updating the tree
be consistent: show sharing option in shared folders, as we do in shared folders
Silently replace @ character when uploading. (Will have to do at least till a proper solution is found.)
Use URL.encodeComponent() instead of URL.encode() as it encodes a few more characters that may appear in filenames and URL.encode() left unencoded.
View revisions
Also available in: Atom