commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Fassev (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TRANSACTION-9) [transaction] Add full file management capabilities to the FileResourceManager
Date Thu, 13 Jul 2006 22:17:30 GMT
    [ http://issues.apache.org/jira/browse/TRANSACTION-9?page=comments#action_12420952 ] 

Peter Fassev commented on TRANSACTION-9:
----------------------------------------

Yes, I think it is still a valid request. 

In the mean time I have done some effort to extended the FileResourceManager, including the
TranscationContext. Actually many of the functionality has been overwritten. It supports now
transaction secure operations on files and directories including creating, renaming, moving
and deleting. Please note, that there is still some job to do, mainly to clean the code and
to extend the tests and to write a documentation, but for now it works. At least, it can be
used as an example.

If you are interested in it, please let me know. 

> [transaction] Add full file management capabilities to the FileResourceManager
> ------------------------------------------------------------------------------
>
>          Key: TRANSACTION-9
>          URL: http://issues.apache.org/jira/browse/TRANSACTION-9
>      Project: Commons Transaction
>         Type: Improvement

>  Environment: Operating System: All
> Platform: All
>     Reporter: Peter Fassev
>     Priority: Minor

>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message