Vidocq Documentation
Version

New in the 0.4.0-SNAPSHOT development line — everything listed here landed after the 0.3.0 release and is not part of it. Every entry links to the section that documents it, and those sections carry the NEW badge. Each brick of the suite keeps its own page of this kind; the ecosystem index gathers them. When the next release train ships, this page is frozen with it and restarts empty on the dev line.

CDI containers other than Vauban

  • Explicit bean archives — dirac-cdi-vauban and dirac-rest now ship a META-INF/beans.xml (bean-discovery-mode="annotated") (DRC-003, dirac#23). 0.3.0 shipped none, so the jars were implicit bean archives: Weld SE, which does not scan those by default, saw neither the @Counted / @Timed interceptors nor the MetricRegistry producer nor the GET /metrics resource, and metrics silently stayed empty. Nothing changes under Vauban. Bean archives.

  • Proven on Weld and Open Liberty — two new test modules run the Dirac jars, unchanged, without Vauban: dirac-it-weld on Weld SE 6.0 (class path, plus two containers in one JVM) and dirac-it-openliberty as a WAR on Open Liberty 26.0.0.10 (MicroProfile 7, CDI 4.0) with Liberty’s own mpMetrics off. Neither is published (dirac#23). Other CDI containers.

  • vauban-api is now a runtime dependency of dirac-cdi-vauban and dirac-rest — it was provided, so outside Vauban the registry producer, the gauge registration and the /metrics resource could not be loaded, and the deployment failed (DRC-004). It no longer brings the CDI API: an application that compiled against CDI through Dirac alone now declares jakarta.enterprise.cdi-api itself (the Vidocq runtime is not affected). Other CDI containers.

  • Two containers keep their metrics apart — the metrics DiracExtension discovers used to live in static sets, shared by every container of the class loader: two applications starting together on one server could register each other’s gauges. They now belong to each container (DRC-005). Internals.

  • Open Liberty can deploy an application with Dirac — the extension also visits the server’s own beans there, and reported every one it could not load as an error, which failed the deployment. Those classes are now skipped (DRC-006). Other CDI containers.