org.xmlBlaster.client.reader
Class SubscribeMessage

java.lang.Object
  org.xmlBlaster.client.reader.SubscribeMessage

All Implemented Interfaces:

I_Callback

public class SubscribeMessage
extends java.lang.Object
implements I_Callback

Subscribe from command line for a message.
Use this as a command line tool to subscribe for messages from xmlBlaster, for example for debugging reasons. Invoke examples:

    java org.xmlBlaster.client.reader.SubscribeMessage  -session.name Tim  -passwd  secret  -oid  __cmd:?totalMem
 

For other supported options type

    java org.xmlBlaster.client.reader.SubscribeMessage -?
 

Field Summary

private Global	glob
private static java.util.logging.Logger	log
private static java.lang.String	ME
private java.lang.String	subscriptionHandle
private I_XmlBlasterAccess	xmlBlasterConnection

Constructor Summary

SubscribeMessage(Global glob)
Constructs the SubscribeMessage object.

SubscribeMessage(Global glob, java.lang.String xmlKey, java.lang.String queryType)
Open the connection, and subscribe to the message

Method Summary

static void	main(java.lang.String[] args) Invoke: java org.xmlBlaster.client.reader.SubscribeMessage -loginName Tim -passwd secret -oid __cmd:?totalMem
private void	setUp() Sets up the fixture.
private java.lang.String	subscribe(java.lang.String xmlKey, java.lang.String queryType)
private void	tearDown() Logout from xmlBlaster
private void	unSubscribe(java.lang.String subscriptionId) Unsubscribe from given subscription
java.lang.String	update(java.lang.String loginName, 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.
private static void	usage() Command line usage.

Methods inherited from class java.lang.Object

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

Field Detail

ME

private static final java.lang.String ME

See Also:

Constant Field Values

glob

private final Global glob

log

private static java.util.logging.Logger log

xmlBlasterConnection

private I_XmlBlasterAccess xmlBlasterConnection

subscriptionHandle

private java.lang.String subscriptionHandle

Constructor Detail

SubscribeMessage

public SubscribeMessage(Global glob)
                 throws XmlBlasterException

Constructs the SubscribeMessage object.

Start with parameter -? to get a usage description.
These command line parameters are not merged with xmlBlaster.property properties.

Parameters:

args - Command line arguments

Throws:

XmlBlasterException

SubscribeMessage

public SubscribeMessage(Global glob,
                        java.lang.String xmlKey,
                        java.lang.String queryType)

Open the connection, and subscribe to the message

Method Detail

setUp

private void setUp()

Sets up the fixture.

Connect to xmlBlaster and login

tearDown

private void tearDown()

Logout from xmlBlaster

subscribe

private java.lang.String subscribe(java.lang.String xmlKey,
                                   java.lang.String queryType)

unSubscribe

private void unSubscribe(java.lang.String subscriptionId)

Unsubscribe from given subscription

Parameters:

subscriptionId - The id you got from your subscription

update

public java.lang.String update(java.lang.String loginName,
                               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:

loginName - 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

usage

private static void usage()

Command line usage.

main

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

Invoke: java org.xmlBlaster.client.reader.SubscribeMessage -loginName Tim -passwd secret -oid __cmd:?totalMem