You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sandesha-dev@ws.apache.org by "Chamikara Jayalath (JIRA)" <ji...@apache.org> on 2007/02/10 05:06:07 UTC
[jira] Created: (SANDESHA2-71) RM logic should be moved out of the
InMemory StorageManager
RM logic should be moved out of the InMemory StorageManager
-----------------------------------------------------------
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Updated: (SANDESHA2-71) RM concepts and logic should be
moved out of the Storage Manager API and the InMemory StorageManager Impl
Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chamikara Jayalath updated SANDESHA2-71:
----------------------------------------
Summary: RM concepts and logic should be moved out of the Storage Manager API and the InMemory StorageManager Impl (was: RM logic should be moved out of the InMemory StorageManager)
> 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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Updated: (SANDESHA2-71) RM concepts and logic should be
moved out of the Storage Manager API and the InMemory StorageManager Impl
Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chamikara Jayalath updated SANDESHA2-71:
----------------------------------------
Summary: RM concepts and logic should be moved out of the Storage Manager API and the InMemory StorageManager Impl (was: RM logic should be moved out of the InMemory StorageManager)
> 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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Resolved: (SANDESHA2-71) RM concepts and logic should be
moved out of the Storage Manager API and the InMemory StorageManager Impl
Posted by "David Illsley (JIRA)" <ji...@apache.org>.
[ 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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org