Using Spring and AMQP to send and receive messages in java (Part 2)
The previous article talked about using RabbitMQ to send messages, and this article will talk about receiving messages.
In traditional JMS, there are two ways to obtain information from the queue, the synchronous method using JmsTemplate and the asynchronous method using message-driven pojo. Spring AMQP also provides a similar way to obtain messages sent via AMQP.
Use RabbitTemplate to receive messages
The simplest method of receiving information provided by RabbitTemplate is the receive() method, through which you can obtain a Message object from the queue:
Message message = rabbit.receive("spittle.test.queue");
Or you can also obtain the default queue of messages through configuration. This is achieved by setting the queue attribute when configuring the template:
<template></template>
This way If so, when calling the receive() method, the message can be obtained from the default queue without setting any parameters:
Message message = rabbit.receive( );
After obtaining the Message object, you generally need to set its body attribute Convert the byte array in to the desired object. Just like converting the domain object to the Message when sending, converting the received Message to the domain object is also tedious. Here you can consider using RabbitTemplate's receiveAndConvert() method as an alternative:
Spittle spittle = (Spittle) rabbit.receiveAndConvert("spittle.test.queue");
The receiveAndConvert() method will use the same message converter as the sendAndConvert() method to convert the Message object into the original type.
Calling the receive() and receiveAndConvert() methods will return immediately. If there are no waiting messages in the queue, you will get null. At this time, programmers generally need to manage polling and necessary threads themselves to implement queue monitoring. If you don't want to poll synchronously every time to wait for the message to arrive, you can use the message-driven pojo provided by Spring AMQP. Let's take a look at using the message-driven pojo to receive messages.
Use message-driven pojo to receive messages
If you want to consume Spittle objects asynchronously in message-driven pojo, you must first solve the pojo itself, as shown below SpittleTestHandler Playing this role:
public class SpittleTestHandler {public void handleSpittleTest (Spittle spittle) { ... } }
In fact, this class does not depend on AMQP. No matter what mechanism is passed to the Spittle object, it can handle it.
Here you also need to declare SpittleTestHandler as a bean in the Spring application context:
<bean></bean>
Finally, declare a listener container and listener, which can be called when the message arrives SpittleTestHandler, the configuration is as follows:
<listener-container><listener></listener></listener-container>
The
The above is the detailed content of Using Spring and AMQP to send and receive messages in java (Part 2). For more information, please follow other related articles on the PHP Chinese website!

JVMmanagesgarbagecollectionacrossplatformseffectivelybyusingagenerationalapproachandadaptingtoOSandhardwaredifferences.ItemploysvariouscollectorslikeSerial,Parallel,CMS,andG1,eachsuitedfordifferentscenarios.Performancecanbetunedwithflagslike-XX:NewRa

Java code can run on different operating systems without modification, because Java's "write once, run everywhere" philosophy is implemented by Java virtual machine (JVM). As the intermediary between the compiled Java bytecode and the operating system, the JVM translates the bytecode into specific machine instructions to ensure that the program can run independently on any platform with JVM installed.

The compilation and execution of Java programs achieve platform independence through bytecode and JVM. 1) Write Java source code and compile it into bytecode. 2) Use JVM to execute bytecode on any platform to ensure the code runs across platforms.

Java performance is closely related to hardware architecture, and understanding this relationship can significantly improve programming capabilities. 1) The JVM converts Java bytecode into machine instructions through JIT compilation, which is affected by the CPU architecture. 2) Memory management and garbage collection are affected by RAM and memory bus speed. 3) Cache and branch prediction optimize Java code execution. 4) Multi-threading and parallel processing improve performance on multi-core systems.

Using native libraries will destroy Java's platform independence, because these libraries need to be compiled separately for each operating system. 1) The native library interacts with Java through JNI, providing functions that cannot be directly implemented by Java. 2) Using native libraries increases project complexity and requires managing library files for different platforms. 3) Although native libraries can improve performance, they should be used with caution and conducted cross-platform testing.

JVM handles operating system API differences through JavaNativeInterface (JNI) and Java standard library: 1. JNI allows Java code to call local code and directly interact with the operating system API. 2. The Java standard library provides a unified API, which is internally mapped to different operating system APIs to ensure that the code runs across platforms.

modularitydoesnotdirectlyaffectJava'splatformindependence.Java'splatformindependenceismaintainedbytheJVM,butmodularityinfluencesapplicationstructureandmanagement,indirectlyimpactingplatformindependence.1)Deploymentanddistributionbecomemoreefficientwi

BytecodeinJavaistheintermediaterepresentationthatenablesplatformindependence.1)Javacodeiscompiledintobytecodestoredin.classfiles.2)TheJVMinterpretsorcompilesthisbytecodeintomachinecodeatruntime,allowingthesamebytecodetorunonanydevicewithaJVM,thusfulf


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

WebStorm Mac version
Useful JavaScript development tools

MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment

SublimeText3 Chinese version
Chinese version, very easy to use

PhpStorm Mac version
The latest (2018.2.1) professional PHP integrated development tool
