Home >> All >> org >> activemq >> [ service Javadoc ]

•

org.activemq.service.boundedvm.* (12)

•

org.activemq.service.impl.* (28)

• org.activemq.service: Javadoc index of package org.activemq.service.


Package Samples:

• org.activemq.service.impl: The core services which make up the JMS Message Broker such as the Store, MessageContainer and MessageContainerManager  
• org.activemq.service.boundedvm

Classes:

• InitialImageMessageContainerManager: Implements an initial image service where on subscription the client will receive the last image that was previously cached. This is very useful in financial market data and in rapidly changing transient event models where you don't want to persist messages when you are away, but wish to cache the last image, per destination around so that when a new reliable consumer subscribes you receive the latest value you may have missed. This is especially true in finance with slow moving markets where you may have to wait a while for an update (or times when you subscribe after market close etc).
• DurableTopicMessageContainer: A default implementation of a Durable Topic based org.activemq.service.MessageContainer which acts as an adapter between the org.activemq.service.MessageContainerManager requirements and those of the persistent org.activemq.store.TopicMessageStore implementations.
• DurableQueueMessageContainer: A default implementation of a Durable Queue based org.activemq.service.MessageContainer which acts as an adapter between the org.activemq.service.MessageContainerManager requirements and those of the persistent org.activemq.store.MessageStore implementations.
• MessageIdentity: Represents a message identity, either by using a unique message number, which is ordered and must not be zero or by specifying the String messageID. Typically a client accessing the MessageStore may have one or the other. Depending on which one is specified the other value may be filled in by operations on the MessageStore
• RedeliveryPolicy: Represents the redelivery policy which is used when a rollback() occurs (either JMS or XA). Various options are possible which this policy tries to capture the main variants. If enabled, a typical redelivery policy could be to use a back-off timeout period.
• DefaultQueueList: Linked list class to provide uniformly named methods to get , remove and insert an element at the beginning and end of the list. These operations allow linked lists to be used as a stack, queue, or double-ended queue (dequeue).
• ProxyMessageContainerManager: A Proxy implementation of org.activemq.service.MessageContainerManager which delegates to some other implementation which is useful for writing Facade implementations
• Service: Service represents some service of some kind with a simple start/stop lifecycle. Note that usually once a service has been stopped it should be discarded and a new service instance created again.
• TransactionTask: The TransactionTask interface should be implemented by any class whose instances are intended to be executed as part of a transaction event. The class must define a method of no arguments called execute.
• DurableTopicSubscriptionContainerImpl: An implemenation of SubscriptionContainerImpl for durable topic subscriptions
• Dispatcher: A dispatcher of messages to some JMS connection. Typically this uses either IO or NIO to shovel the messages down a socket as fast as possible - in either a push or pull way.
• DispatcherImpl: A dispatcher of messages to some JMS connection. Typically this uses either IO or NIO to shovel the messages down a socket as fast as possible - in either a push or pull way.
• DurableMessagePointer: DurableMessagePointers are moved around in the DurableQueueBoundedMessageManager so that we remember the associated messageStore that the message has been persisted to.
• QueueList: Represents a Queue with List like semantics, allowing addition and removal at any point in the queue. Typically this will be implemented using some kind of LinkedList
• DurableTopicSubscription: Represents a durable topic subscription where the consumer has a unique clientID used to persist the messages across both Broker restarts and JMS client restarts
• SubscriptionContainerImpl: A default RAM only implementation of the org.activemq.service.SubscriptionContainer
• QueueMessageContainer: A Queue based MessageContainer
• TopicMessageContainer: A Topic based MessageContainer
• SubscriberEntry: Represents a durable subscribers subscription entry which contains details of the subscription and the subscriber's unique ID
• TransientTopicBoundedMessageContainer: A MessageContainer for transient topics One of these exists for every active Connection consuming transient Topic messages
• QueueListSupport: A base class which is useful for implementation inheritence when implementing a persistent QueueList
• Transaction: A Transaction keeps track of all the tasks that must be run before and after transactional events.
• TransactionManager: A Transaction keeps track of all the tasks that must be run before and after transactional events.
• AbstractTransaction: Keeps track of all the actions the need to be done when a transaction does a commit or rollback.
• AutoCommitTransaction: Keeps track of all the actions the need to be done when a transaction does a commit or rollback.

Home | Contact Us | Privacy Policy | Terms of Service