Re: [Discuss] Most of the identity fields are named as "id" but application identity field is named as "applicationId"

2014-12-18 Thread Imesh Gunaratne
I thought the other way around: application.id Since the entity name is already there, we might not need to repeat it in the property name. Thanks On Thu, Dec 18, 2014 at 3:20 PM, Manula Chathurika Thantriwatte < manu...@wso2.com> wrote: > > Hi, > > +1, I think "application.applicationId" convent

Re: [Discuss] Most of the identity fields are named as "id" but application identity field is named as "applicationId"

2014-12-18 Thread Manula Chathurika Thantriwatte
Hi, +1, I think "application.applicationId" convention is more readable. Thanks ! On Thu, Dec 18, 2014 at 3:12 PM, Imesh Gunaratne wrote: > > Hi Devs, > > As I noticed we have named most of the identity fields in the domain > classes in the REST API as "id": > applicationLevelNetworkPartition.i

[Discuss] Most of the identity fields are named as "id" but application identity field is named as "applicationId"

2014-12-18 Thread Imesh Gunaratne
Hi Devs, As I noticed we have named most of the identity fields in the domain classes in the REST API as "id": applicationLevelNetworkPartition.id childLevelNetworkPartition.id childLevelPartition.id partition.id autoscalingPolicy.id However application identity field is named as "applicationId":