Interested to Buy Any Domain ? << Click Here >> for more details...
Answer Posted / munnu
ObjectMessage contains a Serializable java object as it's payload. Thus it allows exchange of Java objects between applications. This in itself mandates that both the applications be Java applications. The consumer of the message must typecast the object received to it's appropriate type. Thus the consumer should before hand know the actual type of the object sent by the sender. Wrong type casting would result in ClassCastException. Moreover the class definition of the object set in the payload should be available on both the machine, the sender as well as the consumer. If the class definition is not available in the consumer machine, an attempt to type cast would result in ClassNotFoundException. Some of the MOMs might support dynamic loading of the desired class over the network, but the JMS specification does not mandate this behavior and would be a value added service if provided by your vendor. And relying on any such vendor specific functionality would hamper the portability of your application. Most of the time the class need to be put in the classpath of both, the sender and the consumer, manually by the developer.
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
Explain about message selector?
What is the point-to-point model in jms?
Can we use jms for sending automated e-mails?
What does jms stand for?
What is jms endpoint?
Explain about JMS queue?
Name the messaging types supported by jms.
In which situations we are using jms?
Does kafka support jms?
Can we have more than one consumer for a jms queue?
Is jms a message broker?
What is jms consumer?
What is a jms listener?
Which are the benefits of mdb (message driven beans) over standard jms consumers?
What are the types of messages that are supported by JMS?
