org.xmlBlaster.client.jmx
Class NotificationHandler

java.lang.Object
  org.xmlBlaster.client.jmx.NotificationHandler

All Implemented Interfaces:

I_Callback

public class NotificationHandler
extends java.lang.Object
implements I_Callback

Client-sided NotificationHandler
Takes subscribtions to Notifications from clients. Invokes a server-sided
subscription

Update is called, whenever a Notification-event is sent back from the server

Constructor Summary

NotificationHandler(java.lang.String strObjectName, java.lang.String className, org.xmlBlaster.jmxgui.JmxPlugin panel, AsyncMBeanServer server)

Method Summary

void	unregister()
java.lang.String	update(java.lang.String cbSessionId, UpdateKey updateKey, byte[] content, UpdateQos updateQos) This is the callback method invoked from I_XmlBlasterAccess informing the client in an asynchronous mode about a new message.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

NotificationHandler

public NotificationHandler(java.lang.String strObjectName,
                           java.lang.String className,
                           org.xmlBlaster.jmxgui.JmxPlugin panel,
                           AsyncMBeanServer server)

Method Detail

unregister

public void unregister()

update

public java.lang.String update(java.lang.String cbSessionId,
                               UpdateKey updateKey,
                               byte[] content,
                               UpdateQos updateQos)

Description copied from interface: I_Callback

This is the callback method invoked from I_XmlBlasterAccess informing the client in an asynchronous mode about a new message.

So you should implement in your client code the I_Callback interface - suppling the update() method where you can do with the message whatever you want.

The raw protocol driver specific update() method (e.g. CORBA-BlasterCallback.update()) is unpacked and for each arrived message this update is called.

Specified by:

update in interface I_Callback

Parameters:

cbSessionId - The session ID specified by the client which registered the callback. You can specify a cbSessionId during connection (with ConnectQos) and this is bounced back here so you can authenticate the message.

updateKey - The arrived key containing the topic name

content - The arrived message content. This is your payload.

See Also:

I_XmlBlasterAccess