Multiple implementations of ResponseInterceptor fail to trigger

[marcdv]

Describe the bug
I have 2 implementations of ResponseInterceptor, both fail to trigger in 4.1.0. If I remove one of them, then it works.

@Component
public class AuditorGatewayResponseInterceptor implements ResponseInterceptor {

//// removed
}

@Component
public class AnotherResponseInterceptor implements ResponseInterceptor {

//removed
}

[OlgaMaciaszek]

Hello @marcdv, thanks for creating an issue. Please provide a minimal, complete, verifiable example that reproduces the issue, as a link to a GitHub repo with an executable app or tests.

Please learn how to properly format code and logs.

[spring-cloud-issues]

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

[galaxy-sea]

hello @marcdv , see gh-1003

[marcdv]

Please review https://github.com/marcdv/testFeign for an example

Steps to reproduce

1. Start the server
   gradle bootrun

2. call the API
   GET http://localhost:8080/api/test

3. Review logs in console (note no logs)

4. Comment out line 10 (@component) in AResponseInterceptor.java

5. Restart the server

6. Call the API as above

7. Review logs (note BResponseInterceptor was called)

[OlgaMaciaszek]

Thanks, @marcdv. That's actually never been supported and also the docs only show a way to provide one interceptor, so this would be an enhancement. Since this project is now in maintenance mode (suggested replacement: Spring Interface Clients), we are not planning on adding new features ourselves, but we still review small community PR. I see @galaxy-sea has submitted a PR for this, but it has breaking changes, so can only be considered for a major release and I will mark it as such, however at this point it has not been decided if there will be another major of this project.