You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when a DataServiceExecutor interfaces a
KA-BIND endpoint (as opposed to delegating to a KA-TRANSFER endpoint) it will only analyze the status code, but not the status messages returned, but simply utter a warning.
As-Should / Requirement
As an Agent-Enabled Provider, I want to get more meaningful warnings when data/function binding runs into problems in order to decide whether I have a data or a mapping problem.
That is we should try to analyze the specific status messages which we expect from provisioning-agent and remoting-agent and generate more meaningful warnings.
We should also try to find out when such a call generated no/empty result and maybe generate a warning about that such that the status code will not be 200, but 203.
The text was updated successfully, but these errors were encountered:
As-Is / Observation
Currently, when a DataServiceExecutor interfaces a
KA-BIND endpoint (as opposed to delegating to a KA-TRANSFER endpoint) it will only analyze the status code, but not the status messages returned, but simply utter a warning.
As-Should / Requirement
As an Agent-Enabled Provider, I want to get more meaningful warnings when data/function binding runs into problems in order to decide whether I have a data or a mapping problem.
That is we should try to analyze the specific status messages which we expect from provisioning-agent and remoting-agent and generate more meaningful warnings.
We should also try to find out when such a call generated no/empty result and maybe generate a warning about that such that the status code will not be 200, but 203.
The text was updated successfully, but these errors were encountered: