How to Structure Jakarta EE Applications for Productivity Without Bloat--from CodeONE in San Francisco

CodeONE San Francisco session: "How to Structure Jakarta EE Applications for Productivity Without Bloat"

"Most enterprise applications are structured in a bureaucratic way: it is easy to find an exception or DTO, but it is impossible to tell what the application is doing. Repetition, micromanagement, and resulting bloat are the rule. This presentation creates and structures a lean and reasonable Java EE/Jakarta EE application from scratch, focuses on responsibilities, and removes any unnecessary noise—without any slides, in continuous coding/continuous explanation style":

See you at Web, MicroProfile and Java EE Workshops at Munich Airport, Terminal 2 or Virtual Dedicated Workshops / consulting. Is Munich's airport too far? Learn from home:

Cloudy Jakarta EE and MicroProfile: Microservices, Clouds and Beyond Jakarta EE / MicroProfile airhacks workshops at MUC airport, Winter Edition the podcast:

Stay in touch:


In your video you mentioned that you don't know an example where exceptions are placed in a package called exceptions.
Here is one:
In the microprofile library microprofile-fault-tolerance-api-1.0.jar there is one package called exceptions which only contains exceptions.

So it does happen even in current libs.

Posted by Niki on November 07, 2018 at 10:11 AM CET #

Hi Niki,

MicroProfile fault tolerance is about dealing with errors, faults and exceptions.

For me it makes sense in this context to have an Exception package -- the whole point of the API is dealing with exceptional conditions.

In the past I was involved in an error handling framework. I guess, it had an exception package as well.

big thanks for your comment,


Posted by Adam Bien on January 05, 2019 at 02:53 PM CET #

Post a Comment:
  • HTML Syntax: NOT allowed
Online Workshops
...the last 150 posts
...the last 10 comments