commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Zeigermann (JIRA)" <>
Subject [jira] Commented: (TRANSACTION-9) [transaction] Add full file management capabilities to the FileResourceManager
Date Fri, 20 Jul 2007 15:01:06 GMT


Oliver Zeigermann commented on TRANSACTION-9:


I agree to what Peter says about locking of files/folders and locking in general. What about
a HierarchicalLockManager that takes care of all that stuff for us? Might even be reuseable.
I will add an empty impementation for us to remember to later fill it.


I will add the interfaces to the SVN soon. Let us base further discussions on what is in SVN
from then on. That might make things a bit easier. I will also propose a simple interceptor
(instead of listener) concept that is "inspired" by how it works in XA and Spring MVC.

Concerning Jörg's comments:
 1. setProperty() is supposed to return the old value, but maybe that does not make that much
sense? WDYT?
 2. append has been added to writeStream()
 3. the filter thing sounds interesting: Do you have code for that?
 4. I have no really elegant solution to the create-Problem. Distinguishing between FileResource
and DirectoryResource introduces many problems, some of them requiring excessive casting.
I have been there before. Currently I favor the createAsFile/Directory() solution.


> [transaction] Add full file management capabilities to the FileResourceManager
> ------------------------------------------------------------------------------
>                 Key: TRANSACTION-9
>                 URL:
>             Project: Commons Transaction
>          Issue Type: Improvement
>         Environment: Operating System: All
> Platform: All
>            Reporter: Peter Fassev
>            Assignee: Oliver Zeigermann
>            Priority: Minor
>             Fix For: 2.0
>         Attachments:
> Hi,
> As stated in the doc the FileResourceManager is:
> "A resource manager for streamable objects stored in a file system"
> I agree, that this is a resource manager, but it could be easily extended, to 
> support a full file management system. It will be very helpful to have 
> additional methods like renameResource(), getResourceSize(), getResourceTime(), 
> setResourceTime() etc. This are common file operations, which should be managed 
> by the FileResourceManager.
> Further it will be very helpful to have (real) support for resource collections 
> (folders). It will be necessary to distinguish between single resources (files) 
> and collections (folders). 
> Together, this features will enable a transactional access to any file based 
> resources - for instance a document repository.
> Are there plans for such extensions and if not, will they actually fit in the 
> goals of the transaction library?
> If not, please open the underlying structure, like the inner class 
> TransactionContext, in order to add extensions the file management. For 
> instance, it will be good to have a separate factory method, which creates the 
> context.
> If you are interested in this proposal, I am ready to contribute to this 
> project. I consider myself as an experienced java developer and I will be glad 
> to help you. 
> Best regards
> Peter Fassev

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message