In GitLab by @barry.nouwt.tno.nl on Oct 26, 2023, 11:17
For example, when a reactive service is implemented and incoming bindings are invalid (because a datetime is in the past, or because an device ID is not found) it would be good if this information flows back to the proactive side. The ExchangeInfo is a good mechanism for this, but currently there is no way for users of the KE REST API to return an error message that ends up in the Exchange Info.
The users of the KE Java API can already throw an Exception from the ReactHandler that ends up in the ExchangeInfo.
Improve the KE REST API with such a feature.
In GitLab by @barry.nouwt.tno.nl on Oct 26, 2023, 11:17
For example, when a reactive service is implemented and incoming bindings are invalid (because a datetime is in the past, or because an device ID is not found) it would be good if this information flows back to the proactive side. The ExchangeInfo is a good mechanism for this, but currently there is no way for users of the KE REST API to return an error message that ends up in the Exchange Info.
The users of the KE Java API can already throw an
Exceptionfrom theReactHandlerthat ends up in the ExchangeInfo.Improve the KE REST API with such a feature.