[
https://issues.apache.org/jira/browse/SANDESHA2-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Illsley resolved SANDESHA2-71.
------------------------------------
Resolution: Won't Fix
Hi Chamikara, I'm doing some cleanup so returning this JIRA for the moment. I
actually disagree with the sentiment anyway, so if you want to do this, please
re-raise the issue on the list.
Thanks,
David
> RM concepts and logic should be moved out of the Storage Manager API and the
> InMemory StorageManager Impl
> ---------------------------------------------------------------------------------------------------------
>
> Key: SANDESHA2-71
> URL: https://issues.apache.org/jira/browse/SANDESHA2-71
> Project: Sandesha2
> Issue Type: Improvement
> Reporter: Chamikara Jayalath
>
> It seems like InMemory Storage Manager includes a lot of should be moved out
> of it. The scope of the StorageManager API and the InMemory implementation
> should be limited to the task it's name imply.
> Otherwise it will make it really hard when it comes to the introduction of
> new Storage Managers.
> One example is the getNextMessageToSend() method of the SenderBeanManager
> which I think should be removed.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
