[
https://issues.apache.org/jira/browse/CLOUDSTACK-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566250#comment-13566250
]
Joe San commented on CLOUDSTACK-1080:
-------------------------------------
I did manage to submit the patch. But I did not use the last but one commit ID
to create the patch, but rather I gave the patch a name that resembles the bug
id. Let me know if this is fine?
> Interface heirarchy for AccountManagerImpl superflous
> -----------------------------------------------------
>
> Key: CLOUDSTACK-1080
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1080
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
> Reporter: Joe San
> Assignee: Rohit Yadav
> Priority: Trivial
> Labels: Refactoring
>
> The AccountManagerImpl.java has two interfaces in its implements clause which
> is a bit redundant. These two interfaces are already in the same heirarchy
> (AccountManager and AccountService). Can we refactor the AccountManagerImpl
> to implement only the AccountManager?
--
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