|Model change doesn't yield notification [message #637726]
||Mon, 08 November 2010 15:06
Registered: September 2010
I implement a BPEL validator that validates a process ad hoc (and not just on document save). Rule SA00025 states that exactly one attribute of messageType, type or element must be defined on the variable element.
To check the rules at runtime I use a org.eclipse.emf.common.notify.Notification object that informs about changes on the BPEL model.
The validation of the rule works fine except in one situation.
Say we defined two attributes, messageType and type. Obviously, SA00025 is violated. If I now delete the messageType attribute, the rule is satisfied. So far, so good. But now there will be no longer any notifications about model changes on the variable element. So neither changes on the value of type, nor the deletion of the attribute will be recognized by the validator. So, if type is deleted, SA00025 still seems to be satisfied, while it is not (since NONE of the mentioned attributes is defined).
The same use case holds for the combination messageType and element; and type and element, respectively.
Notifications will only be sent as long as messageType is present in the variable element.
This appears to me very likely as a bug, but where does it live?
Powered by FUDForum
. Page generated in 0.04527 seconds