Hi Isuru, Regarding the services,
It should have relationship as follows, right? Topology 1: 0..n Services Group 1: 1..n Services On Mon, Sep 8, 2014 at 12:08 AM, Isuru Haththotuwa <isu...@apache.org> wrote: > > This is to discuss $subject. > > I have attached the class diagram which shows the proposed Topology > changes for Composite App support. Please note that this design is not > finalized yet, might need to tweak this a bit as we go on. > > > > > I have only shown the Composite App related Topology related changes here. > The basic idea is as follows: > > - Topology will contain Applications, identified by a unique > application id (specified in the Application Definition) > - The Application can contain any number of Groups (set of Services > and/or Groups) and/or Clusters. > - The Groups correspond to a particular Group Definition that has been > deployed before. > - Applications and Groups might have a Dependency Order; a set of > Startup Orders and a Kill Behavior which corresponds to the order that > services in the particular App/Group is started and how to handle > dependency termination. > > Can services take part in dependency order too? Thanks. > > - > > -- > Thanks and Regards, > > Isuru H. > +94 716 358 048* <http://wso2.com/>* > > > * <http://wso2.com/>* > > > > -- -- Lahiru Sandaruwan Committer and PMC member, Apache Stratos, Senior Software Engineer, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahi...@wso2.com cell: (+94) 773 325 954 blog: http://lahiruwrites.blogspot.com/ twitter: http://twitter.com/lahirus linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
