[jboss-jira] [JBoss JIRA] (WFLY-11803) Capabilities registered when the model is being populated are not recorded in the Galleon feature-spec
[
https://issues.jboss.org/browse/WFLY-11803?page=com.atlassian.jira.plugin...
]
Yeray Borges updated WFLY-11803:
--------------------------------
Issue Type: Task (was: Bug)
I agree to do not considerate it as a bug, so converted to task instead.
My thoughts about if some capabilities dependent on an attribute value should /
shouldn't be recorded in the feature pack was a bit different. You mentioned, there is
no 'correct' value, but the attribute value configured by the user or by a default
assignment, from my point of view is always a correct one (or at least it is an intention
to be correct) for the current provisioning and hence, Galleon must ensure that the
provisioning using that value is correct too, that means, that all capability requirements
derived from the uses of that value should be present. My mistake here was to assume we
should go beyond what is defined in the metamodel.
At least reviewing these methods, we were able to find out the missing ones for EJB3.
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: Task
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)