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

JMS: per message destination support is hard to use, as it is not possible to set the destination #2078

Closed
WellingR opened this issue Jan 7, 2020 · 1 comment

Comments

@WellingR
Copy link
Member

WellingR commented Jan 7, 2020

As part of #1181 support was added to set the destination as part of the message.

Unfortunately since the constructors of the jms messages are no longer public, it is no longer possible to specify the destination when creating a message. Also it is not possible to call a withDestination(destination: Destination) method, as this does not exist.

Unless I am missing something it is only possible to create a message with a destination if this message is created from a javax.jms.Message.

It would be cool if we could introduce a withDestination(destination: Destination) method, or perhaps even an all-args factory method for each type of message

@WellingR
Copy link
Member Author

WellingR commented Jan 7, 2020

It appears that I did miss something
toQueue and toTopic allow me to do this!

@WellingR WellingR closed this as completed Jan 7, 2020
@ennru ennru added the p:jms label Jan 11, 2020
@ennru ennru added this to the invalid/not release-bound milestone Jan 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants