[jboss-jira] [JBoss JIRA] (WFLY-2512) Transformers chained for versions

Brian Stansberry (JIRA) issues at jboss.org
Fri Feb 7 21:36:29 EST 2014


     [ https://issues.jboss.org/browse/WFLY-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated WFLY-2512:
-----------------------------------

    Fix Version/s: 9.0.0.CR1
                       (was: 8.0.0.Final)

    
> Transformers chained for versions
> ---------------------------------
>
>                 Key: WFLY-2512
>                 URL: https://issues.jboss.org/browse/WFLY-2512
>             Project: WildFly
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>            Reporter: Kabir Khan
>            Assignee: Kabir Khan
>             Fix For: 9.0.0.CR1
>
>
> Say you have a subsystem with model versions 1.0, 1.1 and currently 2.0.
> At present we register a transformer doing everything that needs doing from 2.0 to 1.1, and another one duplicating all that with everything that needs doing from 1.1 to 1.0. As more model versions are added, more transformers 'doing everything' are needed.
> Richard and Tomaz have both come up with the same idea, to avoid this code duplication by only having transformers for each model version increment, and to chain them together, so you would have
> * a transformer for 2.0 to 1.1
> * a transformer for 1.1 to 1.0
> Then if someone wanted to transform from 2.0 to 1.0 we would take the current model/operation and feed that into the 2.0-to-1.1 transformer, giving us the 1.1 model/operation. The 1.1 model/operation would then be fed into the 1.1-to-1.0 transformer giving us the 1.0 model/operation.

--
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


More information about the jboss-jira mailing list