Making the most of Java SE with CDI 2.0
summary
CDI 2.0 makes CDI usable in plain Java SE by standardizing an SE container (Weld and OpenWebBeans implement it) that boots with two lines to bootstrap and is auto-closeable for try-with-resources. It lets code add packages, extensions and properties programmatically, control discovery, and start/stop request scope via a request context controller or an interceptor. Demo builds a Netty TCP listener with a request-scoped time provider showing fresh instances per connection, fully CDI-only and working without a Java EE container.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:38Projects Supporting CDI SE
- 5:32Controlling the Classpath You can disable discovery, and explicitly add beans
- 8:24Request Context
- 11:10Threading and Events
related talks
04mDiscusses CDI 2.0
43mWhat's New in CDI 4.0?
53mJava EE 8 and the Open Future of Java EE - What You Need to Know!
55mModern and Lightweight Cloud Application Development with Jakarta EE10
51mModern and Lightweight Cloud Application Development with Java and Jakarta EE
50mJakarta EE 10: Modern & Lightweight Cloud Application Development
45mEverything YOU need to Know About Jakarta EE 10
42mCloud Native Java EE