6 tips for your JavaEE project be less depressing
summary
Five practical moves that make old JavaEE projects livable: accept the app server as your framework and pick a specific vendor instead of fighting the spec; use five tips centered on CDI producer methods and @Asynchronous or ManagedExecutorService to avoid spawning raw threads; cut JPA boilerplate with DeltaSpike Data (Spring Data–style repositories) or drop to jDBI/jOOQ for native or fluent SQL; and build front-end assets with Maven + webjars/npm plugins so designers keep control.
AI-written summary · about
chapters (10)
- 0:00Introduction and context
- 1:10Why Java EE feels depressing
- 8:56Know your Java EE stack
- 10:47Leverage async operations
- 12:34Use CDI for dependency injection
- 14:40Go beyond the Java EE standard
- 20:48Reduce JPA boilerplate with Delta Spike
- 24:47Alternatives to JPA for queries
- 29:47Modern front-end integration
- 37:52Summary and Q&A
related talks
01h 07mThe Java EE-stic Way of Coding
44mJava EE - And The Bloat Is Gone
10mpart1 – Adam Bien
51m5 Tips to Make Your Java Apps More Awesome!
49mJava EEFuture Is Now, But It Is Not Evenly Distributed Yet
51mReal World Lean Java Practices, Patterns, Hacks, and Workarounds
25m5 quick tips to make your Java apps more awesome
55m10 strategies for developing reliable Jakarta EE & MicroProfile apps for the Cloud