Summary
In this chapter, you learned the concepts of JMS programming and the basics of JMS API programming techniques. I started this chapter by explaining the definition of a messaging service and its major features. The messaging system is based on message-oriented middleware (MOM), which was explained in the previous chapter. Advantages and disadvantages of using a messaging system were then discussed prior to providing information about the JMS API.
The JMS API, which is built onto the J2EE 1.3 platform specifications, covers point-to-point and publish-and-subscriber messaging models used in MOM providers.
In this chapter, you learned the concepts of JMS programming including its architecture, message consumption, destination, connection factory, connection, session, message producer, message consumer, and message listener.
I also showed you how to create two administered objects, ConnectionFactory and Destination, and how to use them in JMS messaging applications.
I explained synchronous messaging and asynchronous messaging and compared the two models. You also learned about message structure and different message types in the JMS specifications.
Although I provided some information about JMS programming concepts and techniques, more details such as methods of some interfaces are discussed in Appendix D. Many concepts were explained using a few sample lines of code, but you can find complete and more valuable examples in the next chapter.