Community
Participate
Working Groups
When live validation validates notifications, the event type of the notification is compared against a list of predefined types in EMFTEventTypes. If the event type is not in EMFTEventTypes, the notification is not validated. There are cases where clients wish to define their own event types for their own custom notifications. An example might be "Add to container" and "Delete from container" events. The client can derive these custom notifications from the raw EMF-defined notifications, and in doing so would make it easier to target containment changes without having to specify all possible containers (which could be many).
Created attachment 61436 [details] Proposed patch
Committed the patch, with a change to the proposed constraintProviders schema. Reinstated the enumeration of core <event> element names and added a new <customEvent> element, similarly structured, whose name is required by not enumerated. This clearly indicates the dependency on custom (non-EMF-defined) notifications types.
Move to verified as per bug 206558.