[jboss-jira] [JBoss JIRA] (WFCORE-155) Evaluate robustness of decisions about target versions for transformation

[ehsavoie Hugonnet (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103305#comment-13103305 ] 

ehsavoie Hugonnet commented on WFCORE-155:
------------------------------------------

Currently we have a lot of registries (*GlobalTransformerRegistry*) which will be organized as a tree of registries the address(of the resource or of the operation) will lead to the *TransformationDescription*(s) to be applied. The 'entry' point is the *TransformerRegistry* which contains the subsystems registry and the domain registry.
When a HC connects to the DC it sends a list of all the subsystems it uses and their versions. 
For each subsystem/version we will get a registry that will contains all the transformations from the current version of the DC to the HC version.
A slight difference exists when we reach a *ChainedTransformingDescription* because it then takes place of the registry to resolve the subparts.
So if the DC is running on 2.0.0 and the HC is on 1.1.0 when the HC registers : a *TransformationTarget* is created with only a 'filtered' registry containing the a registry with the transformation description for each subsystem according to its version.
So if we have a subsystem with an unregistered version we need to manage it in this processing aka 
*GlobalTransformerRegistry.process(final OperationTransformerRegistry registry, final PathAddress address, final ModelVersion version, Map<PathAddress, ModelVersion> versions)* (around line 170) then we need to check that the unregistered version is not used anymore.




> Evaluate robustness of decisions about target versions for transformation
> -------------------------------------------------------------------------
>
>                 Key: WFCORE-155
>                 URL: https://issues.jboss.org/browse/WFCORE-155
>             Project: WildFly Core
>          Issue Type: Task
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: ehsavoie Hugonnet
>             Fix For: 2.0.0.CR1
>
>
> Apologies; this is a bit vague, just a general thing I want us to look into.
> Task is to evaluate how we choose whether transformation needs to occur for a given management API version from a slave, with a view toward checking that intelligent choices are made in the absence of proper transformation definitions.
> The main kind of thing I'm thinking about is the DC is on 2.0.0 and has a transformer to 1.1.0 registered, and then a slave registers that is using 1.1.1. The subsystem author likely forgot to create the transformation to 1.1.1. Odds are good though that transforming to 1.1.0 is a better choice than not transforming and treating the slave as if it were on 2.0.0.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)