EzyHTTP Handle Client Requests

EzyHttp allows you handle client request vi Controller with GET, POST, PUT, DELETE methods

1. Handle Get Request

You can handle a get request with a method and @DoGet annotation. EzyHttp allows you pass parameter via query parameters or path variable, example:
public BookResponse getBook(@PathVariable Long bookId) {
    final BookData bookData = bookService.getBook(bookId);
    return dataToResponseConverter.toResponse(bookData);

public List<BookResponse> getBooks(
    @RequestParam("lower_than") String lowerThan,
    @RequestParam("upper_than") String upperThan,
    @RequestParam("size") int size
) {
    final List<BookData> dataList = bookService.getBooks(
    return dataToResponseConverter.toResponseList(dataList);
You can find out full source code in BookController Example
Use path variable make our code more clearer and it makes our APIs become resource oriented. But when we have many parameters we should use request query parameters

2. Handle Post Request

Get request does not accept an body. So for a create or update API we should use POST method. Of course you still can use path variable and query parameters with a POST request, example:
public boolean addBooks(@PathVariable int count) {
    return Boolean.TRUE;

public BookResponse addBook(@RequestBody AddBookRequest request) {
    final AddBookData addBookData = requestToDataConverter.toData(request);
    final BookData bookData = bookService.addBook(addBookData);
    return dataToResponseConverter.toResponse(bookData);
You can find out full source code in BookController Example

3. Handle Put Request

Same as the POST method, but PUT method is suitable for update APIs, example:
public ResponseEntity getBook(
    @PathVariable Long bookId,
    @RequestBody UpdateBookRequest request
) {
    return ResponseEntity.noContent();

4. Handle Delete Request

If you want to delete a resource, you should use a delete API, but delete method does not accept an request body so we need use path variable or query parmaters, but path variable is a better idea, example
public ResponseEntity getExpectedRevenue() {
    return ResponseEntity.noContent();
You can find out full source code in BookController example

5. Next