Home » Java » Enterprise Java » Spring MVC: REST application with CNVR vol. 3

About Alexey Zvolinskiy

Alexey Zvolinskiy
Alexey is a test developer with solid experience in automation of web-applications using Java, TestNG and Selenium. He is so much into QA that even after work he provides training courses for junior QA engineers.

Spring MVC: REST application with CNVR vol. 3

This is a final, third part of Spring MVC REST tutorial with CNVR. Here I will demonstrate how all that stuff works, which I have developed within first two parts. Here will be four sections for each type of CRUD operations: CREATE, READ, UPDATE, DELETE. As a pre-requirement you need to install any REST client for a working with a REST requests.


The first operation will be creation of a smartphone. I’m going to use POSTMAN REST client. It’s a Google Chrome extension and you can download it absolutely free. When I perform CREATE or UPDATE operation I have to pass some data in a body of the request which will be used for creation or update of entity. So let’s see how it works:


On the image above you can see completed CREATE operation. Let’s consider the most essential parts of it.

  • The URL contains .json sufix
  • POST selected as a HTTP method
  • Request body it is the JSON document which contain required fields for a smartphone creation
  • Response body it is the JSON document which in our case equals to Request body

I hope you noticed one more important detail. I talk about the Content-type = application/json. As you remember in the methods of controoler I specified such parameters as “consumes“:

	@RequestMapping(value="/create", method=RequestMethod.POST, 
			produces = "application/json", consumes = "application/json")
	public Smartphone createSmartphone(@RequestBody Smartphone smartphone) {
		return smartphoneService.create(smartphone);

That’s mean that the method will work just with JSON. Spring permits to set multiple types for “produces” and “consumes” attributes.


The second operation will show how to select some records.


In this case I just used the HTTP GET request and it returned to me a list of existing smartphones in JSON format.


A HTTP PUT request as a HTTP POST request should have body content to be have information about updating data.



In the most straightforward case HTTP DELETE request just need to know ID of entity which will be removed.


As you see everything goes as in previous examples except HTTP request type, which was changed to DELETE.

It’s not all

But as you remember I have developed some methods in the controller which return ModelAndView object. Hence you can do the same operations through a web interface. It was very challenging for me to write these tutorials. I covered here just a top of the “REST” iceberg. In the future I will write some articles about AJAX, exception handling and other cool stuff related to the REST.

Reference: Spring MVC: REST application with CNVR vol. 3 from our JCG partner Alexey Zvolinskiy at the Fruzenshtein’s notes blog.
(0 rating, 0 votes)
You need to be a registered member to rate this.
1 Comment Views Tweet it!
Do you want to know how to develop your skillset to become a Java Rockstar?
Subscribe to our newsletter to start Rocking right now!
To get you started we give you our best selling eBooks for FREE!
1. JPA Mini Book
2. JVM Troubleshooting Guide
3. JUnit Tutorial for Unit Testing
4. Java Annotations Tutorial
5. Java Interview Questions
6. Spring Interview Questions
7. Android UI Design
and many more ....
Email address:

Leave a Reply

1 Comment on "Spring MVC: REST application with CNVR vol. 3"

newest oldest most voted
Notify of


I am a new comer to java config for spring mvc.

I have used your example from GIT, the application is deployed fine on JBoss.

21:03:12,711 INFO [org.jboss.as.server] (DeploymentScanner-threads – 1) JBAS018559: Deployed “MobileApp.war”

But unable to access the links shared, http://localhost:8080/MobileApp/smartphones/create.json

I recieve a 404 error. Resource not found. How should I trace it.