[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Hot Deploy with JBM 2

[ataylor]

anonymous wrote : The JBM 2.0 messaging core will be JMS agnostic, but is also a fully functioning messaging system that can be used/ embedded for OEMs etc.
  | 
  | The core should know nothing about JMS queues, topics, or durable subscriptions since these are JMS concepts, not core concepts. 

I agree.

anonymous wrote : Therefore the core should have no destination deployment configuration at all. 

What about configuring destination properties such as redeliverydelay etc, where would these be held.

anonymous wrote : With core, connection factories are created directly (new JBossConnectionFactory()), so there is no need for them to exist in JNDI, same for destinations. 

Again, where would we set these properties.

anonymous wrote : So, it's the security policy that determines whether users can create, read or write to a queue, the actual queues are created on the fly (if the security config allows it). 

what about topics, how would the security work since the user may not know the name of each consumer at deployment time? 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117489#4117489

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117489