You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Tom Beerbower (JIRA)" <ji...@apache.org> on 2013/02/12 20:17:12 UTC

[jira] [Created] (AMBARI-1412) Get rid of AmbariManagementController

Tom Beerbower created AMBARI-1412:
-------------------------------------

             Summary: Get rid of AmbariManagementController 
                 Key: AMBARI-1412
                 URL: https://issues.apache.org/jira/browse/AMBARI-1412
             Project: Ambari
          Issue Type: Sub-task
            Reporter: Tom Beerbower
            Assignee: Tom Beerbower
             Fix For: 1.3.0


In this phase the goal is to get rid of the AmbariManagementController interface and pull most of the management controller logic into the resource provider implementations.  The easiest way to approach this might be to change the signature of getManagementController() in AbstractResourceProvider to return AmbariManagementControllerImpl instead of AmbariManagementController.  This will allow us to use the IDE refactoring tools to inline the calls to the AmbariManagementController methods in each of the resource providers that extends AbstractResourceProvider.  For this phase, some of the code in the AmbariManagementControllerImpl may have to stick around in some form.  This phase could be done as one big commit or as a single transaction per resource type.

--
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