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
if the exclude exception list is provided with the fallback annotation, the fallack should not be triggered is the excluded exception occurs. The vice versa should happen for included exception list.
Actual Behaviour
We are using @recoverable and @fallback combination with declarative http client that returns a Publisher. We want fallback to be triggered for all >=4xx HttpClientResponseException except when we encounter a 404 (not found) or 400 (bad request).
Even when we exclude all HttpClientResponseExceptions, the fallback is getting triggered for all HttpResponses.
Please refer to #7153 for more details. This is a draft PR raised some couple of years back but never merged.
Steps To Reproduce
Setup a declarative HttpClient like
@Client( id = "123")
interface TestClient{
@Get
@Produces(APPLICATION_JSON)
@Consumes(APPLICATION_JSON)
@Recoverable
fun getTestData():Publisher<HttpResponse<TestData>>
}
Expected Behavior
if the exclude exception list is provided with the fallback annotation, the fallack should not be triggered is the excluded exception occurs. The vice versa should happen for included exception list.
Actual Behaviour
We are using @recoverable and @fallback combination with declarative http client that returns a Publisher. We want fallback to be triggered for all >=4xx HttpClientResponseException except when we encounter a 404 (not found) or 400 (bad request).
Even when we exclude all HttpClientResponseExceptions, the fallback is getting triggered for all HttpResponses.
Please refer to #7153 for more details. This is a draft PR raised some couple of years back but never merged.
Steps To Reproduce
Setup a declarative HttpClient like
Add a fallback client that extends the same
Environment Information
Mac OS: 14.6.1
JDK: 17
Example Application
No response
Version
Micronaut version 4.6.3
The text was updated successfully, but these errors were encountered: