incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe San (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (CLOUDSTACK-1080) Interface heirarchy for AccountManagerImpl superflous
Date Thu, 31 Jan 2013 06:51:12 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Joe San reopened CLOUDSTACK-1080:
---------------------------------


I guess I accidentally removed the AccountManager in the implements clause and submitted the
patch. But theoretically speaking, only the AccountManager is enough in the implements clause
as an AccountManager IS-A AccountService, hence AccountManagerImpl IS-A AccountManager and
IS-A AccountService.

I will submit the patch today for review.
                
> 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

Mime
View raw message