In JMS, there are two types of destination: queues and topics. Each of these is associated with a specific messaging model, either point-to-point (for queues) or
publish-subscribe (for topics).
Although JMS provides a standard API for all Java applications wishing to participate in asynchronous communication, it can be a little cumbersome to use.
Spring eliminates the need for JMS boilerplate code and exception-handling code and makes asynchronous messaging easier to use.
本文章为转载内容，我们尊重原作者对文章享有的著作权。如有内容错误或侵权问题，欢迎原作者联系我们进行内容更正或删除文章。
