Implementing and Documenting REST APIs With Java EE

the standard way to implement rest apis in java ee applications is jax-rs . the de-facto standard for api documentation is openapi (formally swagger). eclipse microprofile supports developers using openapi annotations for jax-rs api implementations to document the apis.

check out the cloud-native starter repo on github. it comes with multiple microservices, two of them have been implemented with java ee and microprofile.

eclipse microprofile supports the openapi v3 specification. the documentation lists all available annotations.

i like using annotations directly in the code to document apis rather than using external configuration files. the closer the documentation stays together with the actual api implementation, the better and more accurate it will be.

in my sample, i created one java class per endpoint to reduce the lengths of the files, since the api documentation can become quite verbose.

when it comes to the design of apis, my personal taste is to provide business-logic-oriented apis rather than crud operations on resources. the following sample shows the ' web-api/v1/getmultiple ' endpoint which internally utilizes several resources. it's part of the api service that uses the bff (backend for frontend) pattern. it provides the exact apis web applications need and doesn't expose the internally used resources.

package com.ibm.webapi.apis;

import javax.ws.rs.*;
import org.eclipse.microprofile.openapi.annotations.*;

@requestscoped
@path("/v1")
@openapidefinition(info = @info(title = "web-api service", version = "1.0", description = "web-api service apis", contact = @contact(url = "https://github.com/nheidloff/cloud-native-starter", name = "niklas heidloff"), license = @license(name = "license", url = "https://github.com/nheidloff/cloud-native-starter/blob/master/license")))
public class getarticles {
   @inject
   com.ibm.webapi.business.service service;
   @inject
   articleasjson articleasjson;

   @get
   @path("/getmultiple")
   @produces(mediatype.application_json)
   @apiresponses(value = { 
      @apiresponse(responsecode = "200", description = "get most recently added articles", content = @content(mediatype = "application/json", schema = @schema(type = schematype.array, implementation = article.class))),
      @apiresponse(responsecode = "500", description = "internal service error") })
   @operation(summary = "get most recently added articles", description = "get most recently added articles")
   public response getarticles() {
      jsonarray jsonarray;
      try {
         list<article> articles = service.getarticles();
         stream<article> streamarticles = articles.stream();
         stream<jsonobject> streamjsonobjects = streamarticles.map(article -> {
            jsonobject output = articleasjson.createjsonarticle(article);
              return output;
         });
         jsonarray = streamjsonobjects.collect(jsoncollectors.tojsonarray());
         return response.ok(jsonarray).build();
      } catch (nodataaccess e) {
         e.printstacktrace();
         return response.status(response.status.internal_server_error).build();
      }  
   }
}

the nice thing about microprofile and the open-source java ee application server, openliberty , is that it comes with the built-in openapi web application to read the documentation and invoke the apis.

to learn more about microprofile openapi, check out the cloud-native starter repo and the documentation .