[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Notifications over JBM core connections
jmesnil
do-not-reply at jboss.com
Thu Sep 18 09:12:32 EDT 2008
"timfox" wrote :
| What if there is no jmx server running? All this stuff should work with no JMX server too.
|
It does work even when there is no JMX MBeanServer (the ManagementService keeps a registry of managed resources using ObjectNames as their keys)
"timfox" wrote :
| I think it might be better to introduce a new packet on the wireformat ManagementMessage and send via that, then there's no need for special routing in the post office - it can be intercepted at the session level
|
"timfox" wrote :
| "jmesnil wrote : * the management service creates a NotificationListener for the given ObjectName
| |
|
| This seems JMX dependent to me
|
Same as above, I use a NotificationBroadcaster to keep track of notifications but it does not depend on any MBeanServer
"timfox" wrote :
| Are notifications supposed to be persisent (i.e. do they survive after the session that created them has died?)
|
| If not, then the listener could just be the session, and you could use the standard session send functionality to send the notification
I do not intend for the notifications to be persistent.
It makes sense to move the notification handling to the session.
But it still got the same issue: ServerSession.send() expect a ServerMessage that I need to create.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177415#4177415
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177415
More information about the jboss-dev-forums
mailing list