[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-312) De-monolithise persistencemanager

[Ovidiu Feodorov (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-312?page=all ]

Ovidiu Feodorov updated JBMESSAGING-312:
----------------------------------------

    Fix Version/s: Unscheduled
                       (was: 1.2.1)

> De-monolithise 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: Unscheduled
>
>   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