Rohit Yadav created CLOUDSTACK-798:
--------------------------------------
Summary: Move usage related cmd classes from cloud-server to
cloud-api
Key: CLOUDSTACK-798
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-798
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: API, Usage
Reporter: Rohit Yadav
Fix For: 4.1.0
Usage related apis exist in cloud-server, the cmd classes should be in
cloud-api:
server/src/com/cloud/api/commands/AddTrafficMonitorCmd.java
server/src/com/cloud/api/commands/DeleteTrafficMonitorCmd.java
server/src/com/cloud/api/commands/GenerateUsageRecordsCmd.java
server/src/com/cloud/api/commands/GetUsageRecordsCmd.java
server/src/com/cloud/api/commands/ListTrafficMonitorsCmd.java
server/src/com/cloud/api/commands/ListUsageTypesCmd.java
The issue is that they are tightly coupled with cloud-server and instead of
using interface to handle object method evoking, they are used directly on
implementing class objects. This makes move refactoring impossible. For example
UsageVO implements no contract or interface which should be defined in
cloud-api.
--
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
