There are some requirements where no message broker is used but just REST endpoints and still data must be mapped to C8Y.
It might get a little bit tricky as the whole interface of a connector in the mapper is designed to support typical pub/sub functionality which obvious does not work for REST where you need to provide endpoints etc.
But thinking about it we can provide a generic REST endpoint @RequestMapping("/**") as part of a mapper and all messages received by that are handled as sub messages by a to be implemented RESTConnector which then allows to use the same UI and mapping capabilities.
The dynamic context path is the mapping key of each mapping.
There are some requirements where no message broker is used but just REST endpoints and still data must be mapped to C8Y.
It might get a little bit tricky as the whole interface of a connector in the mapper is designed to support typical pub/sub functionality which obvious does not work for REST where you need to provide endpoints etc.
But thinking about it we can provide a generic REST endpoint @RequestMapping("/**") as part of a mapper and all messages received by that are handled as sub messages by a to be implemented RESTConnector which then allows to use the same UI and mapping capabilities.
The dynamic context path is the mapping key of each mapping.
Could a evaluated in a hackathon project or PoC.