Petals ESB Container

Fixe by PETALSESBCONT-415

Postponed to 5.0.1 or upper

First point fixed.
This issue is reopened for the second point.

This was fixed when the registry was extracted from the container (see PETALSESBCONT-272)

Since Petals ESB 4.1:

• the WS-API is an extension,
• the Jetty dependency is declared at kernel level, and excluded at WS-API level.

So, in a first step we can remove the Jetty dependency from Petals kernel, and remove the exclusion from the WS-API to reduce the size of Debian package 'Petals ESB'.
In a 2nd step, we can introduce Jetty as an extension providing an HTTP server to reduce resource consumption: the HTTP transporter and the WS-API using the same HTTP server.

You are right. I imagine a such transporter requiring the extension "HTTP server" (the extension of this issue). But how configure a such extension ? Can we imagine having two HTTP server, on different port, one for WS-API, and another one for the HTTP transporter ? It should be better to have only one HTTP server. If the HTTP transporter is not used, it will be strange to configure the WS API through the topology.
Have you any idea ?

Do not forget that we can imagine having a HTTP transporter which is using a HTTP server already running in the Petals container.

The configuration of the http server must be reviewed because it is located into the topology.
In my mind, it should be moved in the server.properties because the only available communications between containers are JMX and the remote transporter.