Stream Messages - Group of Java Primitives
Map Messages - Name Value Pairs. Name being a string& Value being a java primitive
Text Messages - String messages (since being widely used a separate messaging Type has been supported)
Object Messages - Group of serialize able java object
Bytes Message - Stream of uninterrupted bytes
0 Comments
It is according to the specification that the message sent should be received in the same format. A non-java client cannot receive a message in the form of java object. The provider in between handles the conversion of the data type and the message is transferred to the other end. MDB is Message driven bean, which very much resembles the Stateless session bean. The incoming and out going messages can be handled by the Message driven bean. The ability to communicate asynchronously is the special feature about the Message driven bean. There are two kinds of Messaging. Each JMS-enabled client must establish the following: JMS is loosely coupled and RMI (remote method invocation) is tightly coupled (dependency between objects). In RMI, the senders have to wait for the immediate response from the receiver. 1) Point-to-Point 2) Publish and Subscribe. Consumers can filter messages using message selector. Developer has to specify a message selector (String) as an argument when we create a message consumer. Using “durable subscription”, the subscribers can receive messages sent even when the subscribers are not active. Header, Properties and Body. |
ArchivesCategories |