Map standard and custom exceptions to a http response body containing problem details as specified in RFC-7807.

Most things work out of the box: the type and title fields are derived from the exception class name; the detail field is the message of the exception; the instance field is a random UUID URN that is also logged together with the complete stack trace.

These defaults can be overridden with annotations.

• MUST application/problem+json, application/problem+xml; SHOULD any, e.g. +yaml

• SHOULD render text/html

• map also @Valid REST params

• logging: 4xx = DEBUG, 5xx = ERROR; configurable?

• order of extensions is alphabetic (which is better for tests than random)

• multiple extensions with the same name: undefined behavior

• JAXB can’t unmarshal a subclass with the same type and namespace

• Security considerations: nothing dangerous in problem details (i.e. exception message); stack-trace in logs

It’s called ri, but it’s actually only a POC, and it’s incomplete. See the README for details.

The test module runs integration tests by using JEE Testcontainers, i.e. it can be configured to start different Docker containers with various JEE application servers. By default, it starts a Wildfly.

testcontainer-running

As the containers don’t yet implement the API by themselves, the dummy implementation ri is hard-wired in the tests for now.

Wildfly

Open Liberty

TomEE

Payara