[FIX] request parameter -> request header #7
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
avikganguly01
requested changes
Dec 29, 2021
| @@ -40,7 +40,7 @@ public Batch batchDetails(@RequestParam String batchId, @RequestParam String req | |||
| } | |||
|
|
|||
| @GetMapping("/batch/transactions") | |||
| public HashMap<String, String> batchTransactionDetails(@RequestParam String batchId) { | |||
| public HashMap<String, String> batchTransactionDetails(@RequestHeader("batchId") String batchId) { | |||
There was a problem hiding this comment.
Batch id should be a request parameter and not a header.
There was a problem hiding this comment.
Unable to set request parameter in camel route of bulk processor. That's why using request header.
|
@SubhamPramanik : Please review. I want to make sure this doesn't have any regression on bulk processor. |
|
stale PR |
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.
@avikganguly01
@SubhamPramanik
Please review