[jboss-jira] [JBoss JIRA] (WFLY-11803) Capabilities registered when the model is being populated are not recorded in the Galleon feature-spec

[Brian Stansberry (Jira)]

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

Brian Stansberry commented on WFLY-11803:
-----------------------------------------

This is not a bug. Feature specs are part of the feature pack and there is no effective model in a feature pack. A feature pack include features, feature-groups and layers, all of which are possible elements in an effective model, but there's no way to know which the user will use in their config. And it's certainly possible that different features, feature-groups and layers in a feature pack will use different config values, so even trying to use those somehow, there is no 'correct' value for the feature pack.

> Capabilities registered when the model is being populated are not recorded in the Galleon feature-spec
> ------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-11803
>                 URL: https://issues.jboss.org/browse/WFLY-11803
>             Project: WildFly
>          Issue Type: Bug
>            Reporter: Yeray Borges
>            Assignee: Yeray Borges
>            Priority: Major
>
> Specifically, capabilities registered in recordCapabilitiesAndRequirements are not recorded in the Galleon feature-specs.
> The reason is Galleon generates the feature specs using the metamodel instead of the effective model. The metamodel is the resource definitions and the effective model is the current configuration created once the model is populated with all the attribute values.
> recordCapabilitiesAndRequirements is executed when the model is populated, then, capabilities defined there are not exposed in the Galleon feature-specs.
> The goal here is to identify which capabilities are affected and rework them, for example moving them to the resource definition itself, to allow Galleon to record them in the feature-specs.
> Some capabilities could require a different work if they cannot be moved out from recordCapabilitiesAndRequirements.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)