Spring @DeleteMapping

last modified October 18, 2023

Spring @DeleteMapping tutorial shows how to use @DeleteMapping annotation to map HTTP DELETE requests onto specific handler methods. We create a classic Spring application.

Spring is a popular Java application framework for creating enterprise applications.

@DeleteMapping

@DeleteMapping annotation maps HTTP DELETE requests onto specific handler methods. It is a composed annotation that acts as a shortcut for @RequestMapping(method = RequestMethod.DELETE).

Spring @DeleteMapping example

The following application uses @DeleteMapping to delete a resource. We use annotations to set up a Spring web application.

pom.xml src ├───main │ ├───java │ │ └───com │ │ └───zetcode │ │ ├───config │ │ │ MyWebInitializer.java │ │ │ WebConfig.java │ │ ├───controller │ │ │ MyController.java │ │ ├───model │ │ │ Post.java │ │ └───service │ │ PostService.java │ └───resources │ logback.xml └───test └───java

This is the project structure.

pom.xml

<?xml version=“1.0” encoding=“UTF-8”?> <project xmlns=“http://maven.apache.org/POM/4.0.0" xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=“http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion>

<groupId>com.zetcode</groupId>
<artifactId>postmappingex</artifactId>
<version>1.0-SNAPSHOT</version>
<packaging>war</packaging>

<properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <maven.compiler.source>17</maven.compiler.source>
    <maven.compiler.target>17</maven.compiler.target>
    <spring-version>5.3.23</spring-version>
</properties>

<dependencies>

    <dependency>
        <groupId>javax.servlet</groupId>
        <artifactId>javax.servlet-api</artifactId>
        <version>4.0.1</version>
        <scope>provided</scope>
    </dependency>

    <dependency>
        <groupId>org.springframework</groupId>
        <artifactId>spring-webmvc</artifactId>
        <version>${spring-version}</version>
    </dependency>

    <dependency>
        <groupId>com.fasterxml.jackson.core</groupId>
        <artifactId>jackson-databind</artifactId>
        <version>2.13.4</version>
    </dependency>

</dependencies>

<build>
    <plugins>

        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-war-plugin</artifactId>
            <version>3.3.2</version>
        </plugin>

        <plugin>
            <groupId>org.eclipse.jetty</groupId>
            <artifactId>jetty-maven-plugin</artifactId>
            <version>9.4.49.v20220914</version>
        </plugin>

    </plugins>
</build>

</project>

In the pom.xml file we have the project dependencies.

resources/logback.xml

<?xml version=“1.0” encoding=“UTF-8”?> <configuration> <logger name=“org.springframework” level=“ERROR”/> <logger name=“com.zetcode” level=“INFO”/>

<appender name="consoleAppender" class="ch.qos.logback.core.ConsoleAppender">
    <encoder>
        <Pattern>%d{HH:mm:ss.SSS} %blue(%-5level) %magenta(%logger{36}) - %msg %n
        </Pattern>
    </encoder>
</appender>

<root>
    <level value="INFO" />
    <appender-ref ref="consoleAppender" />
</root>

</configuration>

The logback.xml is a configuration file for the Logback logging library.

com/zetcode/config/MyWebInitializer.java

package com.zetcode.config;

import org.springframework.context.annotation.Configuration; import org.springframework.web.servlet.support.AbstractAnnotationConfigDispatcherServletInitializer;

@Configuration public class MyWebInitializer extends AbstractAnnotationConfigDispatcherServletInitializer {

@Override
protected Class<?>[] getRootConfigClasses() {
    return null;
}

@Override
protected Class<?>[] getServletConfigClasses() {

    return new Class[]{WebConfig.class};
}

@Override
protected String[] getServletMappings() {

    return new String[]{"/"};
}

}

MyWebInitializer registers the Spring DispatcherServlet, which is a front controller for a Spring web application.

@Override protected Class<?>[] getServletConfigClasses() {

return new Class[]{WebConfig.class};

}

The getServletConfigClasses returns a web configuration class.

com/zetcode/config/WebConfig.java

package com.zetcode.config;

import org.springframework.context.annotation.ComponentScan; import org.springframework.context.annotation.Configuration; import org.springframework.web.servlet.config.annotation.EnableWebMvc;

@Configuration @EnableWebMvc @ComponentScan(basePackages = {“com.zetcode”}) public class WebConfig {

}

The WebConfig enables Spring MVC annotations with @EnableWebMvc and configures component scanning for the com.zetcode package.

com/zetcode/controller/MyController.java

package com.zetcode.controller;

import com.zetcode.model.Post; import com.zetcode.service.IPostService; import org.springframework.beans.factory.annotation.Autowired; import org.springframework.http.HttpStatus; import org.springframework.http.ResponseEntity; import org.springframework.stereotype.Controller; import org.springframework.web.bind.annotation.DeleteMapping; import org.springframework.web.bind.annotation.GetMapping; import org.springframework.web.bind.annotation.PathVariable;

import java.util.Set;

import static org.springframework.http.ResponseEntity.ok;

@Controller public class MyController {

@Autowired
private IPostService postService;

@GetMapping(value="/posts")
public ResponseEntity<Set<Post>> all() {
    return ok().body(postService.all());
}

@DeleteMapping(value = "/posts/{id}")
public ResponseEntity<Long> deletePost(@PathVariable Long id) {

    var isRemoved = postService.delete(id);

    if (!isRemoved) {
        return new ResponseEntity<>(HttpStatus.NOT_FOUND);
    }

    return new ResponseEntity<>(id, HttpStatus.OK);
}

}

MyController provides mappings between request paths and handler methods. We have two mappings: one for a GET request and one for a DELETE request.

@GetMapping(value="/posts”) public ResponseEntity<Set<Post>> all() { return ok().body(postService.all()); }

The method annotated with @GetMapping returns all posts.

@DeleteMapping(value = “/posts/{id}”) public ResponseEntity<Long> deletePost(@PathVariable Long id) {

var isRemoved = postService.delete(id);

if (!isRemoved) {
    return new ResponseEntity<>(HttpStatus.NOT_FOUND);
}

return new ResponseEntity<>(id, HttpStatus.OK);

}

The deletePost is annotated with @DeleteMapping. The job of the method is to try to delete a post using an IPostService. An appropriate ResponseEntity is returned depending on the outcome.

com/zetcode/model/Post.java

package com.zetcode.model;

import java.util.Objects;

public class Post {

private Long id;
private String content;

public Post() {

}

public Post(Long id, String content) {
    this.id = id;
    this.content = content;
}

public Long getId() {
    return id;
}

public void setId(Long id) {
    this.id = id;
}

public String getContent() {
    return content;
}

public void setContent(String content) {
    this.content = content;
}

@Override
public boolean equals(Object o) {
    if (this == o) return true;
    if (o == null || getClass() != o.getClass()) return false;
    Post post = (Post) o;
    return Objects.equals(id, post.id) &&
            Objects.equals(content, post.content);
}

@Override
public int hashCode() {
    return Objects.hash(id, content);
}

}

This is a simple Post bean. It has two attributes: id and content.

com/zetcode/service/IPostService.java

package com.zetcode.service;

import com.zetcode.model.Post;

import java.util.Set;

public interface IPostService {

boolean delete(Long id);
Set<Post> all();

}

The IPostService contains two contract methods: delete and all.

com/zetcode/service/PostService.java

package com.zetcode.service;

import com.zetcode.model.Post; import org.springframework.stereotype.Service;

import java.util.HashSet; import java.util.Set; import java.util.concurrent.atomic.AtomicLong;

@Service public class PostService implements IPostService {

private final AtomicLong counter = new AtomicLong();

private final Set<Post> posts = new HashSet<>(Set.of(new Post(counter.incrementAndGet(), "Post one"),
        new Post(counter.incrementAndGet(), "Post two"), new Post(counter.incrementAndGet(), "Post three"),
        new Post(counter.incrementAndGet(), "Post four")));

public boolean delete(Long id) {

    var isRemoved = this.posts.removeIf(post -> post.getId().equals(id));

    return isRemoved;
}

public Set<Post> all() {

    return this.posts;
}

}

A PostService has methods to delete a post and return all posts. We do not implement a database layer; instead we use a simple in-memory collection.

Note: In a real application, we would also implement a Repository layer.

$ mvn jetty:run

We run the Jetty server.

$ curl localhost:8080/posts [{“id”:3,“content”:“Post three”},{“id”:4,“content”:“Post four”}, {“id”:1,“content”:“Post one”},{“id”:2,“content”:“Post two”}]

With the curl tool, we retrieve all posts.

$ curl -i -X DELETE localhost:8080/posts/1/ HTTP/1.1 200 OK Date: Wed, 21 Sep 2022 10:56:07 GMT Content-Type: application/json Transfer-Encoding: chunked Server: Jetty(9.4.49.v20220914)

1

We delete a post with Id 1.

$ curl localhost:8080/posts [{“id”:3,“content”:“Post three”},{“id”:4,“content”:“Post four”}, {“id”:2,“content”:“Post two”}]

We get all posts againg; the post with Id one is removed.

In this article, we have presented the @DeleteMapping annotation.

Author

My name is Jan Bodnar, and I am a passionate programmer with extensive programming experience. I have been writing programming articles since 2007. To date, I have authored over 1,400 articles and 8 e-books. I possess more than ten years of experience in teaching programming.

List all Spring tutorials.