jms应用领域（JMS application area）.docVIP

jms应用领域（JMS application area） 1. selection of message types The text type, JMS message type Java object types, byte type, flow type, XML type, in the actual project, is the most widely used text types, object types and XML types of news. The proposal should not have object types, because if the object type, when debugging is very troublesome first of all, you have to write the test code specifically to send a message, second different versions, must manage objects belonging to the class of third, is not convenient to view the contents of news queue or topic. If the use of text type or XML type of message, it can be easily provided by JMS middleware management to send a test message, view the message content, and easier to manage different versions of the compatibility. If you have to use the object type of message, recommend the use of xStream objects into XML. 2. is the use of queue or topic? The definition is very clear, is also very easy to distinguish. But in the actual project, how to choose? My advice is to try to use queue. if you use the JMS project, then your system should be to be deployed in the environment of cluster scale. Topic will bring a lot of trouble in the cluster environment. For example, if you are using MDB to deal with topic, you have a MDB named SampleMDB, which in the way of aggregation are deployed on the A server and B server. Then it is possible with a topic message is the same at MDB two. Although some JMS middleware providers offer some solutions to solve this problem, such as the subsriber group, but it is developing and debugging have brought great trouble to the.Topic message is more complex than queue, the process is very difficult to track the topic message. So, if you do not have topic, how to realize the topic message processing of this nature? You can write a message to a queue transponder, the message is forwarded to all other queue attention in this queue. For example, there is a queue, called SampleQ1, a message sent to send