Petals ESB Container

Replace and externalize the existing registry

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 3.1.1
  • Fix Version/s: 5.0.0
  • Component/s: Registry
  • Security Level: Public
  • Description:

    The existing registry should be replaced by a peer-to-peer registry including:

    • data persistency,
    • only changes propagation,
    • WAN support

    Moreover, the registry should be externalized to be able to change easily its implementation

  • Environment:
    -

Issue Links

Duplicate
 

Activity

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Tue, 15 Feb 2011 - 09:38:54 +0100
Field Original Value New Value
Link This issue blocks SPLOGIDGME-8 [ SPLOGIDGME-8 ]
Hide
Permalink
Christophe Hamerling added a comment - Tue, 15 Feb 2011 - 10:00:35 +0100

Can you give details about "Moreover, the registry should be externalized to be able to change easily its implementation" ? Do you mean that the registry have to be an external runtime?

Show
Christophe Hamerling added a comment - Tue, 15 Feb 2011 - 10:00:35 +0100 Can you give details about "Moreover, the registry should be externalized to be able to change easily its implementation" ? Do you mean that the registry have to be an external runtime?
Hide
Permalink
Christophe DENEUX added a comment - Tue, 15 Feb 2011 - 10:22:02 +0100

To prepare the microkernel, the fractal component 'Registry' of the kernel will move to outside the source code of the kernel. And the implementation of the fractal component 'Registry' is customizable in the Petals ESB conf files.

Show
Christophe DENEUX added a comment - Tue, 15 Feb 2011 - 10:22:02 +0100 To prepare the microkernel, the fractal component 'Registry' of the kernel will move to outside the source code of the kernel. And the implementation of the fractal component 'Registry' is customizable in the Petals ESB conf files.
Christophe DENEUX made changes - Mon, 5 Oct 2015 - 11:31:32 +0200
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Assignee Admin [ rnaudin ] Christophe DENEUX [ cdeneux ]
Christophe DENEUX made changes - Mon, 5 Oct 2015 - 11:31:39 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
Christophe DENEUX added a comment - Mon, 5 Oct 2015 - 11:33:06 +0200

No data persistence is needed, because the system state (including endpoint) is already persisted by the internel component names "SystemState"

Show
Christophe DENEUX added a comment - Mon, 5 Oct 2015 - 11:33:06 +0200 No data persistence is needed, because the system state (including endpoint) is already persisted by the internel component names "SystemState"
Christophe DENEUX made changes - Mon, 5 Oct 2015 - 11:33:06 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 5.0.0 [ 10413 ]
Resolution Duplicate [ 3 ]
Christophe DENEUX made changes - Mon, 5 Oct 2015 - 11:33:37 +0200
Link This issue duplicates PETALSESBCONT-275 [ PETALSESBCONT-275 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
1693d 53m
1
Christophe DENEUX
Mon, 5 Oct 2015 - 11:31:32 +0200
Open Open In Progress In Progress
7s
1
Christophe DENEUX
Mon, 5 Oct 2015 - 11:31:39 +0200
In Progress In Progress Resolved Resolved
1m 27s
1
Christophe DENEUX
Mon, 5 Oct 2015 - 11:33:06 +0200



People

Dates

  • Created:
    Tue, 15 Feb 2011 - 09:38:16 +0100
    Updated:
    Mon, 5 Oct 2015 - 11:33:37 +0200
    Resolved:
    Mon, 5 Oct 2015 - 11:33:06 +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.