Changes between Version 4 and Version 5 of DependencyInjection

Timestamp:

07/07/12 22:22:25 (12 years ago)

Author:

jesseeichar

Comment:

--

DependencyInjection

@@ -137 +137 @@
 The 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
 As 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. 
-An additional (and more powerful) method is to register a BeanPostProcessor which will have access to all beans and can modify them via JavaBean setters.
+An additional (and more powerful) method is to register a !BeanPostProcessor which will have access to all beans and can modify them via !JavaBean setters.
 
 == Risks ==