Pcc3 api fixes - #48
Merged
Merged
Conversation
…own when the request type is a RetrieveResultObj
…d interface is is agreed for CD3
…se in which the information consumer is not allowed to pull on the given transactionId. It is a responsibility of the serviceRegistry to conduct such check.
… a bad request is reported to the client rather than internal server error
…vant when calling a secom controller incorrectly, we'd want to return 404 and not a 400 as was the case
This file contains hidden or 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
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.
This pull request extends the original one made for the PCC3 API Fixes:
This just speeds things up, implementing the changes requested. Overall this branch brings: