Yes, you can have multiple clients without confusion.
The handback object is more or less of use to the Listener. If it has made many
registrations to different MBeans it could use the handback as an id to quickly
distinguish from which subscription a notification came when
handleNotification()
Thank you for quick responses.
I have another question though. If there are multiple clients that want to
listen for notifications, does the ServiceMBeanSupport class handles this case?
Should I pass a unique handback object when registering, so that the listener
can be uniquely identified?
No.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3857207#3857207
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3857207
---
SF email is sponsored by - The IT Product
In the 3.2.6 version, in order to receive JMX notifications,
docs/examples/jmx/jmx-rmi-adaptor.sar file needed to be copied to the deploy
directory, and jmx-invoker-adaptor-server.sar removed. Is it still necessary
in the 4.0.0 version? I don't see the jmx-rmi-adaptor.sar in the 4.0.0
docs/ex
There are examples of this in the testsuite as well as the admin/devel guide.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3857196#3857196
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3857196
---
I haven't touched the RMIAdaptor for some time, but doesn't RMIAdaptor have an
addNotificationListener() and removeNotificationListener on its interface?
If that works as expected you'd just have to call the above methods and
implement the following interface:
| public interface RMINotificati
