Petals ESB Container

The HTTP server Jetty embedded into the Petals ESB container should be an extension

Details

  • Type: Task Task
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 4.1.0
  • Fix Version/s: 5.0.1
  • Component/s: Registry, WS API
  • Security Level: Public
  • Description:
    Hide

    A servlet container is embedded into the Petals ESB container. Nowadays, it is required only by the WS-API.
    So, it is not needed if the extension WS API is not installed.
    So, it should be provided itself as an extension and could be used by other extensions

    Show
    A servlet container is embedded into the Petals ESB container. Nowadays, it is required only by the WS-API. So, it is not needed if the extension WS API is not installed. So, it should be provided itself as an extension and could be used by other extensions
  • Environment:
    -

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Tue, 9 Apr 2013 - 11:50:55 +0200

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.

Show
Christophe DENEUX added a comment - Tue, 9 Apr 2013 - 11:50:55 +0200 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.
Hide
Permalink
Christophe Hamerling added a comment - Tue, 9 Apr 2013 - 12:18:37 +0200

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

Show
Christophe Hamerling added a comment - Tue, 9 Apr 2013 - 12:18:37 +0200 Do not forget that we can imagine having a HTTP transporter which is using a HTTP server already running in the Petals container.
Hide
Permalink
Christophe DENEUX added a comment - Wed, 10 Apr 2013 - 22:41:07 +0200

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 ?

Show
Christophe DENEUX added a comment - Wed, 10 Apr 2013 - 22:41:07 +0200 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 ?
Hide
Permalink
Christophe DENEUX added a comment - Wed, 12 Mar 2014 - 18:23:55 +0100

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.

Show
Christophe DENEUX added a comment - Wed, 12 Mar 2014 - 18:23:55 +0100 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.
Hide
Permalink
Victor NOËL added a comment - Fri, 2 Oct 2015 - 13:47:13 +0200 - edited

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

Show
Victor NOËL added a comment - Fri, 2 Oct 2015 - 13:47:13 +0200 - edited This was fixed when the registry was extracted from the container (see PETALSESBCONT-272)
Hide
Permalink
Christophe DENEUX added a comment - Fri, 2 Oct 2015 - 14:28:41 +0200

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

Show
Christophe DENEUX added a comment - Fri, 2 Oct 2015 - 14:28:41 +0200 First point fixed. This issue is reopened for the second point.
Hide
Permalink
Christophe DENEUX added a comment - Mon, 5 Oct 2015 - 15:54:48 +0200

Postponed to 5.0.1 or upper

Show
Christophe DENEUX added a comment - Mon, 5 Oct 2015 - 15:54:48 +0200 Postponed to 5.0.1 or upper
Hide
Permalink
Christophe DENEUX added a comment - Mon, 23 May 2016 - 15:12:00 +0200

Fixe by PETALSESBCONT-415

Show
Christophe DENEUX added a comment - Mon, 23 May 2016 - 15:12:00 +0200 Fixe by PETALSESBCONT-415

People

Dates

  • Created:
    Tue, 9 Apr 2013 - 11:48:03 +0200
    Updated:
    Mon, 23 May 2016 - 15:12:00 +0200
    Resolved:
    Mon, 23 May 2016 - 15:12:00 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.