Fix ESBJAVA-5138 #831
Merged
Fix ESBJAVA-5138 #831
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The trasnaction id used for the communication between SAP and the SAPTransaportSender to send IDOCs can be of intereset when it comes to responding to the client back in a Proxy. It could be used to track what transactions were successful and what failed. The improvement was to set it as a transport header to the synapse context so that it can be refererded to, in the synapse sequence. Addresses the issue at: https://wso2.org/jira/browse/ESBJAVA-5138
milindaperera
approved these changes
Jul 10, 2017
maheeka
approved these changes
Jul 10, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The trasnaction id used for the communication between SAP and the
SAPTransaportSender to send IDOCs can be of intereset when it comes to
responding to the client back in a Proxy. It could be used to track
what transactions were successful and what failed. The improvement was
to set it as a transport header to the synapse context so that it can
be refererded to, in the synapse sequence.
Addresses the issue at: https://wso2.org/jira/browse/ESBJAVA-5138