Community
Participate
Working Groups
As discussed in the referenced mailing list thread, there is a need to be able to re-use a single table-configuration model for multiple different (but presumably similar) properties in the UML metamodel. For example, UML has distinct occurrences of an "ownedAttribute" property in several kinds of classifier that should all be treated in the same way by the Properties view. Or even "part" of StructuredClassifier could be presented in the same way as "ownedAttribute". This was initially supported by having the creation of the table-instance model by the NattablePropertyEditor reassign the "listenFeature" of the EStructuralFeatureValueFillingConfiguration, if any, in the header configuration. However, this has some issues: * the introduction of a transactional editing domain in the property-editor broke this (there is no read/write transaction in context and the table-configuration model is read-only). This is bug 493853 * this reassignment of the listen-feature was only ever done on the initial creation of the table-instance. If the same table-instance is re-used for a different property that uses the same property-editor, then it would not be reassigned to that other property Perhaps the suggestion on the mailing list of cloning the header axis configuration into a local configuration in the table-instance model will provide a means to address both of these issues.
