Since the creation of the Petals Registry Overlay, it is required to start it as another system process before to start Petals ESB nodes.
It's not really user friendly for a standalone topology, or for the default/sample configuration.
The solution: the Petals Registry Overlay is embedded as a Petals ESB extension, and loaded by the Petals ESB container:
if the topology is a standalone topology
no configuration about the registry is set
So it is not needed to start the Petals Registry Overlay as another system process
Since the creation of the Petals Registry Overlay, it is required to start it as another system process before to start Petals ESB nodes.
It's not really user friendly for a standalone topology, or for the default/sample configuration.
The solution: the Petals Registry Overlay is embedded as a Petals ESB extension, and loaded by the Petals ESB container:
if the topology is a standalone topology
no configuration about the registry is set
So it is not needed to start the Petals Registry Overlay as another system process
Christophe DENEUX added a comment - Thu, 23 Jan 2014 - 11:06:58 +0100 The Petals ESB pre-extension 'Embedded Petals Registry Overlay' has been added to the trunk
A server property has been added to configure the listening port by svn#36056