@Apoorva64, don't forget to sign your commits! The DCO check is failing at the moment.

There's an issue in tests:

Error creating bean with name 'restInvocationProcessor' defined in file [/home/runner/work/microcks/microcks/webapp/target/classes/io/github/microcks/web/RestInvocationProcessor.class]: Unsatisfied dependency expressed through constructor parameter 4: No qualifying bean of type 'io.opentelemetry.api.OpenTelemetry' available: expected at least 1 bean which qualifies as autowire candidate.

It looks like there's no OpenTelemetry bean loaded in the test context. I wonder if this is mandatory as we should be able to totally disable live traces (when running in uber native within testcontainers for example).

Maybe we should put the RestInvocationProcess constructor argument as @Nullable and add some extra guards to avoid this kind of error?

There's an issue in tests:

Error creating bean with name 'restInvocationProcessor' defined in file [/home/runner/work/microcks/microcks/webapp/target/classes/io/github/microcks/web/RestInvocationProcessor.class]: Unsatisfied dependency expressed through constructor parameter 4: No qualifying bean of type 'io.opentelemetry.api.OpenTelemetry' available: expected at least 1 bean which qualifies as autowire candidate.

It looks like there's no OpenTelemetry bean loaded in the test context. I wonder if this is mandatory as we should be able to totally disable live traces (when running in uber native within testcontainers for example).

Maybe we should put the RestInvocationProcess constructor argument as @Nullable and add some extra guards to avoid this kind of error?

i've fixed the build by creating a resolver which resolves the Opentelemetry bean depending of where it is. When disabling the traces with otel.sdk.disabled it still works, it ignores the traces as expected

i've fixed the build by creating a resolver which resolves the Opentelemetry bean depending of where it is. When disabling the traces with otel.sdk.disabled it still works, it ignores the traces as expected

It works, but it creates yet another bean. Wouldn't it be possible to just use @Nullable? If there is no other comment, I'll merge it like this, but add this point as a refactoring before the release.