java-cdi

Constructor injection in Jakarta CDI requires following specific rules for single and multiple constructors to ensure proper dependency resolution. This Skill enforces concrete constructor injection rules and documents requirements to prevent misconfigurations in containerized Java applications.

The best way to handle optional dependencies in CDI is using Instance<T> instead of direct injection. This Skill provides guidance on Instance<T> usage to safely resolve optional dependencies without deployment errors in Jakarta CDI projects.

Preventing CDI bean scope mismatch requires enforcing scope safety rules across your beans. This Skill covers proper CDI scope usage and mismatch prevention for real-world scenarios in containerized Jakarta CDI apps like Quarkus and Java EE.

CDI producer methods must enforce non-null returns to satisfy the container's dependency injection contract. This Skill enforces non-null producer requirements and provides guidance on implementing producer methods with qualifiers correctly.

Deterministic interceptor ordering in Jakarta CDI is achieved by applying specific ordering rules and qualifiers to interceptor bindings. This Skill documents and enforces deterministic interceptor ordering to ensure consistent behavior across real-world scenarios.

Yes, you can use CDI events and observers in Quarkus since it supports Jakarta CDI natively. This Skill covers events, observers, and producer methods across real-world scenarios in containerized Jakarta CDI apps like Quarkus and Java EE.