ArC | Matheus Oliveira

Inside ArC, part 2: proxies, interceptors and the bean that vanished

A constructor that runs twice, an interceptor that works even on internal calls and a bean that doesn’t even exist at runtime. In part 2 of this ArC deep dive, I show what the Quarkus build changes in application code.

Illustration of an editor window with lines of code connected by an electric arc to a grid of blocks representing the generated bytecode

Inside ArC, part 1: the Quarkus CDI that runs before your code does

I opened the bytecode Quarkus generates for CDI to see what the container does before the application starts. Part one of a deep dive into ArC with real experiments: discovery, validation and a create() that is just a new.