Description Camille Letavernier 2020-11-13 03:53:23 EST

Currently, AbstractAdviceBindingConfiguration are specified at the root of the ElementTypeSet, and must reference the corresponding ElementType(s). In most case, custom Advices (Especially the ones related to Stereotypes, which is what we care about in the generated ElementTypes models) are related to a single ElementType, so having them in a flat structure is error-prone.

The ElementTypesConfigurations model should allow defining AbstractAdviceBindingConfiguration as children of ElementTypeConfiguration (In addition to the current reference mechanism: it doesn't replace it).

Some challenges about this:

- Compatibility with existing ElementTypesConfiguration models must be preserved
- When an AbstractAdviceBindingConfiguration is defined as a child of an ElementTypesConfiguration, some of its attributes will become irrelevant; especially the "target" reference (Which should always be the parent ElementType in this case), and the newly added "Apply to all types" attribute (Which should be false in this case). Ideally, these attributes would not exist at all for AbstractAdviceBindingConfiguration owned by their element type. It may be difficult to adjust the metamodels for this; so alternatively, we can either automatically set these values, or add a validation rule to detect/avoid/fix inconsistencies.
- The infra.types (meta)model is extended by UML-specific metamodels (especially uml.types.core); we need to make sure such extensions remain consistent with the updated metamodel