History | View | Annotate | Download (84.7 kB)
include shared flag for subfolders json output
Re-structured the whole thingRemoved unused foldersRe-packaged the java codeFixed the packaging of various artifacts to contain only relevant thingsChanged build.xml to check for all dependencies, fixed target dependencies
Fixed issue 72. IE does not send the correct Accept header resulting in gss serving public html folders with json content type instead of html
Fixed regression bug with uninitialized fields when rendering a public folder as html
Merge with optimizations branch
Backed out changeset ad848a720811
Files uploaded on a shared folder get the user as owner instead of the folder 's owner
temorary fix for lazy loading exception
removed even more DTOs
Merge with sharing branch
Removed System.out debug messages
shared flag for shared files(removed explicit head for fetching file display info), versioned flag for versioned files, admin support to update shared flag for all existing files and folders
Uncommented lines that are forgotten as commented
Field name in X-GSS-Metadata header should have been encoded
fix for 404 on upload progress, needs some further tuning
Fixed indentation and brackets
Fix for Issue 35 and for Revision: 8746b05052 concerning the forbideness of '/' in the file name.
Remove the first and the trailing slash from the query when searching for a resource
Recall a faulty previous commit that was related to forbiding the uploading of a file which file name would contain a slash and also adding to some files a copyright year.
Fix for Issue 35, added a note message on creating a new folder or updating an existing folder, informing the user that slashes are not allowed in folder names.The same note is added during the update of file name. Also, the client code has altered in order to forbid the creation or the update of a resource name.At last, don't allow uploading a file which file name contains slash.
Fix for Issue 35 that doesn't allow renaming of a file name when the new file name contains slashes.
Fix for Issue 35 that doesn't allow the creation of a folder which name contains slashes or the renaming of a folder name when the new folder name contains slashes
Allow public folders and all of the containing subfolders and files to be available in a web page.
Navigation through public folder url with no special characters in their folder names fixed. 1. Todo: Treat the special characters 2. For every public folder all containing sub-folder should also be public.
Minor fixes and remove logging
Fix the authentication sequence in requests of a file or a folder which is public or not public. This solves the Issue 14. Fix login with fireGSS by adding a boolean check in order the fireGSS client to receive a JSON response. ***TODO: fix sharing the home directory inside renderHTML
Some more fixes on Issue 16 - handling a CastException. Also working Issue 14 - when the user isNull and the file or folder is public for everyone then pretend that the owner is the user and and the user as a request attribute inside the FilesHandler servlet and not inside each method (e.g copy)
Don't decode resource names in JSON values. This is only necessary when names are passed as request parameters. This fixes renaming folders '+', '%' and ' ', among others.
Fix updates for folders named '%'.
-Navigation from the parent folder to subfolder and vice versa is available in the web page of a public folder-Only files that are marked as public are available in the web page of a public folder
- fix the problem which was related to download a file. It works now since an if statement was updated from if(content) to if (folder != null && content)- fix the path of a containing subfolder in a public folder- When a folder is marked as public from a user all containing files are also marked as public...
Simplify the content type conditional and make sure resource representation choice is independent of the access privileges.
In order to implement display public's folder contents as a web page i)Implement renderHTML method inside FilesHandler ii)make changes in serveResource in order to decide the contentType depending on client header request. This solves Issue 17
first commit - display public's folder contents as a web page
Reject invalid resource names, like '.' and '..' in both server and web client. This fixes issue 19.
Fix silent NPE due to auto-unboxing.
Consider the folder public flag when checking for authorization permissions.
Merge with 66f69a7348ed1a0de9113a64025721fcc6e68b84
-Allow user to declare a public folder i)a checkbox named [Public] added in the web client's folder properties dialog ii) an API change made in order to return readforall flag for a folder iii) a readforall column added in the domain modelPublic folders are marked with the same icon as shared folders and are available also in the My Shared view. This fixes Issue 17 along with the revision 7fc12576aafb
- Add an administration application.- Remove the redundant RequestBuilder wrapper for efficiency.- Fix warnings.- Ignore the admin app build artifacts.- Guard against users without userclasses in the DB.- Add a dev mode launcher for debugging the admin app.
first commit of adding the public feature to folder / readForAll on each folder
Avoid a NPE when the client doesn't send a Content-Type header.
Redirect to login for browser requests without a cookie present and also for requests with cookies but without the proper one.
Now that we keep around the cookie, give the user the opportunity to use it as the authentication token to get to a file. This way passing around simple file resource URIs is possible, and as long as the user has authenticated with the service in the current browser session, he can access the file. Furthermore, treat such simple browser access as a special case and redirect to login before returning back to the file. Now one can e-mail the file URI to another user and he can click on the link, get prompted to login (or even register for the service) and then get back to the file URI to download it automatically....
Handle metadata updates even if they are sent with application/x-www/form-urlencoded content type.
use http caching by using IF-MODIFIED-SINCE HEADERS and handling response accordingly
Don't convert spaces to plus signs when downloading a file. This fixes bug #756.
Fix the updated URL for a modified folder. This closes bug #759.
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.
Allow setting the modification date when updating a file.
Retry transactions in the face of optimistic locking exceptions for all "write" transactions in WebDAV API.Move TransactionHelper class to EJBs so it is visible from both REST and WebDAV WARs.
Retry transactions in the face of optimistic locking exceptions for all "write" transactions in REST API.
Added the groupURI parameter when parsing permissions, which precedes the group parameter. This allows the unique identification of groups throughout the application. We keep the group parameter for backwards compatibility with old clients
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.
Fix multiple file uploads in IE using Google Gears. It needed a POST instead of PUT, which required accommodating it in the server-side code. Also, error codes from file uploads are not handled in IE, since merely accessing the request.status field throws an internal error.
Fixed problems copying/moving via drag-and-drop had with international characters in file / folder names.
- more efficient moveFile implementation- code clean up for better maintenance and easier implementation of future file storage layering
Uploaded files should be counted towards owner's (i.e. namespace owner's) quota, not uplolader's.
Introduce TransactionHelper, a utility class for retrying the supplied transactional command in the face of rollbacks caused by optimistic lock exceptions. This allows multiple file uploads to succeed, even in a single core system.
Also make hitting the ENTER key behave the same as clicking the Upload button.
- Add "Save file as" menu that forces browser to download file instead of opening it inline.- Fix broken international characters in browser Save As dialog.
Decode file names received by PUT, as we do with file names received by multipart POST.
Remove the redundant gss top-level directory.