Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

Page 1   2   3   4  
org.activemq.advisories.* (20)org.activemq.axis.* (1)org.activemq.benchmark.* (4)
org.activemq.broker.* (20)org.activemq.bug.* (2)org.activemq.capacity.* (6)
org.activemq.config.* (5)org.activemq.demo.* (4)org.activemq.filter.* (35)
org.activemq.gbean.* (8)

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


Package Samples:

org.activemq.broker.impl: The API for the JMS Broker which is the server side of a JMS network though it may be deployed inside a client in peer style networks.  
org.activemq.gbean.management: The JMS container using GBeaps for deployment in Geronimo or other JSR 77/88 based containers  
org.activemq.config
org.activemq.advisories
org.activemq.broker
org.activemq.capacity
org.activemq.filter
org.activemq.bug
org.activemq.demo
org.activemq.gbean
org.activemq.axis
org.activemq.benchmark

Classes:

ActiveMQMessage: The Message interface is the root interface of all JMS messages. It defines the message header and the acknowledge method used for all messages. Most message-oriented middleware (MOM) products treat messages as lightweight entities that consist of a header and a payload. The header contains fields used for message routing and identification; the payload contains the application data being sent. Within this general form, the definition of a message varies significantly across products. It would be quite difficult for the JMS API to support all of these message models. With this in mind, the JMS ...
ActiveMQSession: A Session object is a single-threaded context for producing and consuming messages. Although it may allocate provider resources outside the Java virtual machine (JVM), it is considered a lightweight JMS object. A session serves several purposes: It is a factory for its message producers and consumers. It supplies provider-optimized message factories. It is a factory for TemporaryTopics and TemporaryQueues . It provides a way to create Queue or Topic objects for those clients that need to dynamically manipulate provider-specific destination names. It supports a single series of transactions that ...
ActiveMQStreamMessage: A StreamMessage object is used to send a stream of primitive types in the Java programming language. It is filled and read sequentially. It inherits from the Message interface and adds a stream message body. Its methods are based largely on those found in java.io.DataInputStream and java.io.DataOutputStream . The primitive types can be read or written explicitly using methods for each type. They may also be read or written generically as objects. For instance, a call to StreamMessage.writeInt(6) is equivalent to StreamMessage.writeObject(new Integer(6)) . Both forms are provided, because the explicit ...
ActiveMQConnection: A Connection object is a client's active connection to its JMS provider. It typically allocates provider resources outside the Java virtual machine (JVM). Connections support concurrent use. A connection serves several purposes: It encapsulates an open connection with a JMS provider. It typically represents an open TCP/IP socket between a client and the service provider software. Its creation is where client authentication takes place. It can specify a unique client identifier. It provides a ConnectionMetaData object. It supports an optional ExceptionListener object. Because the creation of a connection ...
ActiveMQTopicSubscriber: A client uses a TopicSubscriber object to receive messages that have been published to a topic. A TopicSubscriber object is the publish/subscribe form of a message consumer. A MessageConsumer can be created by using Session.createConsumer . A TopicSession allows the creation of multiple TopicSubscriber objects per topic. It will deliver each message for a topic to each subscriber eligible to receive it. Each copy of the message is treated as a completely separate message. Work done on one copy has no effect on the others; acknowledging one does not acknowledge the others; one message may be delivered ...
MultiExpressionEvaluator: A MultiExpressionEvaluator is used to evaluate multiple expressions in single method call. Multiple Expression/ExpressionListener pairs can be added to a MultiExpressionEvaluator object. When the MultiExpressionEvaluator object is evaluated, all the registed Expressions are evaluated and then the associated ExpressionListener is invoked to inform it of the evaluation result. By evaluating multiple expressions at one time, some optimizations can be made to reduce the number of computations normally required to evaluate all the expressions. When this class adds an Expression it wrapps each node in ...
ActiveMQDestination: A Destination object encapsulates a provider-specific address. The JMS API does not define a standard address syntax. Although a standard address syntax was considered, it was decided that the differences in address semantics between existing message-oriented middleware (MOM) products were too wide to bridge with a single syntax. Since Destination is an administered object, it may contain provider-specific configuration information in addition to its address. The JMS API also supports a client's use of provider-specific address names. Destination objects support concurrent use. A Destination object ...
ActiveMQTopicPublisher: A client uses a TopicPublisher object to publish messages on a topic. A TopicPublisher object is the publish-subscribe form of a message producer. Normally, the Topic is specified when a TopicPublisher is created. In this case, an attempt to use the publish methods for an unidentified TopicPublisher will throw a java.lang.UnsupportedOperationException . If the TopicPublisher is created with an unidentified Topic , an attempt to use the publish methods that assume that the Topic has been identified will throw a java.lang.UnsupportedOperationException . During the execution of its publish method, ...
ActiveMQMapMessage: A MapMessage object is used to send a set of name-value pairs. The names are String objects, and the values are primitive data types in the Java programming language. The names must have a value that is not null, and not an empty string. The entries can be accessed sequentially or randomly by name. The order of the entries is undefined. MapMessage inherits from the Message interface and adds a message body that contains a Map. The primitive types can be read or written explicitly using methods for each type. They may also be read or written generically as objects. For instance, a call to MapMessage.setInt("foo", ...
ActiveMQBytesMessage: A BytesMessage object is used to send a message containing a stream of uninterpreted bytes. It inherits from the Message interface and adds a bytes message body. The receiver of the message supplies the interpretation of the bytes. The BytesMessage methods are based largely on those found in java.io.DataInputStream and java.io.DataOutputStream . This message type is for client encoding of existing message formats. If possible, one of the other self-defining message types should be used instead. Although the JMS API allows the use of message properties with byte messages, they are typically not ...
ActiveMQQueueSender: A client uses a QueueSender object to send messages to a queue. Normally, the Queue is specified when a QueueSender is created. In this case, an attempt to use the send methods for an unidentified QueueSender will throw a java.lang.UnsupportedOperationException . If the QueueSender is created with an unidentified Queue , an attempt to use the send methods that assume that the Queue has been identified will throw a java.lang.UnsupportedOperationException . During the execution of its send method, a message must not be changed by other threads within the client. If the message is modified, the result ...
ActiveMQXASession: The XASession interface extends the capability of Session by adding access to a JMS provider's support for the Java Transaction API (JTA) (optional). This support takes the form of a javax.transaction.xa.XAResource object. The functionality of this object closely resembles that defined by the standard X/Open XA Resource interface. An application server controls the transactional assignment of an XASession by obtaining its XAResource. It uses the XAResource to assign the session to a transaction, prepare and commit work on the transaction, and so on. An XAResource provides some fairly sophisticated ...
ActiveMQTopic: A Topic object encapsulates a provider-specific topic name. It is the way a client specifies the identity of a topic to JMS API methods. For those methods that use a Destination as a parameter, a Topic object may used as an argument . For example, a Topic can be used to create a MessageConsumer and a MessageProducer by calling: Session.CreateConsumer(Destination destination) Session.CreateProducer(Destination destination) Many publish/subscribe (pub/sub) providers group topics into hierarchies and provide various options for subscribing to parts of the hierarchy. The JMS API places no restriction ...
ActiveMQMessageProducer: A client uses a MessageProducer object to send messages to a destination. A MessageProducer object is created by passing a Destination object to a message-producer creation method supplied by a session. MessageProducer is the parent interface for all message producers. A client also has the option of creating a message producer without supplying a destination. In this case, a destination must be provided with every send operation. A typical use for this kind of message producer is to send replies to requests using the request's JMSReplyTo destination. A client can specify a default delivery mode, ...
ActiveMQMessageConsumer: A client uses a MessageConsumer object to receive messages from a destination. A MessageConsumer object is created by passing a Destination object to a message-consumer creation method supplied by a session. MessageConsumer is the parent interface for all message consumers. A message consumer can be created with a message selector. A message selector allows the client to restrict the messages delivered to the message consumer to those that match the selector. A client may either synchronously receive a message consumer's messages or have the consumer asynchronously deliver them as they arrive. ...
ActiveMQXAConnectionFactory: The XAConnectionFactory interface is a base interface for the XAQueueConnectionFactory and XATopicConnectionFactory interfaces. Some application servers provide support for grouping JTS capable resource use into a distributed transaction (optional). To include JMS API transactions in a JTS transaction, an application server requires a JTS aware JMS provider. A JMS provider exposes its JTS support using an XAConnectionFactory object, which an application server uses to create XAConnection objects. XAConnectionFactory objects are JMS administered objects, just like ConnectionFactory objects. It is ...
ActiveMQQueueReceiver: A client uses a QueueReceiver object to receive messages that have been delivered to a queue. Although it is possible to have multiple QueueReceiver s for the same queue, the JMS API does not define how messages are distributed between the QueueReceiver s. If a QueueReceiver specifies a message selector, the messages that are not selected remain on the queue. By definition, a message selector allows a QueueReceiver to skip messages. This means that when the skipped messages are eventually read, the total ordering of the reads does not retain the partial order defined by each message producer. Only ...
PropertiesConfigLoader: Parses a Properties object into a set of BrokerSecurityConfig and DestinationSecurityConfig objects that can be used to secure the ActiveMQ broker. Sample properties configuration: # Secure a connection the the 'localhost' broker connect.roles=admins,traders,brokers,guests # Secure the TEST_TOPIC topic. topic.T1.names=TEST_TOPIC topic.T1.consume.roles=traders topic.T1.produce.roles=traders,brokers topic.T1.send.roles=traders,brokers # You can also secure more than one destination in one go. queue.Q1.names=TEST_QUEUE,A_QUEUE,B_QUEUE queue.Q1.consume.roles=traders queue.Q1.produce.roles=traders,brokers ...
ActiveMQConnectionConsumer: For application servers, Connection objects provide a special facility for creating a ConnectionConsumer (optional). The messages it is to consume are specified by a Destination and a message selector. In addition, a ConnectionConsumer must be given a ServerSessionPool to use for processing its messages. Normally, when traffic is light, a ConnectionConsumer gets a ServerSession from its pool, loads it with a single message, and starts it. As traffic picks up, messages can back up. If this happens, a ConnectionConsumer can load each ServerSession with more than one message. This reduces the thread ...
ReadOnlyContext: A read-only Context This version assumes it and all its subcontext are read-only and any attempt to modify (e.g. through bind) will result in an OperationNotSupportedException. Each Context in the tree builds a cache of the entries in all sub-contexts to optimise the performance of lookup. This implementation is intended to optimise the performance of lookup(String) to about the level of a HashMap get. It has been observed that the scheme resolution phase performed by the JVM takes considerably longer, so for optimum performance lookups should be coded like: Context componentContext = (Context)new ...
TransactionContext: A TransactionContext provides the means to control a JMS transaction. It provides a local transaction interface and also an XAResource interface. An application server controls the transactional assignment of an XASession by obtaining its XAResource. It uses the XAResource to assign the session to a transaction, prepare and commit work on the transaction, and so on. An XAResource provides some fairly sophisticated facilities for interleaving work on multiple transactions, recovering a list of transactions in progress, and so on. A JTA aware JMS provider must fully implement this functionality. ...
ActiveMQObjectMessage: An ObjectMessage object is used to send a message that contains a serializable object in the Java programming language ("Java object"). It inherits from the Message interface and adds a body containing a single reference to an object. Only Serializable Java objects can be used. If a collection of Java objects must be sent, one of the Collection classes provided since JDK 1.2 can be used. When a client receives an ObjectMessage , it is in read-only mode. If a client attempts to write to the message at this point, a MessageNotWriteableException is thrown. If clearBody is called, the message can now ...
ActiveMQQueueBrowser: A client uses a QueueBrowser object to look at messages on a queue without removing them. The getEnumeration method returns a java.util.Enumeration that is used to scan the queue's messages. It may be an enumeration of the entire content of a queue, or it may contain only the messages matching a message selector. Messages may be arriving and expiring while the scan is done. The JMS API does not require the content of an enumeration to be a static snapshot of queue content. Whether these changes are visible or not depends on the JMS provider. A QueueBrowser can be created from either a Session or ...
ActiveMQTemporaryTopic: A TemporaryTopic object is a unique Topic object created for the duration of a Connection . It is a system-defined topic that can be consumed only by the Connection that created it. A TemporaryTopic object can be created either at the Session or TopicSession level. Creating it at the Session level allows the TemporaryTopic to participate in the same transaction with objects from the PTP domain. If a TemporaryTopic is created at the TopicSession , it will only be able participate in transactions with objects from the Pub/Sub domain.
ActiveMQQueue: A Queue object encapsulates a provider-specific queue name. It is the way a client specifies the identity of a queue to JMS API methods. For those methods that use a Destination as a parameter, a Queue object used as an argument. For example, a queue can be used to create a MessageConsumer and a MessageProducer by calling: Session.CreateConsumer(Destination destination) Session.CreateProducer(Destination destination) The actual length of time messages are held by a queue and the consequences of resource overflow are not defined by the JMS API.

Home | Contact Us | Privacy Policy | Terms of Service