What happens when same alias gets used for different commands? I think even with the current mechanism for command name the problem exists i.e. two different commands can have the same name. And in that case how is it handled?
> -----Original Message----- > From: Kishan Kavala [mailto:kishan.kav...@citrix.com] > Sent: Monday, April 08, 2013 6:34 PM > To: dev@cloudstack.apache.org > Subject: [Discuss] API name alias > > APICommand annotation in API Cmd object has a name parameter. Currently > name parameter takes only one value. I plan to enhance this to support > comma separated values. This will allow multiple API names for the same API > Cmd object. > > Current: > @APICommand(name = "apiName1", .. > > Proposed: > @APICommand(name = "apiName1, apiAlias2, apiAlias3", .. > > Requirement: > As part of CLOUDSTACK-763, I'll be introducing NetworkACLList (grouping of > NetworkACLItems). Current APIs use *NetworkACL (create > NetworkACL/deleteNetworkACL etc..) for NetworkACLItem related APIs. > These APIs have to be changed to *NetworkACL Item(create > NetworkACLItem/deleteNetworkACLItem etc..) to get the terminology right. > We also need to support old API names for backward compatibility. Hence > the need for API name alias. > > Terminology: > NetworkACLItem - Individual ACL Entry (was NetworlACL earlier). > NetworkACL - Group of Network ACL Items. API will use the term > NetworkACLList to differentiate from the existing NetworkACL APIs. >
