Can you give us a little more detail on what you mean by child instances?
Is it possibly lightweight containers you are talking about, http://servicemix.apache.org/what-is-a-lightweight-component.html ?
Or are you looking for some specific architectural pattern?
I guess I have a misunderstanding here. What I meant by child instance was a ServiceMix instance created by ServiceMix kernel (admin create instance02).
I would like to know what's the difference between such instance and the default ServiceMix instance on startup. I see lots of bundles missing in my instance02.
ServiceMix Noob ?:|
To quote from the SMX Kernel user guide:
"ServiceMix Kernel provides some commands to administer instances of ServiceMix Kernel. An instance of ServiceMix Kernel is a copy of the Kernel that you can launch separately and deploy applications onto it. An instance does not contain a full copy of ServiceMix Kernel, but only a copy of the configuration files and data folder which contains all runtime informations, logs and temporary files."
I find these instances are useful for testing out and developing new applications using the host's default configuration as a starting point. From my own experience I've used instances for deploying small software failover clusters (master/slave instances on one host), see the Kernel user guide for more information on failover configuration: http://servicemix.apache.org/SMX4KNL/67-configuring-failover-deployments-available-in-110.html