Feature Request
Currently, the CallbackEventDispatcher can be defined dynamically on the event (e.g. by defining it on the ContractNegotiation/TransferProcess on the initiation) or statically through configuration/extension.
For the latter, a global dispatcher can be registered, but not one specific to the participantContextId, if that, all the events will be dispatched to a common endpoint.
To permit different participants to define events related to themselves, it should be possible to define the participantContextId on the callback, in that case, only events with a particular participantContextId or events without participantContextId will be dispatched to that callback.
Which Areas Would Be Affected?
e.g., DPF, CI, build, transfer, etc.
Why Is the Feature Desired?
Are there any requirements?
Who will sponsor this feature?
Please @-mention the committer that will sponsor your feature.
Solution Proposal
If possible, provide a (brief!) solution proposal.
Feature Request
Currently, the
CallbackEventDispatchercan be defined dynamically on the event (e.g. by defining it on the ContractNegotiation/TransferProcess on the initiation) or statically through configuration/extension.For the latter, a global dispatcher can be registered, but not one specific to the
participantContextId, if that, all the events will be dispatched to a common endpoint.To permit different participants to define events related to themselves, it should be possible to define the
participantContextIdon the callback, in that case, only events with a particularparticipantContextIdor events withoutparticipantContextIdwill be dispatched to that callback.Which Areas Would Be Affected?
e.g., DPF, CI, build, transfer, etc.
Why Is the Feature Desired?
Are there any requirements?
Who will sponsor this feature?
Please @-mention the committer that will sponsor your feature.
Solution Proposal
If possible, provide a (brief!) solution proposal.