![]() |
|
|
|
|
Change By:
|
Eric Hechinger
(11/Dec/13 4:57 PM)
|
|
Description:
|
Currently, the control migrators registered in a dialog migration task are inherited by class hierarchy.
For example, DialogMigrationTask define a bunch of migrators, and his sub class DamDialogmigrationTask add migrators.
A custom module may want to uses the migrators defined in Dam, but also the Category and Data one. This is currently not possible but necessary.
The solution is to use a registry of migrators defined at the module level, and to define a new DialogMigration task that uses those registry to build the available migrators list.
Task:
-
Define
Create
a new
Interface used to register dialogs (ControlMigrators)
ControlMigratorsRegistry.
-
- Singleton filled by the modules version handlers that defines custom controls and migrators
-
Define a new DialogMigratortask that uses
these
this
registry (DialogMigrationRegisteryTask)
-
Implement
Adapt the
module
version handlers that defines
specific ControlMigrators
-
Configure these registry on
Adapt
the
module descriptors xml files.
existing DialogMigrationTask in order to be backward compatible
|
|
|
|
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
|
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <
[email protected]>
----------------------------------------------------------------
