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

JmsMessageReceiverConnection: use of correlationId on request should be configurable [SWS-735] #825

Closed
gregturn opened this issue Oct 6, 2011 · 4 comments
Assignees
Milestone

Comments

@gregturn
Copy link
Member

@gregturn gregturn commented Oct 6, 2011

Henk Hofman opened SWS-735 and commented

Even if a correlation id is specified on a request message in some cases you might want to use the message id of the request message to be used as correlation id (according to the message id pattern, see: http://download.oracle.com/docs/cd/E13171_01/alsb/docs25/interopjms/MsgIDPatternforJMS.html#wp1046209)


Affects: 2.0.2

@gregturn
Copy link
Member Author

@gregturn gregturn commented Oct 6, 2011

Arjen Poutsma commented

You can plug in a MessagePostProcessor into the JmsMessageReceiver, and change the message just before it's sent.

@gregturn
Copy link
Member Author

@gregturn gregturn commented Oct 7, 2011

Henk Hofman commented

Sorry, but that won't do, because you only have the responseMessage in the MessagePostProcessor. To set the messageId of the requestMessage as correlationId on the responseMessage you also need the requestMessage. Do you have any other suggestions to overcome that problem?

@gregturn
Copy link
Member Author

@gregturn gregturn commented Oct 7, 2011

Arjen Poutsma commented

Well, you can always get access to the thread-local transport context, and get access to the request message that way:

TransportContext context = TransportContextHolder.getTransportContext();
JmsReceiverConnection connection = (JmsReceiverConnection) context.getConnection();
Message requestMessage = connection.getRequestMessage();
@gregturn
Copy link
Member Author

@gregturn gregturn commented May 4, 2012

Arjen Poutsma commented

Closing old issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.