[ANN] Vidocq — MicroProfile 7.1 + Jakarta EE Core Profile 11 implementation, now open source
ant...@sabot-durand.net
Dear MicroProfile community,
We are pleased to announce the open source release of Vidocq, a new independent implementation of MicroProfile 7.1 and Jakarta EE Core Profile 11, built from scratch on Java 25.
This implementation was mainly created by my colleague Yann Blazart and I, with major help from AI (Claude and GitHub Copilot).
The project is available at codeberg.org/Vidocq (EUPL 1.2 / EPL 2 / GPL 2.0) and documented at vidocq.dev. It is currently in alpha. Vidocq is the first European MicroProfile implementation (sovereignty was one of our goals).
What makes it different
Three non-negotiable constraints drove the implementation from day one:
- Zero external dependencies outside the Jakarta and MicroProfile spec APIs. No Netty, no ASM, no ByteBuddy, no SmallRye.
- Strict JPMS throughout: every module ships an explicit module-info.java, minimal exports, no classpath fallback.
- Java 25 virtual threads as the only concurrency model, with ScopedValue replacing ThreadLocal everywhere. All CDI proxies, JSON-B bindings, REST client proxies and Data repositories are generated at compile time via the Class-File API (JEP 484). No runtime reflection in production.
TCK status
Every completed specification passes its TCK at 100%, across 5,650 tests in total:
- Core Profile: CDI 4.1 Lite (774), Jakarta REST 4.0 (2535), JSON-P 2.1 (178), JSON-B 3.0 (289), Servlet 6.1 (1261, still in progress), Config 3.1 (349)
- MicroProfile: Fault Tolerance 4.1 (463), JWT 2.1 (206), REST Client 4.0 (168), Metrics 5.1.1 (127), OpenAPI 4.1 (349), Telemetry 2.1 (85), Health 4.0 (28), Config 3.1 (349)
No disabled test. No spec workaround.
On the development method
Vidocq was largely built with AI assistance (Claude and GitHub Copilot), using the TCK as the external referee at each step. The constraints were deliberately designed to be AI-hostile in the right way: no library shortcut, no reflection fallback, no approximation that a passing unit test might hide. Getting to 100% required significant human work to interpret the specs, challenge the AI's output and track down subtle conformance failures.
The full account of the experiment, from the CDI prototype at JChateau in March 2026 to today's release, is available here: vidocq.dev/posts/the-story-of-vidocq. This post also contains a tribute to all spec teams on the EE Core Profile and MicroProfile. Without years of that work, this spec-driven experiment, which became an actual project, would not have been possible.
We are happy to engage on any TCK issues, challenge submissions, or specification ambiguities that arise from our work.
Antoine Sabot-Durand and Yann Blazart
John Clingan
Have you submitted, or do you plan to submit, any CCRs?
Emily Jiang
--
You received this message because you are subscribed to the Google Groups "MicroProfile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/microprofile/9c487c18-4fba-40c1-8340-6954d3e16bdcn%40googlegroups.com.
--
Emily
Michael Redlich
--
You received this message because you are subscribed to the Google Groups "MicroProfile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/microprofile/9c487c18-4fba-40c1-8340-6954d3e16bdcn%40googlegroups.com.