[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-312) Refactor persistencemanager
Tim Fox (JIRA)
jira-events at lists.jboss.org
Mon Oct 1 06:58:41 EDT 2007
[ http://jira.jboss.com/jira/browse/JBMESSAGING-312?page=all ]
Tim Fox closed JBMESSAGING-312.
-------------------------------
Resolution: Out of Date
> Refactor persistencemanager
> ---------------------------
>
> Key: JBMESSAGING-312
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-312
> Project: JBoss Messaging
> Issue Type: Task
> Reporter: Tim Fox
> Assigned To: Tim Fox
> Fix For: 2.0.0 Beta 1
>
> Original Estimate: 4 days
> Remaining Estimate: 4 days
>
> Refactor PersistenceManager to make less monolithic.
> The PersistenceManager should really only deal with simple persistence operations, e..g. addReference, removeReference, addMessage, removeMessage etc. This makes it easy to re-implement for another type of store.
> Currently the PM contains logic that belongs elsewhere e.g. in the ChannelState.
> The TransactionCallback should be removed to it's own java file.
> The locking operations should occur in the caller.
> There should be an abstraction PMTxContext which can be passed into PM operations to group them.
> This should dramatically clarify and simplify things
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list