xmlBlaster 2.1.0 API

org.xmlBlaster.test.qos
Class TestCallback

java.lang.Object
  extended by junit.framework.Assert
      extended by junit.framework.TestCase
          extended by org.xmlBlaster.test.qos.TestCallback
All Implemented Interfaces:
junit.framework.Test, I_Callback

public class TestCallback
extends junit.framework.TestCase
implements I_Callback

This client test dead letter generation on callback problems.

Works only if callback server is a separate instance (Corba is OK, but not SOCKET).

This client may be invoked multiple time on the same xmlBlaster server, as it cleans up everything after his tests are done.


Field Summary
private  I_XmlBlasterAccess conAdmin
           
private  Global glob
           
private  boolean isDeadMessage
           
private  boolean isSocket
           
private static java.util.logging.Logger log
           
private static java.lang.String ME
           
private  java.lang.String name
           
private  int numReceived
           
private  java.lang.String passwd
           
private  java.lang.String publishOid
           
private  java.lang.String subscribeDeadMessageOid
           
 
Constructor Summary
TestCallback(Global glob, java.lang.String testName, java.lang.String name)
          Constructs the TestCallback object.
 
Method Summary
static void main(java.lang.String[] args)
          Invoke:
protected  void setUp()
          Sets up the fixture.
static junit.framework.Test suite()
          Method is used by TestRunner to load these tests
protected  void tearDown()
          Tears down the fixture.
 void testCallbackFailure()
          We expect dead letters after destroying our callback server.
 java.lang.String update(java.lang.String cbSessionId, UpdateKey updateKey, byte[] content, UpdateQos updateQos)
          This is the callback method invoked from xmlBlaster delivering us a new asynchronous message.
private  void waitOnUpdate(long timeout, int numWait)
          Little helper, waits until the wanted number of messages are arrived or returns when the given timeout occurs.
 
Methods inherited from class junit.framework.TestCase
countTestCases, createResult, getName, run, run, runBare, runTest, setName, toString
 
Methods inherited from class junit.framework.Assert
assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertFalse, assertFalse, assertNotNull, assertNotNull, assertNotSame, assertNotSame, assertNull, assertNull, assertSame, assertSame, assertTrue, assertTrue, fail, fail
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
 

Field Detail

ME

private static java.lang.String ME

glob

private final Global glob

log

private static java.util.logging.Logger log

name

private java.lang.String name

passwd

private java.lang.String passwd

numReceived

private int numReceived

isDeadMessage

private boolean isDeadMessage

subscribeDeadMessageOid

private java.lang.String subscribeDeadMessageOid

conAdmin

private I_XmlBlasterAccess conAdmin

publishOid

private java.lang.String publishOid

isSocket

private boolean isSocket
Constructor Detail

TestCallback

public TestCallback(Global glob,
                    java.lang.String testName,
                    java.lang.String name)
Constructs the TestCallback object.

Parameters:
testName - The name used in the test suite
name - The name to login to the xmlBlaster
Method Detail

setUp

protected void setUp()
Sets up the fixture.

Connect to xmlBlaster and login as admin, subscribe to dead letters

Overrides:
setUp in class junit.framework.TestCase

tearDown

protected void tearDown()
Tears down the fixture.

cleaning up .... erase() the previous message OID and logout

Overrides:
tearDown in class junit.framework.TestCase

testCallbackFailure

public void testCallbackFailure()
We expect dead letters after destroying our callback server.


update

public java.lang.String update(java.lang.String cbSessionId,
                               UpdateKey updateKey,
                               byte[] content,
                               UpdateQos updateQos)
This is the callback method invoked from xmlBlaster delivering us a new asynchronous message.

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_Callback.update(String, UpdateKey, byte[], UpdateQos)

waitOnUpdate

private void waitOnUpdate(long timeout,
                          int numWait)
Little helper, waits until the wanted number of messages are arrived or returns when the given timeout occurs.

Parameters:
timeout - in milliseconds
numWait - how many messages to wait

suite

public static junit.framework.Test suite()
Method is used by TestRunner to load these tests


main

public static void main(java.lang.String[] args)
Invoke:
  java -Djava.compiler= junit.textui.TestRunner org.xmlBlaster.test.qos.TestCallback

  java org.xmlBlaster.test.qos.TestCallback -dispatch/callback/retries 0 -dispatch/callback/delay 3000
 


xmlBlaster 2.1.0 API

Copyright © 1999-2011 The xmlBlaster.org contributers.