Closed rokkolesa closed 1 week ago
/cc @alesj (kafka), @cescoffier (kafka), @ozangunalp (kafka)
@ozangunalp @Ladicek Do you think we can extend the detection to handle this case?
Yes, that should be possible.
For the Instance
injection we do support the recognition of the Emitter in Quarkus (as opposed to upstream), so that's not a problem.
For serde detection, it should not be a problem.
Describe the bug
When injecting an
Emitter
orMutinyEmitter
wrapped inInstance
, the serializer is not autodetected and instead fails the application startup.Expected behavior
I expect that it should not matter if the emitter is injected directly or via
Instance
regarding the serializer autodetection.Actual behavior
The application startup fails with the error:
If i instead inject the emitter directly, the error is not thrown and the emitter works correctly.
How to Reproduce?
Using the below snippet causes an exception at startup, even if the bean is not used.
Output of
uname -a
orver
No response
Output of
java -version
openjdk version "21.0.5" 2024-10-15 OpenJDK Runtime Environment Homebrew (build 21.0.5) OpenJDK 64-Bit Server VM Homebrew (build 21.0.5, mixed mode, sharing)
Quarkus version or git rev
3.16.3
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.9.9
Additional information
I can work around this issue by specifying
mp.messaging.outgoing.foo_out.value.serializer=io.quarkus.kafka.client.serialization.ObjectMapperSerializer
inapplication.properties
.