Extensions should bring their own web service

[DominikPinsel]

Hello everyone,

currently the EDC has one web service implemented in the core (jetty). All extensions, that want to provide an API, register their controllers at this extension.
I assume it is better if each extension, that wants to provide an API, brings its own web service.

Improvements would be:

• Better Security by mapping the different parts of the application to different ports (admin, telemetry, health, IDS-Rest, IDS-Multipart, etc.)
• Servlet API available within extension
• Dependency. At the time of writing the IDS-Multipart extension references a Jetty package, to create multipart messages. The Jetty web service extension activates the multipart feature, using the same package.
• No overlapping APIs
• IDS compliance with root path. IDS should return the self-description at the root path. This path is not accessible using the existing Jetty web service implementation.
• Individually configurable (e.g. for non blocking APIs)

_{Dominik Pinsel [email protected], Daimler TSS GmbH, legal info/Impressum}