Changes between Version 2 and Version 3 of DependencyInjection


Ignore:
Timestamp:
07/07/12 13:04:22 (12 years ago)
Author:
jesseeichar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DependencyInjection

    v2 v3  
    135135=== Backwards Compatibility Issues ===
    136136
    137 A new dependency and new servlet and filter definitions in web.xml.  Monitor Manager is added to ServiceContext, ResourceManager and ServiceManager.
     137The main backwards compatibility issue will be the configuration.  Services, harvesters, scheduled tasks should continue to work as they do now.  On startup the system will check the configuration files and attempt to migrate them to the new version.  A copy of the original configuration files will be made so the administrator can revert the change or compare the old and new configurations
     138As big or even bigger compatibility issue will be configuration overrides.  They will be useable only for a small subset of cases.  For example, to override SQL values and at the moment config-gui.xml is left alone so it will apply to that.  The new way to override configuration will be to create a new spring configuration file and create a new bean of the same id as the bean you want to override.
     139An additional (and more powerful) method is to register a BeanPostProcessor which will have access to all beans and can modify them via JavaBean setters.
    138140
    139141== Risks ==
    140142
    141 Nothing notable
     143 * Potential for a component to not be wired correctly (because the entire system is quite large) or a cyclic dependency could cause issues.
     144 * Configuration overrides would not work at all and there is not migration for that. 
    142145
    143146== Participants ==