Skip to content

Add selector type support for sendAndReceive methods in JmsOperations and JmsTemplate #36177

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.

Sign up for GitHub

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

Jump to bottom
Open
pisek wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Add selector type support for sendAndReceive methods in JmsOperations and JmsTemplate #36177

pisek wants to merge 4 commits into from

Conversation

@pisek
Copy link
Contributor

@pisek pisek commented Jan 19, 2026

For explicit response queue we need correlationId to be used.
There are 2 main approaches depending on JMS provider:

  • CORRELATION_ID - correlationId set on request message that JMS provider copies to response message
  • MESSAGE_ID - after sending request, JMS provider assigns messageId to request message and this value is also being copied to correlationId on response message

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Jan 19, 2026
@sbrannen sbrannen added the in: messaging Issues in messaging modules (jms, messaging) label Jan 19, 2026
@jhoeller
Copy link
Contributor

jhoeller commented Jan 19, 2026 •
edited
Loading

Frankly, this adds quite a bit of complexity to the sendAndReceive overloads. At this point I wonder whether the previously introduced sendAndReceive methods without a SelectorType argument (#36162) are even useful on their own? If not, I'd rather revert that addition to 7.0.4, revisiting the topic for 7.1 instead.

If the selector type is commonly configured per provider, it should rather be a JmsTemplate-level setter rather than yet another sendAndReceive argument. Also, it is unusual for JmsTemplate to compose a selector expression - that might be an indication that the functionality should better live on top of JmsTemplate itself.

@jhoeller jhoeller self-assigned this Jan 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@jhoeller jhoeller

Labels

in: messaging Issues in messaging modules (jms, messaging) status: waiting-for-triage An issue we've not yet triaged or decided on

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@pisek @jhoeller @sbrannen @spring-projects-issues