javaclients
Class HelloWorldVolatile2

java.lang.Object
  javaclients.HelloWorldVolatile2

All Implemented Interfaces:

I_Callback

public class HelloWorldVolatile2
extends java.lang.Object
implements I_Callback

This client connects to xmlBlaster and publishes a volatile message.

Additionally the topic destroyDelay is reduced to 4 seconds, we can see in the xmlBlaster dump that the topic disappeared 4 seconds later.

 <qos>
   <expiration lifeTime='0' forceDestroy='true'/>
 </qos>
 

Invoke: java javaclients.HelloWorldVolatile2

Invoke: java javaclients.HelloWorldVolatile2 -session.name joe -passwd secret

See Also:

xmlBlaster interface, engine.message.lifecycle

Field Summary

private Global	glob
private static java.util.logging.Logger	log

Constructor Summary

HelloWorldVolatile2(Global glob)

Method Summary

static void	main(java.lang.String[] args) Try
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

Field Detail

glob

private final Global glob

log

private static java.util.logging.Logger log

Constructor Detail

HelloWorldVolatile2

public HelloWorldVolatile2(Global glob)

Method Detail

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

main

public static void main(java.lang.String[] args)

Try

   java javaclients.HelloWorldVolatile2 -help
 

for usage help