You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The codecs.isResolvable() checks if there is exactly one implementation of a Codec resolvable, so if more than one codec is resolvable no codec is registered.
Expected behavior
All custom codecs should be registered.
Actual behavior
If more than one bean implements the Codec interface, no custom codec is registered.
How to Reproduce?
Create two beans implementing the Codec interface and check if the codec is registered.
Output of uname -a or ver
No response
Output of java -version
17
GraalVM version (if different from Java)
No response
Quarkus version or git rev
3.3.1
Build tool (ie. output of mvnw --version or gradlew --version)
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
According to the documentation of the redis-client extenstion, custom codecs can be registered, see https://quarkus.io/guides/redis-reference#custom-codec .
However when more than one bean implementing the
Codec
interface is present, noCodec
is registered.The problem seems to be the in the
RedisClientRecorder
class:quarkus/extensions/redis-client/runtime/src/main/java/io/quarkus/redis/runtime/client/RedisClientRecorder.java
Line 68 in 45d914a
The
codecs.isResolvable()
checks if there is exactly one implementation of aCodec
resolvable, so if more than one codec is resolvable no codec is registered.Expected behavior
All custom codecs should be registered.
Actual behavior
If more than one bean implements the
Codec
interface, no custom codec is registered.How to Reproduce?
Create two beans implementing the
Codec
interface and check if the codec is registered.Output of
uname -a
orver
No response
Output of
java -version
17
GraalVM version (if different from Java)
No response
Quarkus version or git rev
3.3.1
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: