Using the Quarkus extension for the Spring Web API

Red Hat build of Quarkus 2.2

Abstract

Create endpoints for RESTful services in your Quarkus applications using annotations from Spring Web

Part I. Using the Quarkus extension for the Spring Web API
Copy link

As an application developer, you can use Spring Web annotations to define RESTful services in your Quarkus application.

Making open source more inclusive
Copy link

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

Quarkus provides a compatibility layer for using annotations from Spring Web to define REST endpoints for your application. This functionality is provided by the quarkus-spring-web extension as an alternative to using the default JAX-RS annotations to define your REST endpoints.

Important

The Spring compatibility layer in Quarkus does not start a Spring Application Context or execute any infrastructure classes that are provided by Spring (for example, org.springframework.beans.factory.config.BeanPostProcessor) when you start your application. Quarkus can only read metadata from Spring classes and annotations and parse user code method return types and parameter types that are specific to Spring. However, when you add arbitrary libraries that are part of Spring Framework to your Quarkus application, such libraries will not function properly because Quarkus is not designed to use them.

Note

You can create the example that uses the Quarkus extension for the Spring Web API by following this guide or you can download and view the completed example. To view the completed Quarkus Spring Web example, download it as an archive or clone the Quarkus examples Git repository. You can find the Spring Web example in the spring-web-quickstart directory.

Chapter 1. Prerequisites
Copy link

Have OpenJDK 11 installed and the JAVA_HOME environment variable set to match the path to the directory in which OpenJDK is installed on your system.
Have Apache Maven 3.8.1 or higher installed.

Chapter 2. Creating the Spring Web example Maven project
Copy link

You can create a new Quarkus project, automatically generate the REST controller class, and add the quarkus-spring-web dependency with a single command by using the Quarkus Maven plugin. You can also update the pom.xml file and create the REST controller class and the REST controller test class manually.

Procedure

Use one of the following approaches to create your Quarkus Spring Web example Maven project:
- If you do not have a Maven project, you can create a new Maven project by using the Quarkus Maven plugin. Enter the following command to complete the following actions:
  - Create the Maven project directory structure
  - Create the org.acme.spring.web.GreetingController class that defines a REST endpoint for your application
  - Import the quarkus-spring-web extension
    You must replace <project_name> with the name of the directory that contains your project files.
    
    mvn com.redhat.quarkus.platform:quarkus-maven-plugin:2.2.5.Final-redhat-00007:create \ -DprojectGroupId=org.acme \ -DprojectArtifactId=<project_name> \ -DclassName="org.acme.spring.web.GreetingController" \ -Dpath="/greeting" \ -Dextensions="spring-web"
    
    Copy to Clipboard Toggle word wrap
- If you already have a Quarkus Maven project, you must add the quarkus-spring-web extension to it by using the command line:
1. Navigate to the root directory of your project. Enter the following command:
  cd <project_name>
  Copy to Clipboard Toggle word wrap
2. Add the quarkus-spring-web extension to the pom.xml file of your project. Enter the following command:
  ./mvnw quarkus:add-extension -Dextensions="spring-web"
  Copy to Clipboard Toggle word wrap
  The following entry is added to your pom.xml file:
  pom.xml
  <dependency> <groupId>io.quarkus</groupId> <artifactId>quarkus-spring-web</artifactId> </dependency>
  
  Copy to Clipboard Toggle word wrap

Chapter 3. Creating the main class and test class for GreetingController
Copy link

When you create your project on the command line, the Quarkus Maven plugin automatically generates the GreetingController class file with Spring Web annotations that defines the REST endpoint and a class file that contains the unit test for GreetingController.

Procedure

Create the src/main/java/org/acme/spring/web/GreetingController.java file that contains the following code.

src/main/java/org/acme/spring/web/GreetingController.java

package org.acme.spring.web;

import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RestController;

@RestController
@RequestMapping("/greeting")
public class GreetingController {

    @GetMapping
    public String hello() {
        return "Hello Spring";
    }
}

package org.acme.spring.web;

import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RestController;

@RestController
@RequestMapping("/greeting")
public class GreetingController {

    @GetMapping
    public String hello() {
        return "Hello Spring";
    }
}

Copy to Clipboard

Toggle word wrap

Create the src/test/java/org/acme/spring/web/GreetingControllerTest.java file that contains the following code.

src/test/java/org/acme/spring/web/GreetingControllerTest.java

package org.acme.spring.web;

import io.quarkus.test.junit.QuarkusTest;
import org.junit.jupiter.api.Test;

import static io.restassured.RestAssured.given;
import static org.hamcrest.CoreMatchers.is;

@QuarkusTest
public class GreetingControllerTest {

    @Test
    public void testHelloEndpoint() {
        given()
          .when().get("/greeting")
          .then()
             .statusCode(200)
             .body(is("Hello Spring"));
    }

}

package org.acme.spring.web;

import io.quarkus.test.junit.QuarkusTest;
import org.junit.jupiter.api.Test;

import static io.restassured.RestAssured.given;
import static org.hamcrest.CoreMatchers.is;

@QuarkusTest
public class GreetingControllerTest {

    @Test
    public void testHelloEndpoint() {
        given()
          .when().get("/greeting")
          .then()
             .statusCode(200)
             .body(is("Hello Spring"));
    }

}

Copy to Clipboard

Toggle word wrap

Chapter 4. Compiling and starting your Spring Web example
Copy link

Compile and start your example application by using the Quarkus Maven Plugin. You can also compile and run your application as a native executable.

Procedure

Navigate to the root directory of your project. Enter the following command:
```
cd <project_name>
```
```
cd <project_name>
```
Copy to Clipboard Toggle word wrap
Run the application in development mode by using the Quarkus Maven Plugin. Enter the following command:
```
./mvnw quarkus:dev
```
```
./mvnw quarkus:dev
```
Copy to Clipboard Toggle word wrap
Navigate to the http://localhost:8080/greeting directory. Your browser displays the following message:
```
Hello Spring
```
```
Hello Spring
```
Copy to Clipboard Toggle word wrap

Chapter 5. Configuring the GreetingController to return a JSON response
Copy link

The GreetingController that is automatically generated when you set up your Spring Web example is a simple endpoint that returns a text string as a response. In more complex applications, you might need to configure your REST controller to return a response in JSON format. The following example illustrates how you can configure a Spring RestController to return JSON content.

Procedure

Expand your GreetingController class as shown in the example. The expanded class returns a JSON-formatted response that contains a greeting and a name. To ensure that your configuration works correctly, you must import the PathVariable annotation class from Spring Web:

src/main/java/org/acme/spring/web/GreetingController.java

import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.PathVariable;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RestController;

@RestController
@RequestMapping("/greeting")
public class GreetingController {

    @GetMapping
    public String hello() {
        return "hello";
    }

    @GetMapping("/{name}")
    public Greeting hello(@PathVariable(name = "name") String name) {
        return new Greeting("hello " + name);
    }

    public static class Greeting {
        private final String message;

        public Greeting(String message) {
            this.message = message;
        }

        public String getMessage(){
            return message;
        }
    }
}

import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.PathVariable;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RestController;

@RestController
@RequestMapping("/greeting")
public class GreetingController {

    @GetMapping
    public String hello() {
        return "hello";
    }

    @GetMapping("/{name}")
    public Greeting hello(@PathVariable(name = "name") String name) {
        return new Greeting("hello " + name);
    }

    public static class Greeting {
        private final String message;

        public Greeting(String message) {
            this.message = message;
        }

        public String getMessage(){
            return message;
        }
    }
}

Copy to Clipboard

Toggle word wrap

When you make changes to your REST endpoint, you must update the class file that contains the unit tests for your REST endpoint:

src/test/java/org/acme/spring/web/GreetingControllerTest.java

package org.acme.spring.web;

import io.quarkus.test.junit.QuarkusTest;
import org.junit.jupiter.api.Test;

import static io.restassured.RestAssured.given;
import static org.hamcrest.CoreMatchers.is;

@QuarkusTest
public class GreetingControllerTest {

    @Test
    public void testHelloEndpoint() {
        given()
          .when().get("/greeting/quarkus")
          .then()
            .statusCode(200)
            .body("message", is("hello quarkus"));
    }

}

package org.acme.spring.web;

import io.quarkus.test.junit.QuarkusTest;
import org.junit.jupiter.api.Test;

import static io.restassured.RestAssured.given;
import static org.hamcrest.CoreMatchers.is;

@QuarkusTest
public class GreetingControllerTest {

    @Test
    public void testHelloEndpoint() {
        given()
          .when().get("/greeting/quarkus")
          .then()
            .statusCode(200)
            .body("message", is("hello quarkus"));
    }

}

Copy to Clipboard

Toggle word wrap

Note

When you use the Spring Web compatibility layer in Quarkus, the com.fasterxml:jackson.core dependency is automatically added to the classpath of your application and configured.

Chapter 6. Enabling OpenAPI and Swagger-UI support in your Spring Web example
Copy link

You can add support for generating OpenAPI schema documents of your REST endpoints with Swagger-UI to your application by adding the quarkus-smallrye-openapi extension.

Procedure

Add the quarkus-smallrye-openapi extension as a dependency of your Spring Web example. By adding the extension, you can generate a basic OpenAPI schema document from your REST Endpoints. Enter the following command:

./mvnw quarkus:add-extension -Dextensions="io.quarkus:quarkus-smallrye-openapi"

./mvnw quarkus:add-extension -Dextensions="io.quarkus:quarkus-smallrye-openapi"

Copy to Clipboard

Toggle word wrap

The following dependency is added to your pom.xml:

pom.xml

<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-smallrye-openapi</artifactId>
</dependency>

<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-smallrye-openapi</artifactId>
</dependency>

Copy to Clipboard

Toggle word wrap

Obtain the schema document from the /q/openapi. Enter the following command:

curl http://localhost:8080/q/openapi

curl http://localhost:8080/q/openapi

Copy to Clipboard

Toggle word wrap

You receive a response with the generated OpenAPI schema document in YAML format:

---
openapi: 3.0.3
info:
  title: Generated API
  version: "1.0"
paths:
  /greeting:
    get:
      responses:
        "200":
          description: OK
          content:
            text/plain:
              schema:
                type: string
  /greeting/{name}:
    get:
      parameters:
      - name: name
        in: path
        required: true
        schema:
          type: string
      responses:
        "200":
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Greeting'
components:
  schemas:
    Greeting:
      type: object
      properties:
        message:
          type: string

---
openapi: 3.0.3
info:
  title: Generated API
  version: "1.0"
paths:
  /greeting:
    get:
      responses:
        "200":
          description: OK
          content:
            text/plain:
              schema:
                type: string
  /greeting/{name}:
    get:
      parameters:
      - name: name
        in: path
        required: true
        schema:
          type: string
      responses:
        "200":
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Greeting'
components:
  schemas:
    Greeting:
      type: object
      properties:
        message:
          type: string

Copy to Clipboard

Toggle word wrap

Chapter 7. Adding MicroProfile OpenAPI annotations to your REST controller code
Copy link

You can add MicroProfile OpenAPI annotations to your REST controller code to generate a more detailed OpenAPI schema for your REST endpoints.

Procedure

Add the @OpenApiDefinition annotation at the class level of your GreetingController. Include the data that is shown in the annotation in the following example:

@OpenAPIDefinition(
    info = @Info(
        title="Greeting API",
        version = "1.0.1",
        contact = @Contact(
            name = "Greeting API Support",
            url = "http://exampleurl.com/contact",
            email = "techsupport@example.com"),
        license = @License(
            name = "Apache 2.0",
            url = "https://www.apache.org/licenses/LICENSE-2.0.html"))
)

@OpenAPIDefinition(
    info = @Info(
        title="Greeting API",
        version = "1.0.1",
        contact = @Contact(
            name = "Greeting API Support",
            url = "http://exampleurl.com/contact",
            email = "techsupport@example.com"),
        license = @License(
            name = "Apache 2.0",
            url = "https://www.apache.org/licenses/LICENSE-2.0.html"))
)

Copy to Clipboard

Toggle word wrap

Annotate your endpoint definitions by using the @Tag annotation. Enter a name and a description for each endpoint:

@Tag(name = "Hello", description = "Just say hello")
@GetMapping(produces=MediaType.TEXT_PLAIN_VALUE)
public String hello() {
    return "hello";
}

@GetMapping(value = "/{name}", produces=MediaType.APPLICATION_JSON_VALUE)
@Tag(name = "Hello to someone", description = "Just say hello to someone")
public Greeting hello(@PathVariable(name = "name") String name) {
    return new Greeting("hello " + name);
}

@Tag(name = "Hello", description = "Just say hello")
@GetMapping(produces=MediaType.TEXT_PLAIN_VALUE)
public String hello() {
    return "hello";
}

@GetMapping(value = "/{name}", produces=MediaType.APPLICATION_JSON_VALUE)
@Tag(name = "Hello to someone", description = "Just say hello to someone")
public Greeting hello(@PathVariable(name = "name") String name) {
    return new Greeting("hello " + name);
}

Copy to Clipboard

Toggle word wrap

The data that you provided in the annotations appears in the generated OpenAPI schema:

openapi: 3.0.3
info:
  title: Greeting API
  contact:
    name: Greeting API Support
    url: http://exampleurl.com/contact
    email: techsupport@example.com
  license:
    name: Apache 2.0
    url: https://www.apache.org/licenses/LICENSE-2.0.html
  version: 1.0.1
tags:
- name: Hello
    description: Just say hello
- name: Hello to someone
    description: Just say hello to someone
paths:
  /greeting:
    get:
      tags:
      - Hello
      responses:
        '200':
          description: OK
          content:
            text/plain:
              schema:
                type: string
  /greeting/{name}:
    get:
      tags:
      - Hello to someone
      parameters:
      - name: name
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Greeting'

components:
  schemas:
    Greeting:
      type: object
      properties:
        message:
          type: string

openapi: 3.0.3
info:
  title: Greeting API
  contact:
    name: Greeting API Support
    url: http://exampleurl.com/contact
    email: techsupport@example.com
  license:
    name: Apache 2.0
    url: https://www.apache.org/licenses/LICENSE-2.0.html
  version: 1.0.1
tags:
- name: Hello
    description: Just say hello
- name: Hello to someone
    description: Just say hello to someone
paths:
  /greeting:
    get:
      tags:
      - Hello
      responses:
        '200':
          description: OK
          content:
            text/plain:
              schema:
                type: string
  /greeting/{name}:
    get:
      tags:
      - Hello to someone
      parameters:
      - name: name
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Greeting'

components:
  schemas:
    Greeting:
      type: object
      properties:
        message:
          type: string

Copy to Clipboard

Toggle word wrap

Chapter 8. Overview of Spring Web annotations supported in Quarkus
Copy link

The Spring compatibility layer in Quarkus supports a limited subset of features that Spring Web provides. Specifically, Quarkus supports only the REST-related annotations from Spring Web, for example, @RestController, but not @Controller.

Quarkus supports the following annotations from Spring Web:

@RestController
@RequestMapping
@GetMapping
@PostMapping
@PutMapping
@DeleteMapping
@PatchMapping
@RequestParam
@RequestHeader
@MatrixVariable
@PathVariable
@CookieValue
@RequestBody
@ResponseStatus
@ExceptionHandler ^[1]
@RestControllerAdvice ^[2]

^[1] Can only be used in a @RestControllerAdvice class, not on a per-controller basis.

^[2] Only the @ExceptionHandler capability is supported in Quarkus.

Chapter 9. Overview of Spring Web annotations and their JAX-RS equivalents
Copy link

The following table shows how Spring Web annotations can be converted to JAX-RS annotations.

Expand

Table 9.1. Spring Web annotations and their JAX-RS equivalents
Spring	JAX-RS	Notes
`@RestController`		No equivalent annotation in JAX-RS. Annotating a class with `@Path` suffices.
`@RequestMapping`(path="/api")	`@Path`("/api")
`@RequestMapping`(consumes="application/json")	`@Consumes`("application/json")
`@RequestMapping`(produces="application/json")	`@Produces`("application/json")
`@RequestParam`	`@QueryParam`
`@PathVariable`	`@PathParam`
`@RequestBody`		No equivalent annotation in JAX-RS. Method parameters that correspond to the body of the request are handled in JAX-RS without requiring any annotation.
`@RestControllerAdvice`		No equivalent annotation in JAX-RS.
`@ResponseStatus`		No equivalent annotation in JAX-RS.
`@ExceptionHandler`		No equivalent annotation in JAX-RS. Exceptions are handled by implementing `javax.ws.rs.ext.ExceptionMapper`.

Chapter 10. Controller method parameter types supported in Quarkus
Copy link

In addition to the method parameters that can be annotated with the appropriate Spring Web annotations from the previous table, the following controller method parameter types are supported:

javax.servlet.http.HttpServletRequest
javax.servlet.http.HttpServletResponse

For this to function, users must add the quarkus-undertow dependency.

Chapter 11. Controller method return types supported in Quarkus
Copy link

The Quarkus extension for Spring Web API supports the following method return types:

Primitive types
String (Used as a literal. Quarkus does not support Spring MVC view)
POJO classes that are serialized using JSON
org.springframework.http.ResponseEntity

Chapter 12. Exception handler method parameter types supported in Quarkus
Copy link

The Quarkus extension for Spring Web API supports the following exception handler method parameter types:

An exception argument: declared as a general Exception or as a more specific exception. This also serves as a mapping hint if the annotation itself does not specify the exception types using its value().
Request objects or response objects or both (typically from the Servlet API): You can choose any specific request or response type, for example ServletRequest or HttpServletRequest. To use the Servlet API, you must add the quarkus-undertow dependency to your project.

Note

The order in which the types are listed is arbitrary and does not reflect the order of preference in which individual parameter types should be used.

Other parameter types that are mentioned in the Spring ExceptionHandler Java API documentation are not supported in Quarkus

Chapter 13. Exception handler method return types supported in Quarkus
Copy link

The Quarkus extension for Spring Web API supports the following method return types:

org.springframework.http.ResponseEntity
java.util.Map

Other return types mentioned in the Spring ExceptionHandler Java API documentation are not supported in Quarkus.

Legal Notice
Copy link

The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.

Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.

Linux® is the registered trademark of Linus Torvalds in the United States and other countries.

Java® is a registered trademark of Oracle and/or its affiliates.

XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.

MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.

Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.

The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.

All other trademarks are the property of their respective owners.

Using the Quarkus extension for the Spring Web API

Part I. Using the Quarkus extension for the Spring Web API
Copy link

Making open source more inclusive
Copy link

Chapter 1. Prerequisites
Copy link

Chapter 2. Creating the Spring Web example Maven project
Copy link

Chapter 3. Creating the main class and test class for GreetingController
Copy link

Chapter 4. Compiling and starting your Spring Web example
Copy link

Chapter 5. Configuring the GreetingController to return a JSON response
Copy link

Chapter 6. Enabling OpenAPI and Swagger-UI support in your Spring Web example
Copy link

Chapter 7. Adding MicroProfile OpenAPI annotations to your REST controller code
Copy link

Chapter 8. Overview of Spring Web annotations supported in Quarkus
Copy link

Chapter 9. Overview of Spring Web annotations and their JAX-RS equivalents
Copy link

Chapter 10. Controller method parameter types supported in Quarkus
Copy link

Chapter 11. Controller method return types supported in Quarkus
Copy link

Chapter 12. Exception handler method parameter types supported in Quarkus
Copy link

Chapter 13. Exception handler method return types supported in Quarkus
Copy link

Legal Notice
Copy link

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

Making open source more inclusive

About Red Hat

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links

Using the Quarkus extension for the Spring Web API

Part I. Using the Quarkus extension for the Spring Web APICopy linkLink copied to clipboard!

Making open source more inclusiveCopy linkLink copied to clipboard!

Chapter 1. PrerequisitesCopy linkLink copied to clipboard!

Chapter 2. Creating the Spring Web example Maven projectCopy linkLink copied to clipboard!

Chapter 3. Creating the main class and test class for GreetingControllerCopy linkLink copied to clipboard!

Chapter 4. Compiling and starting your Spring Web exampleCopy linkLink copied to clipboard!

Chapter 5. Configuring the GreetingController to return a JSON responseCopy linkLink copied to clipboard!

Chapter 6. Enabling OpenAPI and Swagger-UI support in your Spring Web exampleCopy linkLink copied to clipboard!

Chapter 7. Adding MicroProfile OpenAPI annotations to your REST controller codeCopy linkLink copied to clipboard!

Chapter 8. Overview of Spring Web annotations supported in QuarkusCopy linkLink copied to clipboard!

Chapter 9. Overview of Spring Web annotations and their JAX-RS equivalentsCopy linkLink copied to clipboard!

Chapter 10. Controller method parameter types supported in QuarkusCopy linkLink copied to clipboard!

Chapter 11. Controller method return types supported in QuarkusCopy linkLink copied to clipboard!

Chapter 12. Exception handler method parameter types supported in QuarkusCopy linkLink copied to clipboard!

Chapter 13. Exception handler method return types supported in QuarkusCopy linkLink copied to clipboard!

Legal NoticeCopy linkLink copied to clipboard!

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

Making open source more inclusive

About Red Hat

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links

Part I. Using the Quarkus extension for the Spring Web API
Copy link

Making open source more inclusive
Copy link

Chapter 1. Prerequisites
Copy link

Chapter 2. Creating the Spring Web example Maven project
Copy link

Chapter 3. Creating the main class and test class for GreetingController
Copy link

Chapter 4. Compiling and starting your Spring Web example
Copy link

Chapter 5. Configuring the GreetingController to return a JSON response
Copy link

Chapter 6. Enabling OpenAPI and Swagger-UI support in your Spring Web example
Copy link

Chapter 7. Adding MicroProfile OpenAPI annotations to your REST controller code
Copy link

Chapter 8. Overview of Spring Web annotations supported in Quarkus
Copy link

Chapter 9. Overview of Spring Web annotations and their JAX-RS equivalents
Copy link

Chapter 10. Controller method parameter types supported in Quarkus
Copy link

Chapter 11. Controller method return types supported in Quarkus
Copy link

Chapter 12. Exception handler method parameter types supported in Quarkus
Copy link

Chapter 13. Exception handler method return types supported in Quarkus
Copy link

Legal Notice
Copy link