Need a better, easier way to manage authorization within your application? Check out this tutorial on role-based security with JAX-RS annotations. Let's get started!
Spring Boot + Jersey: Role-Based Security With JAX-RS Annotations
How to Use Apache Shiro and OAuth 2.0 to Build a Secure Application
For those unfamiliar, Apache Shiro—a Java Security framework—performs authorization, authentication, and session management (along with many other functions) to help build more secure applications.
This post will show you how to use JAX-RS to build a simple Java REST application. JAX-RS is a set of interfaces so you’ll need to pick your implementation. In this post, we’ll be using Jersey—but you can use whatever implementation you prefer and none of these APIs are Jersey specific.
Spring Boot – Microservice- JaxRS Jersey – HATEOAS – JerseyTest – Integration
In this article, we discuss how to write a Spring Boot microservice based on Spring Jax-Rs Jersey, HATEOAS API, and JerseyTest framework integration. We are going to take the material of our previous article Spring Boot - Microservice - Spring Data REST and HATEOAS Integration and rewrite it for new Spring Jax-Rs Jersey usage.
You may also like: REST API — What Is HATEOAS?
Thoughts on the Jakarta EE Package Name Change
The Eclipse Foundation announced that Jakarta EE cannot continue to use the javax package name. Apparently, this comes with the fact that while Java EE is based on this name, no further modifications are allowed to classes or packages starting with that name.
While this is certainly bad news, for me, the bad news already started when it was announced that Jakarta EE can’t use the javax name for new specifications and sub-packages. That would have already meant continuing to evolve a platform that becomes more inconsistent over time.
Applying Bulkheads and Backpressure Using MicroProfile (Video)
I’ve recorded a video on how to implement bulkheads and backpressure using MicroProfile Fault Tolerance. The idea behind bulkheads is to split applications into several execution units that isolate functionality. In enterprise Java applications, this typically means defining multiple thread pools.
Applying backpressure to clients results in either adding information about the current pressure on the system to the client so that they will react to it, or to explicitly deny the request with a temporary error response.