Petals ESB Container

Externalize the registry implementation

View this issue in another formatViewView
- XML
- Word
- Printable

Details

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

Description:
Hide
Externalize the registry implementation in a dedicated project:

to continue the development of the Petals µKernel,

to be able to change easily the implementation of the registry.

The registry implementation is selected according the following rules:

the registry implementation configured in the topology definition (as the registry is distributed, it must be the same on each Petals ESB node)

otherwise, if no registry implementation is configured, the registry implementation available on the classpath is used.

If an error occurs, the Petals ESB node startup is aborted.
Show
Externalize the registry implementation in a dedicated project:

to continue the development of the Petals µKernel,

to be able to change easily the implementation of the registry.

The registry implementation is selected according the following rules:

the registry implementation configured in the topology definition (as the registry is distributed, it must be the same on each Petals ESB node)

otherwise, if no registry implementation is configured, the registry implementation available on the classpath is used.

If an error occurs, the Petals ESB node startup is aborted.

Environment:

-

Issue Links

Depends

This issue depends on:
~~PETALSESBCONT-268~~ The registry should be a sub-component of the composite "System"
~~PETALSESBCONT-269~~ Add a controller in the Petals composite
~~PETALSESBCONT-271~~ Create a Debian package to install the registry implementation 'Initial registry'
~~PETALSESBCONT-272~~ Externalize the initial registry implementation in a dedicated project
~~PETALSESBCONT-273~~ Move the registry synchronization as an administration operation of the Petals ESB initial registry
~~PETALSESBCONT-274~~ Remove the dedicated configuration parameters linked to the Petals ESB initial registry from the topology
~~PETALSESBCONT-304~~ Move the dedicated configuration parameters linked to the Petals ESB initial registry from the local container configuration

This issue blocks:
~~PETALSESBCONT-276~~ Make the topology dynamic
~~PETALSESBCONT-275~~ Create a Petals ESB Registry based on a Hazelcast cluster

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Christophe DENEUX added a comment - Wed, 13 Nov 2013 - 11:53:09 +0100

The registry is dynamically loaded in the trunk: svn#35853

Show

Christophe DENEUX added a comment - Wed, 13 Nov 2013 - 11:53:09 +0100 The registry is dynamically loaded in the trunk: svn#35853

People

Assignee:

Christophe DENEUX

Reporter:

Christophe DENEUX
Watchers:

0

Dates

Created:

Thu, 7 Nov 2013 - 15:25:26 +0100

Updated:

Wed, 4 Jun 2014 - 09:03:04 +0200

Resolved:

Fri, 4 Apr 2014 - 10:25:52 +0200