Hi Shaheed,
I'm sorry I did not get what you mean. Do you think we need to avoid using
the "aliases" attribute and make the syntax as below?
{
"startupOrders":[
[
"cartridge.oracle1",
"cartridge.cassandra1",
"cartridge.tomcat1"
],
[
"cartridge.oracle1",
"cartridge.redis1"
]
],
"scalingDependents":[
[
"cartridge.redis1",
"cartridge.tomcat1"
]
]
}
On Tue, May 12, 2015 at 4:03 AM, Shaheedur Haque (shahhaqu) <
shahh...@cisco.com> wrote:
> I’m confused by the new syntax. Originally, startup orders were pairs of
> comma separated strings, “A, B” implying an order between A and B, and that
> the change was simply to make it [“A”, “B”]. What does it mean when you
> have [“A”, “B”, “C”]:
>
>
>
> 1. Is the order A then B then C?
>
> 2. Is the meaning EXACTLY the same as specifying [“A”, “B”] and also
> [“B”, “C”]?
>
>
>
>
>
> *From:* Imesh Gunaratne [mailto:im...@apache.org]
> *Sent:* 10 May 2015 10:37
> *To:* dev
> *Cc:* Shaheedur Haque (shahhaqu); Reka Thirunavukkarasu; Dakshika
> Jayathilaka
> *Subject:* Re: [Discuss] Fixing Comma Separated Dependency JSON
> Definitions
>
>
>
> I have now updated the Cartridge Group & Application creation pages in the
> UI with this modification:
>
>
>
>
>
>
>
> Thanks
>
>
>
> On Sun, May 10, 2015 at 2:15 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
> I have now updated the API and the samples accordingly. The changes were
> pushed to master branch with the following commit revision:
>
> 112680a12ec5dc0a53d8253eb7818bf0e76adf07
>
>
>
> We need to update the UI with this modification.
>
>
>
> Thanks
>
>
>
> On Sun, May 10, 2015 at 1:47 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
> It looks like I have made a mistake in the above sample when defining
> aliases. Aliases should either start with "cartridge." or "group.":
>
>
>
> {
>
> "startupOrders":[
>
> {
>
> "aliases":[
>
> "cartridge.oracle1",
>
> "cartridge.cassandra1",
>
> "cartridge.tomcat1"
>
> ]
>
> },
>
> {
>
> "aliases":[
>
> "cartridge.oracle1",
>
> "cartridge.redis1"
>
> ]
>
> }
>
> ],
>
> "scalingDependents":[
>
> {
>
> "aliases":[
>
> "cartridge.redis1",
>
> "cartridge.tomcat1"
>
> ]
>
> }
>
> ]
>
> }
>
>
>
> On Sun, May 10, 2015 at 12:42 PM, Imesh Gunaratne <im...@apache.org>
> wrote:
>
> A good point Chamila! IMO order of elements in array is by default
> preserved by CXF. We might need to verify it.
>
>
>
> Thanks
>
>
>
> On Sun, May 10, 2015 at 12:12 PM, Chamila De Alwis <chami...@wso2.com>
> wrote:
>
> Hi Imesh,
>
> Is the order among the array preserved during serialization and de
> serialization in JSON? Is it explicitly declared in the bean via
> JsonPropertyOrder annotation?
>
> On May 10, 2015 11:57 AM, "Imesh Gunaratne" <im...@apache.org> wrote:
>
> Hi Devs,
>
>
>
> According to a suggestion made by Shaheed I have now updated the
> dependency JSON definitions (startup orders and scaling dependents) as
> follows:
>
>
>
> {
>
> "startupOrders":[
>
> {
>
> "aliases":[
>
> "oracle.oracle1",
>
> "cassandra.cassandra1",
>
> "tomcat.tomcat1"
>
> ]
>
> },
>
> {
>
> "aliases":[
>
> "oracle.oracle1",
>
> "redis.redis1"
>
> ]
>
> }
>
> ],
>
> "scalingDependents":[
>
> {
>
> "aliases":[
>
> "redis.redis1",
>
> "tomcat.tomcat1"
>
> ]
>
> }
>
> ]
>
> }
>
>
>
> Please feel free to share your thoughts on this.
>
>
>
> Thanks
>
>
>
> --
>
> Imesh Gunaratne
>
>
>
> Senior Technical Lead, WSO2
>
> Committer & PMC Member, Apache Stratos
>
>
>
>
>
> --
>
> Imesh Gunaratne
>
>
>
> Senior Technical Lead, WSO2
>
> Committer & PMC Member, Apache Stratos
>
>
>
>
>
> --
>
> Imesh Gunaratne
>
>
>
> Senior Technical Lead, WSO2
>
> Committer & PMC Member, Apache Stratos
>
>
>
>
>
> --
>
> Imesh Gunaratne
>
>
>
> Senior Technical Lead, WSO2
>
> Committer & PMC Member, Apache Stratos
>
>
>
>
>
> --
>
> Imesh Gunaratne
>
>
>
> Senior Technical Lead, WSO2
>
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Senior Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
