![]() |
|
|
|
|
Issue Type:
|
![Task]() Task
|
|
Affects Versions:
|
5.2 |
|
Assignee:
|
Eric Hechinger
|
|
Components:
|
dialogs, framework |
|
Created:
|
09/Dec/13 9:32 AM
|
|
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 a new Interface used to register dialogs (ControlMigrators)
- Define a new DialogMigratortask that uses these registry (DialogMigrationRegisteryTask)
- Implement module specific ControlMigrators
- Configure these registry on the module descriptors xml files.
|
|
Fix Versions:
|
5.2.1 |
|
Project:
|
Magnolia UI
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Eric Hechinger
|
|
Security Level:
|
Public |
|
|
|
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: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------
