Nowadays, exposed APIs are finally getting the attention they deserve and companies are starting to recognize their strategic value. However, working with 3rd party APIs can be really tedious work, especially when these APIs are not maintained, ill designed or missing any documentation. That’s why I decided to look around for ways to provide fellow programmers and other team members with proper documentation when it comes to integration. One way to go is to use WADL, which is a standard specifically designed to describe HTTP based web applications (like REST web services). However there are few drawback when using WADL that made me look elsewhere for solutions how to properly document and expose API documentation.
In the age of APIs, it is more obvious than ever that significant part of business value of many organizations (or their products) stems from their exposed interfaces. One of the most popular architectural styles to design and build such an API is REST. RESTful web services were introduced to Java in JSR 311 and the specification got name JAX-RS. At the time of writing this review JAX-RS reached version 2.0 and 2.1 is being drafted. Realizing this I felt the need to brush up on my previous knowledge of this technology and see what it has to offer. In my search for study resources I came across an awesome book called RESTful Java with JAX-RS 2.0 by Bill Burke, software architect and developer from Red Hat with years of experience working with REST and related technologies.