;
> Thanks
>
>
>
> Martin
>
>
>
>
>
>
>
> *From:* Reka Thirunavukkarasu [mailto:r...@wso2.com]
> *Sent:* Wednesday, October 15, 2014 2:04 AM
>
> *To:* Martin Eppel (meppel)
> *Cc:* dev@stratos.apache.org; Isuru Haththotuwa; Udara Liyanage
> *Subject:*
r
> Preview - 2 is Ready".
>
>
>
> Please share us, if you think in any other way that we can improve this
> application definition. In the mean time, we will also go through and
> update on how we can improve this.
>
>
>
> Thanks,
>
> Reka
>
>
>
>
iously (I attached the json) or some other suitable model
describe which cartridge, group gets started up when (pretty much explain how
the dependencies are resolved and what states a cartridge or groups has to be) ?
I think it would be really helpful to understand the model.
I f this is not possible c
e model
> describe which cartridge, group gets started up when (pretty much explain
> how the dependencies are resolved and what states a cartridge or groups has
> to be) ?
>
>
>
> I think it would be really helpful to understand the model.
>
>
>
> I f this is not pos
Thirunavukkarasu
Cc: dev@stratos.apache.org; Isuru Haththotuwa; Udara Liyanage
Subject: RE: [Grouping][testing] How to model nested dependencies ?
Reka,
I think the issue is I don’t understand what goes into the “component” and
dependencies section of the application definition.
My current understanding is
[mailto:r...@wso2.com]
Sent: Monday, October 13, 2014 10:56 PM
To: Martin Eppel (meppel)
Cc: dev@stratos.apache.org; Isuru Haththotuwa; Udara Liyanage
Subject: Re: [Grouping][testing] How to model nested dependencies ?
Hi Martin,
As i mentioned in the other mail, you can define startup order for
Hi Martin,
As i mentioned in the other mail, you can define startup order for top
level groups/cartridges in the application and you can define startup order
in the group definition for group's subgroups/cartridges. In your case, i'm
not sure why are you trying with nested group definition.
Group
