You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Harikrishna Patnala (JIRA)" <ji...@apache.org> on 2013/06/04 06:52:20 UTC
[jira] [Assigned] (CLOUDSTACK-2089) API dispatcher not able to
handle multiple entities while translating UUID to internaID
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harikrishna Patnala reassigned CLOUDSTACK-2089:
-----------------------------------------------
Assignee: Harikrishna Patnala
> API dispatcher not able to handle multiple entities while translating UUID to internaID
> ---------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2089
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2089
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: API
> Affects Versions: 4.2.0
> Reporter: Harikrishna Patnala
> Assignee: Harikrishna Patnala
> Fix For: 4.2.0
>
>
> Currently API dispatcher assumes single entity type for UUID defined on @EntityReference of a response class even if we can able to provide list of entity types (Class<?>[] entityType()).
> This needs to be supported in order to have some kind of generic APIs that has ID referring multiple entities (of course one entity in one go).
> For listing/updating configuration parameters (@Granular global parameters) we provide scope (zone/cluster/pool/account) and id. This id can be of any entity(zone/cluster/pool/account).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira