We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Add a list of termination reasons to TransferTerminationMessage and ContractNegotiationTerminationMessage.
TransferTerminationMessage
ContractNegotiationTerminationMessage
String rejectionReason
spi, protocol services
According to the spec, both messages support an optional list of termination reasons. Those are of type object. The spec doesn't define the schema.
object
Introduce a class that can be extended if needed (e.g., predefined enums like in StoreFailure):
StoreFailure
public class ProtocolServiceFailure extends Failure { private final String reason; ... }
Add mapping in dsp transformers.
The text was updated successfully, but these errors were encountered:
Should be List<Object> reasons for now.
List<Object> reasons
Sorry, something went wrong.
This issue is stale because it has been open for 14 days with no activity.
This issue was closed because it has been inactive for 7 days since being marked as stale.
No branches or pull requests
Feature Request
Add a list of termination reasons to
TransferTerminationMessage
andContractNegotiationTerminationMessage
.TransferTerminationMessage
String rejectionReason
inContractNegotiationTerminationMessage
Which Areas Would Be Affected?
spi, protocol services
Why Is the Feature Desired?
According to the spec, both messages support an optional list of termination reasons. Those are of type
object
. The spec doesn't define the schema.Solution Proposal
Introduce a class that can be extended if needed (e.g., predefined enums like in
StoreFailure
):Add mapping in dsp transformers.
The text was updated successfully, but these errors were encountered: