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

Quick Search    Search Deep

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


Package Samples:

org.activemq.message

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 ...
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 ...
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 ...
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 ...
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 ...
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 ...
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.
ActiveMQTemporaryQueue: A TemporaryQueue object is a unique Queue object created for the duration of a Connection . It is a system-defined queue that can be consumed only by the Connection that created it. A TemporaryQueue object can be created at either the Session or QueueSession level. Creating it at the Session level allows to the TemporaryQueue to participate in transactions with objects from the Pub/Sub domain. If it is created at the QueueSession , it will only be able participate in transactions with objects from the PTP domain.
ActiveMQTextMessage: A TextMessage object is used to send a message containing a java.lang.String . It inherits from the Message interface and adds a text message body. This message type can be used to transport text-based messages, including those with XML content. When a client receives a TextMessage , 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 be both read from and written to.
ActiveMQXid: A ActiveMQXid object holds the distributed transaction id that is passed around in an ActiveMQ system. Eventhough a Transaction Manager (TM) has his own Xid implementation that he uses when he talks to the our ActiveMQXAResource, we need to send the Xid data down to the server in our format. ActiveMQ uses Strings as the transaction id. This class coverts an Xid to and from a string.
ActiveMQBytesMessageTest: To change the template for this generated type comment go to Window - Preferences - Java - Code Generation - Code and Comments
ActiveMQMapMessageTest: To change the template for this generated type comment go to Window - Preferences - Java - Code Generation - Code and Comments
ActiveMQMessageTest: To change the template for this generated type comment go to Window - Preferences - Java - Code Generation - Code and Comments
ActiveMQStreamMessageTest: To change the template for this generated type comment go to Window - Preferences - Java - Code Generation - Code and Comments
ActiveMQTextMessageTest: To change the template for this generated type comment go to Window - Preferences - Java - Code Generation - Code and Comments
KeepAlive: Keep-alive packet which holds not information and is only intended to keep connections from being idle.
ReceiptHolder: ReceiptHolder is a utility class used for waiting for receipts from Packets sent to the broker
Packet: Denotes an object that can be serialized/deserailized using a PacketReader or PacketWriter
MessageAck: Denotes an object that can be serialized/deserailized using a PacketReader/PacketWriter
CleanupConnectionInfo: Denotes an object that can be serialized/deserailized using a Packet Reader/Writer
SessionInfo: Denotes an object that can be serialized/deserailized using a Packet Reader/Writer
CapacityInfoRequest: Request nfomation about the Capacity for more messages for a Connection/Broker
BodyPacket: Represents a polymorphic interface for any packet or message which has a body

Home | Contact Us | Privacy Policy | Terms of Service