Community
Participate
Working Groups
In style customization, properties customizations by expression propose only the style EAttributes. It should be interesting to also have the style EReferences to directly call java services on it.
Do you have a concrete example of what such a Java service would do? I don't remember the details, but I believe the current restriction of only allowing attributes there was an explicit decision at the time. Maybe it is too restrictive, but depending on you use case there might be alternative solutions.
When customizing a style property defined by reference, we can only propose values which already exist in the VSM, hence the combo. In the implementation, EReferenceCustomizationElement.value is a non-containment reference which points to an already existing VSM element. There is no support for storing directly in the aird (inside the EReferenceCustomizationElement) style-related EObjects which would be created "out of the blue" by a service call. Sure, it might be possible to support something like this, but it would involve relatively complex issues (unintended side-effect of having VSM-level elements inside the aird; what lifecycle for these elements? performance implications of calling a service on each target element's refresh to re-create the same style elements 99% of the time, etc). Without some concrete scenario where the current situation is really problematic and can't be worked around, closing as WONTFIX.
