Cdi from monolith to module
0 likes•294 views
This document discusses the past, present, and future of the Contexts and Dependency Injection (CDI) specification. It outlines how CDI started as part of Java EE and is now a cornerstone of MicroProfile. It also describes how CDI 2.0 supports standalone Java applications and the future work to make CDI compatible with Java module systems like Jigsaw. Key points covered include enhancing CDI's SPI, adding support for asynchronous bean resolution, and a three step approach to migrating CDI applications to use Java modules.
![@antoine_sd
CDI 2.0 brings CDI SE into play
public static void main(String[] args) {
SeContainer container = SeContainerInitializer.newInstance()
.disableDiscovery()
.addBeanClasses(MyService.class)
.initialize();
MyService service = container.select(MyService.class).get();
service.sayHello();
container.close();
}](https://image.slidesharecdn.com/cdifrommonolithtomodule-181113175950/85/Cdi-from-monolith-to-module-9-320.jpg)
Cdi from monolith to module
- 1. @antoine_sd CDI from monolith to modularity Antoine Sabot-Durand Red Hat CDI spec lead
- 2. @antoine_sd Me, Myself and I Antoine Sabot-Durand Java Champion at Red Hat Commiter on MicroProfile CDI spec lead Follow me: @antoine_sd Follow CDI: @cdispec
- 3. @antoine_sd Agenda The Past CDI as part of Java EE The Present CDI as part of Microprofile CDI 2.0 on Java SE The future CDI in modular application
- 5. @antoine_sd CDI Timeline Dec 2009 June 2013 Apr 2014 Sep 2014 CDI1.0 (Java EE 6) CDI1.1 (Java EE 7) CDI1.2 (1.1 MR) CDI2.0 Starts Mai 2017 CDI2.0 released
- 6. @antoine_sd CDI 1.x corner stone for Java EE From Java EE 6 to Java EE 7, CDI has became centric thanks to: Powerful SPI EJB integration (to switch from EJB to CDI) Events
- 8. @antoine_sd CDI corner stone for MicroProfile MicroProfile is built on top of CDI and JAX-RS MicroProfile 2.0 adopted CDI 2.0 (latest version MicroProfile 2.1)
- 9. @antoine_sd CDI 2.0 brings CDI SE into play public static void main(String[] args) { SeContainer container = SeContainerInitializer.newInstance() .disableDiscovery() .addBeanClasses(MyService.class) .initialize(); MyService service = container.select(MyService.class).get(); service.sayHello(); container.close(); }
- 11. @antoine_sd CDI Future is multiple Enhance CDI SPI to provide a better integration with other specs Make CDI more reactive (i.e. support asynchronous bean resolution) Make CDI app Jigsaw compatible
- 12. @antoine_sd CDI Future is multiple Enhance CDI SPI to provide a better integration with other specs Make CDI more reactive (i.e. support asynchronous bean resolution) Make CDI development Jigsaw (JPMS) compatible
- 13. @antoine_sd Why CDI + JPMS? To reduce deployment size for MicroServices To Produce standalone images with Jlink As CDI is centric moving in that direction will impact MicroProfile
- 14. @antoine_sd Catching up on JPMS JPMS = Modularized JDK and modules for your applications Strong encapsulation Clearly defined APIs Explicit relationships
- 15. @antoine_sd 3 steps to move to JPMS Build on Java 9+ Move to automatic modules Move to named modules
- 16. @antoine_sd 3 steps to move to JPMS Step 1 - Build on Java 9: The class path still exists! Often works fine Be wary of Java EE dependences (JAXB, @Generated etc.) and jdk.unsupported Time for some clean-up Watch out for illegal access warnings Remove split packages Remove circular dependencies (services can help)
- 17. @antoine_sd 3 steps to move to JPMS Step 2 - Automatic Modules Use non-modular JARs on module path Read all resolved modules and the classpath ("UNNAMED" module) Export all packages Define module name via Automatic-Module-Name manifest entry Send patches to your deps with module name in MANIFEST.MF
- 18. @antoine_sd 3 steps to move to JPMS Step 3 - Named Modules Declare module-info descriptor No Jlink image without named module Carefully decide on API dependences ("Do I really need java.desktop?") ModiTect is a tool that can help you to do that
- 19. @antoine_sd Anatomy of a module descriptor module com.example { requires java.sql; requires joda.time; requires com.google.guava; exports com.example.foo; exports com.example.foo.bar; exports com.example.foo.baz; uses com.acme.SomeService; provides com.acme.AnotherService with com.example.internal.MyServiceImpl; }
- 20. @antoine_sd Moditect A project developed by Gunnar Morling https://github.com/moditect/moditect Provides a Maven Plugin Useful tool to add modularity to non modular jar Also useful to produce jlink image
- 21. Demo
- 22. @antoine_sd CDI-JLINK repo CDI-JLINK repo is here: https://github.com/antoinesd/cdi-jlink Don’t skip the readme !