If you are not familiar with Spring 5, it is recommended that you review the Spring 5 Features.<\/p>\n
Spring WebFlux is a reactive web framework<\/a> provided by Spring.<\/h2>\n![\"spring](\"https:\/\/cdn.silicloud.com\/blog-img\/blog\/img\/655ccde8c40ba52feef2849b\/6-0.png\" "\\"\\"")
<\/div>\n\n- \n
Mono implements the Publisher interface and returns either 0 or 1 element.<\/ol>\n<\/li>\n<\/ol>\n <\/p>\n
Flux implements the Publisher interface and returns multiple (N) elements.<\/ol>\nExample of a Hello World application using Spring WebFlux<\/h2>\n![\"spring](\"https:\/\/cdn.silicloud.com\/blog-img\/blog\/img\/655ccde8c40ba52feef2849b\/9-0.png\" "\\"\\"")
<\/div>\nDependencies for Spring WebFlux in Maven.<\/h3>\n<project xmlns=\"https:\/\/maven.apache.org\/POM\/4.0.0\" xmlns:xsi=\"https:\/\/www.w3.org\/2001\/XMLSchema-instance\" xsi:schemaLocation=\"https:\/\/maven.apache.org\/POM\/4.0.0 https:\/\/maven.apache.org\/xsd\/maven-4.0.0.xsd\">\r\n <modelVersion>4.0.0<\/modelVersion>\r\n <groupId>com.scdev.spring<\/groupId>\r\n <artifactId>SpringWebflux<\/artifactId>\r\n <version>0.0.1-SNAPSHOT<\/version>\r\n <name>Spring WebFlux<\/name>\r\n <description>Spring WebFlux Example<\/description>\r\n \r\n <properties>\r\n <project.build.sourceEncoding>UTF-8<\/project.build.sourceEncoding>\r\n <project.reporting.outputEncoding>UTF-8<\/project.reporting.outputEncoding>\r\n <jdk.version>1.9<\/jdk.version>\r\n <\/properties>\r\n \r\n <parent>\r\n\t\t<groupId>org.springframework.boot<\/groupId>\r\n\t\t<artifactId>spring-boot-starter-parent<\/artifactId>\r\n\t\t<version>2.0.1.RELEASE<\/version>\r\n\t\t<relativePath\/> <!-- lookup parent from repository -->\r\n\t<\/parent>\r\n\r\n\t<dependencies>\r\n\t\t<dependency>\r\n\t\t\t<groupId>org.springframework.boot<\/groupId>\r\n\t\t\t<artifactId>spring-boot-starter-webflux<\/artifactId>\r\n\t\t<\/dependency>\r\n\t\t<dependency>\r\n\t\t\t<groupId>org.springframework.boot<\/groupId>\r\n\t\t\t<artifactId>spring-boot-starter-test<\/artifactId>\r\n\t\t\t<scope>test<\/scope>\r\n\t\t<\/dependency>\r\n\r\n\t\t<dependency>\r\n\t\t\t<groupId>io.projectreactor<\/groupId>\r\n\t\t\t<artifactId>reactor-test<\/artifactId>\r\n\t\t\t<scope>test<\/scope>\r\n\t\t<\/dependency>\r\n <\/dependencies>\r\n\t<repositories>\r\n\t\t<repository>\r\n\t\t\t<id>spring-snapshots<\/id>\r\n\t\t\t<name>Spring Snapshots<\/name>\r\n\t\t\t<url>https:\/\/repo.spring.io\/snapshot<\/url>\r\n\t\t\t<snapshots>\r\n\t\t\t\t<enabled>true<\/enabled>\r\n\t\t\t<\/snapshots>\r\n\t\t<\/repository>\r\n\t\t<repository>\r\n\t\t\t<id>spring-milestones<\/id>\r\n\t\t\t<name>Spring Milestones<\/name>\r\n\t\t\t<url>https:\/\/repo.spring.io\/milestone<\/url>\r\n\t\t\t<snapshots>\r\n\t\t\t\t<enabled>false<\/enabled>\r\n\t\t\t<\/snapshots>\r\n\t\t<\/repository>\r\n\t<\/repositories>\r\n\t<pluginRepositories>\r\n\t\t<pluginRepository>\r\n\t\t\t<id>spring-snapshots<\/id>\r\n\t\t\t<name>Spring Snapshots<\/name>\r\n\t\t\t<url>https:\/\/repo.spring.io\/snapshot<\/url>\r\n\t\t\t<snapshots>\r\n\t\t\t\t<enabled>true<\/enabled>\r\n\t\t\t<\/snapshots>\r\n\t\t<\/pluginRepository>\r\n\t\t<pluginRepository>\r\n\t\t\t<id>spring-milestones<\/id>\r\n\t\t\t<name>Spring Milestones<\/name>\r\n\t\t\t<url>https:\/\/repo.spring.io\/milestone<\/url>\r\n\t\t\t<snapshots>\r\n\t\t\t\t<enabled>false<\/enabled>\r\n\t\t\t<\/snapshots>\r\n\t\t<\/pluginRepository>\r\n\t<\/pluginRepositories>\r\n <build>\r\n <plugins>\r\n <plugin>\r\n <groupId>org.springframework.boot<\/groupId>\r\n <artifactId>spring-boot-maven-plugin<\/artifactId>\r\n <\/plugin>\r\n <\/plugins>\r\n <pluginManagement>\r\n <plugins>\r\n <plugin>\r\n <groupId>org.apache.maven.plugins<\/groupId>\r\n <artifactId>maven-compiler-plugin<\/artifactId>\r\n <version>3.7.0<\/version>\r\n <configuration>\r\n <source>${jdk.version}<\/source>\r\n <target>${jdk.version}<\/target>\r\n <\/configuration>\r\n <\/plugin>\r\n <\/plugins>\r\n <\/pluginManagement>\r\n <\/build>\r\n \r\n<\/project>\r\n<\/code><\/pre>\nThe pivotal dependencies are spring-boot-starter-webflux and spring-boot-starter-parent, while other dependencies serve for the creation of JUnit test scenarios.<\/p>\n
Spring WebFlux Handler can be rephrased as “Handler for Spring WebFlux.”<\/h3>\n
The Handler method of Spring WebFlux manages the request and provides a Mono or Flux as the response.<\/p>\n
package com.scdev.spring.component;\r\n\r\nimport org.springframework.http.MediaType;\r\nimport org.springframework.stereotype.Component;\r\nimport org.springframework.web.reactive.function.BodyInserters;\r\nimport org.springframework.web.reactive.function.server.ServerRequest;\r\nimport org.springframework.web.reactive.function.server.ServerResponse;\r\n\r\nimport reactor.core.publisher.Mono;\r\n\r\n@Component\r\npublic class HelloWorldHandler {\r\n\r\n\tpublic Mono<ServerResponse> helloWorld(ServerRequest request) {\r\n\t\treturn ServerResponse.ok().contentType(MediaType.TEXT_PLAIN)\r\n\t\t\t.body(BodyInserters.fromObject(\"Hello World!\"));\r\n\t}\r\n}\r\n<\/code><\/pre>\nTake note that the Mono reactive component contains the body of the ServerResponse. Additionally, observe the sequence of functions used to establish the content type, response code, and body of the returned response.<\/p>\n
The Spring WebFlux Router is to be rephrased natively.<\/h3>\n
One possible option:
\nRouter for Spring WebFlux in Spring’s framework for reactive web applications.<\/p>\n
Router methods are employed to establish routes for the application. These methods generate a RouterFunction object which also encapsulates the ServerResponse body.<\/p>\n
package com.scdev.spring.component;\r\n\r\nimport org.springframework.context.annotation.Bean;\r\nimport org.springframework.context.annotation.Configuration;\r\nimport org.springframework.http.MediaType;\r\nimport org.springframework.web.reactive.function.server.RequestPredicates;\r\nimport org.springframework.web.reactive.function.server.RouterFunction;\r\nimport org.springframework.web.reactive.function.server.RouterFunctions;\r\nimport org.springframework.web.reactive.function.server.ServerResponse;\r\n\r\n@Configuration\r\npublic class HelloWorldRouter {\r\n\r\n\t@Bean\r\n\tpublic RouterFunction<ServerResponse> routeHelloWorld(HelloWorldHandler helloWorldHandler) {\r\n\r\n\t\treturn RouterFunctions.route(RequestPredicates.GET(\"\/helloWorld\")\r\n .and(RequestPredicates.accept(MediaType.TEXT_PLAIN)), helloWorldHandler::helloWorld);\r\n\t}\r\n}\r\n<\/code><\/pre>\nWe have set up a GET endpoint at \/helloWorld which will provide a plain text response when called by the client.<\/p>\n
A Spring Boot Application<\/h3>\n
We need to set up our basic WebFlux application using Spring Boot.<\/p>\n
package com.scdev.spring;\r\n\r\nimport org.springframework.boot.SpringApplication;\r\nimport org.springframework.boot.autoconfigure.SpringBootApplication;\r\n\r\n@SpringBootApplication\r\npublic class Application {\r\n\r\n\tpublic static void main(String[] args) {\r\n\t\tSpringApplication.run(Application.class, args);\r\n\t}\r\n}\r\n<\/code><\/pre>\nBy examining the code above, it is apparent that there is no reference to Spring WebFlux. However, Spring Boot will automatically set up our application as Spring WebFlux because we have included the dependency of the spring-boot-starter-webflux module.<\/p>\n
Support for Java 9 Modules<\/h3>\n
If you are using Java 8, our application is prepared to run. However, if you are using Java 9, we will also need to incorporate the module-info.java class.<\/p>\n
module com.scdev.spring {\r\n requires reactor.core;\r\n requires spring.web;\r\n requires spring.beans;\r\n requires spring.context;\r\n requires spring.webflux;\r\n requires spring.boot;\r\n requires spring.boot.autoconfigure;\r\n exports com.scdev.spring;\r\n}\r\n<\/code><\/pre>\nStarting the Spring WebFlux Spring Boot Application.<\/h3>\n![\"Eclipse](\"https:\/\/cdn.silicloud.com\/blog-img\/blog\/img\/655ccde8c40ba52feef2849b\/29-0.png\" "\\"\\"")
<\/div>\n2018-05-07 15:01:47.893 INFO 25158 --- [ main] o.s.w.r.f.s.s.RouterFunctionMapping : Mapped ((GET && \/helloWorld) && Accept: [text\/plain]) -> com.scdev.spring.component.HelloWorldRouter$$Lambda$501\/704766954@6eeb5d56\r\n2018-05-07 15:01:48.495 INFO 25158 --- [ctor-http-nio-1] r.ipc.netty.tcp.BlockingNettyContext : Started HttpServer on \/0:0:0:0:0:0:0:0:8080\r\n2018-05-07 15:01:48.495 INFO 25158 --- [ main] o.s.b.web.embedded.netty.NettyWebServer : Netty started on port(s): 8080\r\n2018-05-07 15:01:48.501 INFO 25158 --- [ main] com.scdev.spring.Application : Started Application in 1.86 seconds (JVM running for 5.542)\r\n<\/code><\/pre>\nBased on the logs, it’s evident that our application is operational on the Netty server, specifically on port 8080. Now, we can proceed with testing the app.<\/p>\n
Test for a Spring WebFlux application.<\/h3>\n
We have the ability to test our app using different techniques.<\/p>\n
\n- \n
Using the CURL command, you can send a request to the specified URL and receive the response “Hello World!”.<\/ol>\n<\/li>\n<\/ol>\nAlternatively, you can launch the URL in a browser.<\/p>\n
To test a Rest web service using WebTestClient from Spring 5 reactive web, you can use the provided JUnit test program. This program sends a GET request to the specified URI and checks if the response status is OK and the response body is “Hello World!”.<\/p>\n
Another option is to use WebClient from Spring Web Reactive to call the REST web service. This program sends a GET request to the specified URI and retrieves the response body as a string.<\/p>\n
Running these programs will give you the expected output and any relevant debug messages.<\/p>\n
Please provide the text that you want me to paraphrase.<\/h2>\n
This article discussed Spring WebFlux and how to create a basic reactive Restful web service. It’s great to see that well-known frameworks like Spring are embracing the reactive programming model. However, there is still much to explore because if your dependencies are not reactive and non-blocking, your application cannot be truly reactive. For instance, relational database vendors do not provide reactive drivers as they rely on JDBC, which is not reactive. Thus, Hibernate API is also non-reactive. Consequently, if you are using relational databases, you cannot currently develop a fully reactive application. Nonetheless, I am optimistic that this situation will change in the near future.<\/p>\n
The project code is available for download on my GitHub Repository.<\/p>\n
Source: Official documentation<\/p>\n
Paraphrased: Documentation endorsed by the official source.<\/p>\n
<\/p>\n
<\/p>\n
more tutorials<\/p>\n
Spring Boot CLI(Opens in a new browser tab)<\/span><\/a><\/p>\nThe Spring Framework(Opens in a new browser tab)<\/span><\/a><\/p>\nSpring MVC HandlerInterceptorAdapter and HandlerInterceptor.(Opens in a new browser tab)<\/span><\/a><\/p>\n
<\/div>\n- \n
- \n
- Mono implements the Publisher interface and returns either 0 or 1 element.<\/ol>\n<\/li>\n<\/ol>\n
- \n
- Using the CURL command, you can send a request to the specified URL and receive the response “Hello World!”.<\/ol>\n<\/li>\n<\/ol>\n
Alternatively, you can launch the URL in a browser.<\/p>\n
To test a Rest web service using WebTestClient from Spring 5 reactive web, you can use the provided JUnit test program. This program sends a GET request to the specified URI and checks if the response status is OK and the response body is “Hello World!”.<\/p>\n
Another option is to use WebClient from Spring Web Reactive to call the REST web service. This program sends a GET request to the specified URI and retrieves the response body as a string.<\/p>\n
Running these programs will give you the expected output and any relevant debug messages.<\/p>\n
Please provide the text that you want me to paraphrase.<\/h2>\n
This article discussed Spring WebFlux and how to create a basic reactive Restful web service. It’s great to see that well-known frameworks like Spring are embracing the reactive programming model. However, there is still much to explore because if your dependencies are not reactive and non-blocking, your application cannot be truly reactive. For instance, relational database vendors do not provide reactive drivers as they rely on JDBC, which is not reactive. Thus, Hibernate API is also non-reactive. Consequently, if you are using relational databases, you cannot currently develop a fully reactive application. Nonetheless, I am optimistic that this situation will change in the near future.<\/p>\n
The project code is available for download on my GitHub Repository.<\/p>\n
Source: Official documentation<\/p>\n
Paraphrased: Documentation endorsed by the official source.<\/p>\n
<\/p>\n
<\/p>\n
more tutorials<\/p>\n
Spring Boot CLI(Opens in a new browser tab)<\/span><\/a><\/p>\n
The Spring Framework(Opens in a new browser tab)<\/span><\/a><\/p>\n
Spring MVC HandlerInterceptorAdapter and HandlerInterceptor.(Opens in a new browser tab)<\/span><\/a><\/p>\n
<\/p>\n
- Flux implements the Publisher interface and returns multiple (N) elements.<\/ol>\n
Example of a Hello World application using Spring WebFlux<\/h2>\n
<\/div>\nDependencies for Spring WebFlux in Maven.<\/h3>\n
<project xmlns=\"https:\/\/maven.apache.org\/POM\/4.0.0\" xmlns:xsi=\"https:\/\/www.w3.org\/2001\/XMLSchema-instance\" xsi:schemaLocation=\"https:\/\/maven.apache.org\/POM\/4.0.0 https:\/\/maven.apache.org\/xsd\/maven-4.0.0.xsd\">\r\n <modelVersion>4.0.0<\/modelVersion>\r\n <groupId>com.scdev.spring<\/groupId>\r\n <artifactId>SpringWebflux<\/artifactId>\r\n <version>0.0.1-SNAPSHOT<\/version>\r\n <name>Spring WebFlux<\/name>\r\n <description>Spring WebFlux Example<\/description>\r\n \r\n <properties>\r\n <project.build.sourceEncoding>UTF-8<\/project.build.sourceEncoding>\r\n <project.reporting.outputEncoding>UTF-8<\/project.reporting.outputEncoding>\r\n <jdk.version>1.9<\/jdk.version>\r\n <\/properties>\r\n \r\n <parent>\r\n\t\t<groupId>org.springframework.boot<\/groupId>\r\n\t\t<artifactId>spring-boot-starter-parent<\/artifactId>\r\n\t\t<version>2.0.1.RELEASE<\/version>\r\n\t\t<relativePath\/> <!-- lookup parent from repository -->\r\n\t<\/parent>\r\n\r\n\t<dependencies>\r\n\t\t<dependency>\r\n\t\t\t<groupId>org.springframework.boot<\/groupId>\r\n\t\t\t<artifactId>spring-boot-starter-webflux<\/artifactId>\r\n\t\t<\/dependency>\r\n\t\t<dependency>\r\n\t\t\t<groupId>org.springframework.boot<\/groupId>\r\n\t\t\t<artifactId>spring-boot-starter-test<\/artifactId>\r\n\t\t\t<scope>test<\/scope>\r\n\t\t<\/dependency>\r\n\r\n\t\t<dependency>\r\n\t\t\t<groupId>io.projectreactor<\/groupId>\r\n\t\t\t<artifactId>reactor-test<\/artifactId>\r\n\t\t\t<scope>test<\/scope>\r\n\t\t<\/dependency>\r\n <\/dependencies>\r\n\t<repositories>\r\n\t\t<repository>\r\n\t\t\t<id>spring-snapshots<\/id>\r\n\t\t\t<name>Spring Snapshots<\/name>\r\n\t\t\t<url>https:\/\/repo.spring.io\/snapshot<\/url>\r\n\t\t\t<snapshots>\r\n\t\t\t\t<enabled>true<\/enabled>\r\n\t\t\t<\/snapshots>\r\n\t\t<\/repository>\r\n\t\t<repository>\r\n\t\t\t<id>spring-milestones<\/id>\r\n\t\t\t<name>Spring Milestones<\/name>\r\n\t\t\t<url>https:\/\/repo.spring.io\/milestone<\/url>\r\n\t\t\t<snapshots>\r\n\t\t\t\t<enabled>false<\/enabled>\r\n\t\t\t<\/snapshots>\r\n\t\t<\/repository>\r\n\t<\/repositories>\r\n\t<pluginRepositories>\r\n\t\t<pluginRepository>\r\n\t\t\t<id>spring-snapshots<\/id>\r\n\t\t\t<name>Spring Snapshots<\/name>\r\n\t\t\t<url>https:\/\/repo.spring.io\/snapshot<\/url>\r\n\t\t\t<snapshots>\r\n\t\t\t\t<enabled>true<\/enabled>\r\n\t\t\t<\/snapshots>\r\n\t\t<\/pluginRepository>\r\n\t\t<pluginRepository>\r\n\t\t\t<id>spring-milestones<\/id>\r\n\t\t\t<name>Spring Milestones<\/name>\r\n\t\t\t<url>https:\/\/repo.spring.io\/milestone<\/url>\r\n\t\t\t<snapshots>\r\n\t\t\t\t<enabled>false<\/enabled>\r\n\t\t\t<\/snapshots>\r\n\t\t<\/pluginRepository>\r\n\t<\/pluginRepositories>\r\n <build>\r\n <plugins>\r\n <plugin>\r\n <groupId>org.springframework.boot<\/groupId>\r\n <artifactId>spring-boot-maven-plugin<\/artifactId>\r\n <\/plugin>\r\n <\/plugins>\r\n <pluginManagement>\r\n <plugins>\r\n <plugin>\r\n <groupId>org.apache.maven.plugins<\/groupId>\r\n <artifactId>maven-compiler-plugin<\/artifactId>\r\n <version>3.7.0<\/version>\r\n <configuration>\r\n <source>${jdk.version}<\/source>\r\n <target>${jdk.version}<\/target>\r\n <\/configuration>\r\n <\/plugin>\r\n <\/plugins>\r\n <\/pluginManagement>\r\n <\/build>\r\n \r\n<\/project>\r\n<\/code><\/pre>\nThe pivotal dependencies are spring-boot-starter-webflux and spring-boot-starter-parent, while other dependencies serve for the creation of JUnit test scenarios.<\/p>\n
Spring WebFlux Handler can be rephrased as “Handler for Spring WebFlux.”<\/h3>\n
The Handler method of Spring WebFlux manages the request and provides a Mono or Flux as the response.<\/p>\n
package com.scdev.spring.component;\r\n\r\nimport org.springframework.http.MediaType;\r\nimport org.springframework.stereotype.Component;\r\nimport org.springframework.web.reactive.function.BodyInserters;\r\nimport org.springframework.web.reactive.function.server.ServerRequest;\r\nimport org.springframework.web.reactive.function.server.ServerResponse;\r\n\r\nimport reactor.core.publisher.Mono;\r\n\r\n@Component\r\npublic class HelloWorldHandler {\r\n\r\n\tpublic Mono<ServerResponse> helloWorld(ServerRequest request) {\r\n\t\treturn ServerResponse.ok().contentType(MediaType.TEXT_PLAIN)\r\n\t\t\t.body(BodyInserters.fromObject(\"Hello World!\"));\r\n\t}\r\n}\r\n<\/code><\/pre>\nTake note that the Mono reactive component contains the body of the ServerResponse. Additionally, observe the sequence of functions used to establish the content type, response code, and body of the returned response.<\/p>\n
The Spring WebFlux Router is to be rephrased natively.<\/h3>\n
One possible option:
\nRouter for Spring WebFlux in Spring’s framework for reactive web applications.<\/p>\nRouter methods are employed to establish routes for the application. These methods generate a RouterFunction object which also encapsulates the ServerResponse body.<\/p>\n
package com.scdev.spring.component;\r\n\r\nimport org.springframework.context.annotation.Bean;\r\nimport org.springframework.context.annotation.Configuration;\r\nimport org.springframework.http.MediaType;\r\nimport org.springframework.web.reactive.function.server.RequestPredicates;\r\nimport org.springframework.web.reactive.function.server.RouterFunction;\r\nimport org.springframework.web.reactive.function.server.RouterFunctions;\r\nimport org.springframework.web.reactive.function.server.ServerResponse;\r\n\r\n@Configuration\r\npublic class HelloWorldRouter {\r\n\r\n\t@Bean\r\n\tpublic RouterFunction<ServerResponse> routeHelloWorld(HelloWorldHandler helloWorldHandler) {\r\n\r\n\t\treturn RouterFunctions.route(RequestPredicates.GET(\"\/helloWorld\")\r\n .and(RequestPredicates.accept(MediaType.TEXT_PLAIN)), helloWorldHandler::helloWorld);\r\n\t}\r\n}\r\n<\/code><\/pre>\nWe have set up a GET endpoint at \/helloWorld which will provide a plain text response when called by the client.<\/p>\n
A Spring Boot Application<\/h3>\n
We need to set up our basic WebFlux application using Spring Boot.<\/p>\n
package com.scdev.spring;\r\n\r\nimport org.springframework.boot.SpringApplication;\r\nimport org.springframework.boot.autoconfigure.SpringBootApplication;\r\n\r\n@SpringBootApplication\r\npublic class Application {\r\n\r\n\tpublic static void main(String[] args) {\r\n\t\tSpringApplication.run(Application.class, args);\r\n\t}\r\n}\r\n<\/code><\/pre>\nBy examining the code above, it is apparent that there is no reference to Spring WebFlux. However, Spring Boot will automatically set up our application as Spring WebFlux because we have included the dependency of the spring-boot-starter-webflux module.<\/p>\n
Support for Java 9 Modules<\/h3>\n
If you are using Java 8, our application is prepared to run. However, if you are using Java 9, we will also need to incorporate the module-info.java class.<\/p>\n
module com.scdev.spring {\r\n requires reactor.core;\r\n requires spring.web;\r\n requires spring.beans;\r\n requires spring.context;\r\n requires spring.webflux;\r\n requires spring.boot;\r\n requires spring.boot.autoconfigure;\r\n exports com.scdev.spring;\r\n}\r\n<\/code><\/pre>\nStarting the Spring WebFlux Spring Boot Application.<\/h3>\n
<\/div>\n2018-05-07 15:01:47.893 INFO 25158 --- [ main] o.s.w.r.f.s.s.RouterFunctionMapping : Mapped ((GET && \/helloWorld) && Accept: [text\/plain]) -> com.scdev.spring.component.HelloWorldRouter$$Lambda$501\/704766954@6eeb5d56\r\n2018-05-07 15:01:48.495 INFO 25158 --- [ctor-http-nio-1] r.ipc.netty.tcp.BlockingNettyContext : Started HttpServer on \/0:0:0:0:0:0:0:0:8080\r\n2018-05-07 15:01:48.495 INFO 25158 --- [ main] o.s.b.web.embedded.netty.NettyWebServer : Netty started on port(s): 8080\r\n2018-05-07 15:01:48.501 INFO 25158 --- [ main] com.scdev.spring.Application : Started Application in 1.86 seconds (JVM running for 5.542)\r\n<\/code><\/pre>\nBased on the logs, it’s evident that our application is operational on the Netty server, specifically on port 8080. Now, we can proceed with testing the app.<\/p>\n
Test for a Spring WebFlux application.<\/h3>\n
We have the ability to test our app using different techniques.<\/p>\n
- \n
- \n