Petals ESB Container

Externalize the registry implementation

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
  • 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:

    1. the registry implementation configured in the topology definition (as the registry is distributed, it must be the same on each Petals ESB node)
    2. 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:
    1. the registry implementation configured in the topology definition (as the registry is distributed, it must be the same on each Petals ESB node)
    2. 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

Activity

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Thu, 7 Nov 2013 - 15:30:38 +0100
Field Original Value New Value
Link This issue depends on PETALSESBCONT-268 [ PETALSESBCONT-268 ]
Christophe DENEUX made changes - Thu, 7 Nov 2013 - 18:08:18 +0100
Link This issue depends on PETALSESBCONT-269 [ PETALSESBCONT-269 ]
Christophe DENEUX made changes - Wed, 13 Nov 2013 - 11:52:56 +0100
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Christophe DENEUX made changes - Wed, 13 Nov 2013 - 11:52:59 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Wed, 13 Nov 2013 - 15:49:42 +0100
Link This issue depends on PETALSESBCONT-271 [ PETALSESBCONT-271 ]
Christophe DENEUX made changes - Wed, 13 Nov 2013 - 15:50:46 +0100
Link This issue depends on PETALSESBCONT-272 [ PETALSESBCONT-272 ]
Christophe DENEUX made changes - Fri, 13 Dec 2013 - 12:07:20 +0100
Link This issue depends on PETALSESBCONT-273 [ PETALSESBCONT-273 ]
Christophe DENEUX made changes - Fri, 13 Dec 2013 - 12:21:19 +0100
Link This issue blocks PETALSESBCONT-275 [ PETALSESBCONT-275 ]
Christophe DENEUX made changes - Fri, 13 Dec 2013 - 12:24:40 +0100
Link This issue depends on PETALSESBCONT-274 [ PETALSESBCONT-274 ]
Christophe DENEUX made changes - Mon, 16 Dec 2013 - 16:29:29 +0100
Link This issue blocks PETALSESBCONT-276 [ PETALSESBCONT-276 ]
Christophe DENEUX made changes - Mon, 6 Jan 2014 - 14:56:48 +0100
Fix Version/s 4.2.1 [ 10413 ]
Christophe DENEUX made changes - Fri, 4 Apr 2014 - 10:25:52 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Wed, 4 Jun 2014 - 09:03:04 +0200
Link This issue depends on PETALSESBCONT-304 [ PETALSESBCONT-304 ]

People

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
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.