Community
Participate
Working Groups
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729) Build Identifier: When using the framework emfforms, you could implement an editor for an eobject which can have cross resource containement. In this case, validation will launch resolution of proxy, and resolution of proxy will launch a new validation. That will decrease the live validation performance (which is run too often). Futhermore, in the case of cross resource containement, perhaps the validation must not run across all the ressources. It would surely better to run it only on the edited object resource. Reproducible: Sometimes
There is a NotificationFilter in emf.transaction which tests if a notification is a read only notification. It could be used to avoid to launch too often the "live validation".
Created attachment 150220 [details] a patch for this bug I propose a patch which uses the NotificationFilter and which doesn't validate objects which are not in the edited objet resource.
Created attachment 150232 [details] a new patch if the validation is done in a transactional context, it must be execute in a runExclusive.
Fixed in HEAD>20091023 , thanks Simon!
