commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Fujimoto-Johnson (JIRA)" <>
Subject [jira] Commented: (TRANSACTION-11) Improve relationship between ResourceManager and FileResourceManager
Date Tue, 01 Aug 2006 15:31:16 GMT
    [ ] 
Jeremy Fujimoto-Johnson commented on TRANSACTION-11:

I apologize for marking this issue with too high of a priority. I just took the default and
didn't pay enough attention.

However, on the second point: the reason I want this change is that I am implementing another
implementation of ResourceManager. I want to be able to switch between FileResourceManager
and my new implementation by configuration for use in the Slide project. It would be significantly
easier for me to do so if FileResourceManager implemented an interface that could be used
as the type referenced in AbstractTxFileStoreService and XMLResourceDescriptor. Fortunately
there almost is one: ResourceManager. Unfortunately there are two methods used that aren't
part of the ResourceManager interface: setDefaultTransactoinTimeout and reset. Thus my patch.
Now my new implementation of ResourceManager and FileResourceManager can each be used in Slide.

> Improve relationship between ResourceManager and FileResourceManager
> --------------------------------------------------------------------
>                 Key: TRANSACTION-11
>                 URL:
>             Project: Commons Transaction
>          Issue Type: Improvement
>    Affects Versions: 1.1, 1.2
>            Reporter: Jeremy Fujimoto-Johnson
>         Assigned To: Oliver Zeigermann
>         Attachments: commons-transaction-rm-patch.txt
> Add the reset method to ResourceManager so that classes using a ResourceManager won't
have to cast it to FileResourceManager to call this method.
> Add new constructors to FileResourceManager so that it can be constructed with the default
timeout period for transactions already specified so that you don't have to cast to FileResourceManager
to set it later.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


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

View raw message