@Service @Configurable public class ClusterTopic<X extends java.io.Serializable> extends ClusterTopicImpl<X>
Following example shows how to make two nodes in resin cluster
communicate between each other using cluster topic.
This example makes use of Candi
Resin's dependency injection implementation.
1. ClusterTopic Configuration
<registry>
<resin xmlns="http://caucho.com/ns/resin"
xmlns:jms="urn:java:com.caucho.jms">
<cluster id="">
<server id="a" port="6700"/>
<server id="b" port="6701"/>
<host id="">
<web-app id="">
<jms:ClusterTopic>
<jms:name>server_topic</jms:name>
</jms:ClusterTopic>
</web-app>
</host>
</cluster>
</resin>
</registry>
Above configurations would make ClusterTopic to run on nodes 'a' and 'b'.2. Executing following lines of code on node 'a', would make node 'a' as the subscriber to the Topic:
| Constructor and Description |
|---|
ClusterTopic() |
acknowledge, close, closeSubscriber, createSubscriber, destroy, getUrl, hasMessage, init, notifyMessageAvailable, receiveLocal, removeCluster, rollback, send, sendLocal, sendLocalAsBackup, setCluster, setPath, subscribeTopicdrainTo, drainTo, iterator, offer, offer, peek, poll, poll, postConstruct, put, receive, remainingCapacity, setTopicName, size, takegenerateMessageID, generateMessageID, getJMSDestination, getName, getQueueName, getTopicName, hasMessage, setName, setSerializationHandle, toStringcontains, containsAll, isEmpty, remove, removeAll, retainAll, toArray, toArrayclone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitgetTopicName, toString