Vidocq

Vidocq

@vidocq.dev

The first sovereign European Jakarta EE Core Profile 11 and MicroProfile 7.1 runtime, built on JDK 25.

31 followers20 following13 posts

Vidocq reposted

A solution we have to test for @vidocq.dev JLink images deployment in #k8s. Looks great !

Bruno Borges@brunoborges.bsky.social

$ kubectl patch deployment myjvmapp --type=merge -p '{"spec":{"template":{"metadata":{"annotations":{"brewlet.sh/jdk":"temurin-27"}}}}}' And now the same app is running with JDK 27 without having to rebuild/repackage/republish/redeploy the container image. brewlet.sh

Vidocq reposted

75 years of experience on stage at @devoxx.com to present the story of #Vidocq the edgy stack based on #Jakarta_EE #MicroProfile #Java_25 #Virtual_Threads #Java_Modules #NoDependencies #Sovereignty #Java_Mammoths

youtu.beCan AI Build a Jakarta EE Runtime? The Vidocq Experiment by Antoine Sabot Durand, yann Blazart, SebaYouTube video by Devoxx
SCIAM@sciam.fr

Hier après midi, un trio de choc était sur scène pour présenter l'histoire de #Vidocq la nouvelle stack #Jakarta_EE et #MicroProfile qui fait du neuf avec du vieux

Vidocq reposted

#CDI issue #1015: your @ApplicationScoped bean has a package-private method. The proxy must live in the same package — but that package belongs to someone else. How #Vauban solves it without opens, without ASM, without reflection:

vidocq.devOne App, Every Proxy Case: Where Your CDI Proxies Actually Come FromA normal-scoped bean is never handed out directly — a generated subclass is. Where it comes from depends on one thing only, the origin of the type being proxied: your own code, a modular dependency, a...

Vidocq reposted

We’ve been waiting for a long time but thanks to #Vidocq, it’s “The Return of #CDI” #Vauban #JakartaEE #Microprofile #Java

You are up to date.