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
