Page Comparison

...

You can override mda.MigrationClassMap and mda.MigrationBeanMap in the same way, or define another instance of mda.RelocatedBeanFactoryPostProcessor if you need similar assistance in migrating classes and beans of your own.Important note: the Spring Framework technology on which this feature is built is limited in that it can only process bean names and class names in beans defined at the outer level of the configuration. Beans defined within other beans (“inner beans”) are not visible to it and migration assistance will not be available for them.

Migration assistance and Spring contexts

The mda.MigrationAssistanceBean will only be instantiated in the Spring context in which the standard bean definition resource is imported. This instance of the bean will be able to process other beans instantiated within that context. It will not process uninstantiated bean definitions (e.g., lazy-initialised beans which are not used, abstract beans).

If your application uses child contexts, note that in general bean definitions are inherited from parent contexts, but those bean definitions are not instantiated. This means that the MigrationAssistanceBean from the parent context will not be able to process beans instantiated in the child context.

If you need migration assistance in a child context, instantiate the bean again in the child context like this:

<bean id="child.MigrationAssistanceBean" lazy-init=false
    parent="mda.MigrationAssistanceBean"/>