Hi Reka, Great news!!
I tried with a similar Application, however there were no instance spawned for the top level Cartridge. But, both the Groups were successfully activated. Might be an issue with the definitions I used, have attached there here. Will check on this more. On Sun, Oct 12, 2014 at 11:09 AM, Reka Thirunavukkarasu <[email protected]> wrote: > Hi all, > > I have tested the hierarchical monitors with the attached sample > application which has group2 and tomcat cartridge as in top level. group2 > further refers to tomcat and group1. group1 further refers to php. Their > startup order has also defined in the definitions as below mentioned: > > For Eg: > > app (group2, tomcat) implies that group2 should be started before tomcat. > > The application structure is like: > --------------- app (group2, > tomcat)---------------- > | > | > --------group2 (group1, tomcat)------- > tomcat > | | > tomcat group1 > | > php > > > For the above composite application structure, Application successfully > became active after its children activated according to the start up order > definied. > > Please find the samples as attached. If you encounter any issue while > testing, can you update the thread? > > > Thanks, > Reka > > > > -- > Reka Thirunavukkarasu > Senior Software Engineer, > WSO2, Inc.:http://wso2.com, > Mobile: +94776442007 > > -- > Thanks and Regards, > > Isuru H. > +94 716 358 048* <http://wso2.com/>* > > > * <http://wso2.com/>* > > >
app5.json
Description: application/json
group1.json
Description: application/json
group2.json
Description: application/json
