Petals ESB Container

Move the dedicated configuration parameters linked to the Petals ESB initial registry from the local container configuration

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 4.2.0
  • Fix Version/s: 5.0.0
  • Security Level: Public
  • Description:

    Some parameters of the Petals Initial registry are defined into the local container configuration and are defined as attribute of class ContainerConfiguration. They must be moved as extension parameters, and removed from ContainerConfiguration

  • Environment:
    -

Issue Links

Activity

Hide
Christophe DENEUX added a comment - Wed, 4 Jun 2014 - 09:05:00 +0200

As the initial registry has been replaced by a registry based on Hazelcast, it is not planned to move the parameters:

  • the parameters also used by the persistence service will be renamed as petals.persistence.xxx,
  • the parameters dedicated to the initial registry implementation will be removed from the Petals µKernel.
Show
Christophe DENEUX added a comment - Wed, 4 Jun 2014 - 09:05:00 +0200 As the initial registry has been replaced by a registry based on Hazelcast, it is not planned to move the parameters:
  • the parameters also used by the persistence service will be renamed as petals.persistence.xxx,
  • the parameters dedicated to the initial registry implementation will be removed from the Petals µKernel.
Hide
Christophe DENEUX added a comment - Wed, 4 Jun 2014 - 09:29:09 +0200

Parameters reworked in trunk

Show
Christophe DENEUX added a comment - Wed, 4 Jun 2014 - 09:29:09 +0200 Parameters reworked in trunk

People

Dates

  • Created:
    Wed, 4 Jun 2014 - 09:01:36 +0200
    Updated:
    Wed, 4 Jun 2014 - 09:29:09 +0200
    Resolved:
    Wed, 4 Jun 2014 - 09:29:09 +0200