[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1671) Consider storing JMS destinations in their own journal instance

[Tim Fox (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBMESSAGING-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Fox updated JBMESSAGING-1671:
---------------------------------

    Fix Version/s: 2.0.0
                       (was: 2.0.0.beta5)


> Consider storing JMS destinations in their own journal instance
> ---------------------------------------------------------------
>
>                 Key: JBMESSAGING-1671
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1671
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>            Assignee: Tim Fox
>             Fix For: 2.0.0
>
>
> We should consider storing JMS destinations in their own journal instance, and automatically deploy them into JNDI and management from this. This would mean that any JMS destinations created via the management interface would get redeployed on startup, which is not currently the case

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira