Petals ESB Container

It seems to be a proposition for the Petals-Exploitation project?
I think this is not the goal of the actual launcher in Petals ESB.
The actual launcher is basic and may stay like that until the relay of the Petals-Exploitation tools.

I think a part of this issue impacts the launcher, for launch Petals with a specific configuration file. It seems to me that it's not possible today.
An other part (directory tree) impacts Petals-Exploitation.

The last version of the launcher cannot be fully parametrized by an external configuration file.

There is still some work to do in the container to centralize the configuration, then I can modify the launcher to allow this kind of startup:
$ petals-esb -c myconfig.xml

I prefer a mechanism as Apache2: in the directory /etc/petals, we have the following directories:

• topologies-available: containing a directory per available topology. Such a directory contains all needed conf files and directories
• topologies-enabled: containing a directory per running topology. Such a directory contains all needed conf files and directories

So, you can have two scripts:

• petals-topology -c mytopology : to start all containers located on the current system, members of the topology 'mytopology'
• petals-esb -c mytopology [-i instance] : to start the local node of the topology, if only one local node. Or to start the node 'instance' of the topology 'mytopology' if several nodes are local.