Skip to content

Conversation

@quaff
Copy link
Contributor

@quaff quaff commented Jan 26, 2026

  1. Fix wrong type name in assertion message.
  2. Rename retryTemplate to retryOperations to match type better.

1. Fix wrong type name in assertion message.
2. Rename `retryTemplate` to `retryOperations` to match type better.

Signed-off-by: Yanming Zhou <zhouyanming@gmail.com>
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Jan 26, 2026
@jhoeller
Copy link
Contributor

Well spotted - however, while this is debatable, it is actually intentional. JdbcClient and JmsClient follow the same pattern of accepting Operations interfaces while suggesting the Template classes both in the parameter name and the assertion message. The rationale is that the common thing to pass in there is a template instance, with the operations interface primarily declared for testability. In other words, the operations interface is just a facade for a specific template rather than an independent contract.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status: waiting-for-triage An issue we've not yet triaged or decided on

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants