Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(spi): Change unsupported class types in RetryConfig #133

Open
wants to merge 1 commit into
base: quarkus-3.8
Choose a base branch
from

Conversation

edeweerd1A
Copy link
Contributor

It was discovered whilst trying a fix for another issue and refactoring the repository and moving spi classes to runtime. In runtime the Quarkus annotation processor is applied. And it was failing because of this incorrect configuration interface.

This interface was written using the fields of the org.eclipse.microprofile.faulttolerance.Retry annotation. And one can set Class object as type of fields of annotation. It is however not supported by microprofile-config.

This will have no effect as such, as those configuration entries are directly injected as configuration entries linked to the retryable method of io.quarkiverse.kafkastreamsprocessor.impl.decorator.processor.RetryDecoratorDelegate.

It was discovered whilst trying a fix for another issue and refactoring the repository and moving spi classes to runtime.
In runtime the Quarkus annotation processor is applied.
And it was failing because of this incorrect configuration interface.

This interface was written using the fields of the `org.eclipse.microprofile.faulttolerance.Retry` annotation.
And one can set `Class` object as type of fields of annotation.
It is however not supported by `microprofile-config`.

This will have no effect as such, as those configuration entries are directly injected as configuration entries linked to the retryable method of `io.quarkiverse.kafkastreamsprocessor.impl.decorator.processor.RetryDecoratorDelegate`.
@edeweerd1A edeweerd1A requested a review from a team as a code owner October 30, 2024 13:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant