Petals ESB Container

The container configuration should be read by the petals launchers and not by the kernel itself

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 3.1
  • Fix Version/s: 4.2.0
  • Component/s: Configuration, Launcher
  • Security Level: Public
  • Description:
    Hide

    To anticipate on the next 'Petals Micro Kernel', the container configuration should be read by Petals launcher instead of the Petals kernel:
    1/ The petals launcher will read the container configuration property file,
    2/ The petals launcher will launch the petals kernel using this propertie as parameters

    Show
    To anticipate on the next 'Petals Micro Kernel', the container configuration should be read by Petals launcher instead of the Petals kernel: 1/ The petals launcher will read the container configuration property file, 2/ The petals launcher will launch the petals kernel using this propertie as parameters
  • Environment:
    -

Issue Links

Duplicate
 

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Sébastien André added a comment - Thu, 4 Nov 2010 - 16:59:49 +0100

I think the package org.ow2.petals.launcher.configuration from revision 16165 can resolve this issue.

There are two configuration methods that are used now, because except for the launcher, other classes still use the former configuration from APIs.

We should only use one of these two methods

Show
Sébastien André added a comment - Thu, 4 Nov 2010 - 16:59:49 +0100 I think the package org.ow2.petals.launcher.configuration from revision 16165 can resolve this issue. There are two configuration methods that are used now, because except for the launcher, other classes still use the former configuration from APIs. We should only use one of these two methods
Hide
Permalink
Christophe DENEUX added a comment - Fri, 5 Nov 2010 - 09:29:43 +0100

I think that it will be better to define configuration classes into the project 'petals-kernel-api'

Show
Christophe DENEUX added a comment - Fri, 5 Nov 2010 - 09:29:43 +0100 I think that it will be better to define configuration classes into the project 'petals-kernel-api'
Hide
Permalink
Roland Naudin added a comment - Fri, 5 Nov 2010 - 10:12:48 +0100

+1
But i still think that there is 2 kind of configuration.
Topologic configuration that need to be share amongst the Petals domain (static/dynamic...) and can be different according to the topology mode.

Local configuration that regards only the local container.

I think we must distinguish this 2 kind of conf, as they are handled differently in the kernel, or micro-kernel, what ever you call it.

Show
Roland Naudin added a comment - Fri, 5 Nov 2010 - 10:12:48 +0100 +1 But i still think that there is 2 kind of configuration. Topologic configuration that need to be share amongst the Petals domain (static/dynamic...) and can be different according to the topology mode. Local configuration that regards only the local container. I think we must distinguish this 2 kind of conf, as they are handled differently in the kernel, or micro-kernel, what ever you call it.
Hide
Permalink
Christophe DENEUX added a comment - Fri, 5 Nov 2010 - 10:27:25 +0100

Yes, two kind of configuration information:
1/ topologic configuration (ie: topology.xml)
2/ local configuration (ie: server.properties + logger.properties)

Show
Christophe DENEUX added a comment - Fri, 5 Nov 2010 - 10:27:25 +0100 Yes, two kind of configuration information: 1/ topologic configuration (ie: topology.xml) 2/ local configuration (ie: server.properties + logger.properties)

People

Dates

  • Created:
    Fri, 10 Sep 2010 - 22:10:59 +0200
    Updated:
    Tue, 12 Mar 2013 - 08:27:21 +0100
    Resolved:
    Tue, 12 Mar 2013 - 08:26:22 +0100
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.