You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cloudstack.apache.org by "Joe San (JIRA)" <ji...@apache.org> on 2013/02/01 01:07:12 UTC

[jira] [Commented] (CLOUDSTACK-1080) Interface heirarchy for AccountManagerImpl superflous

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13568264#comment-13568264 ] 

Joe San commented on CLOUDSTACK-1080:
-------------------------------------

If you can let me know what refactoring you are expecting, then I could try to provide a fix for it. Could you please let me know?
                
> 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