|Checking a single element using EVL [message #882969]
||Thu, 07 June 2012 14:49
| Maarten Bezemer
Registered: February 2012
I have a user who designed a big (>1MB and around 5000 elements/eObjects) model. Unfortunately, since I enabled EVL validation for my application, opening and editing this model is not doable anymore: it takes too much time.
Batch validation (opening) is fixed now (I made some errors triggering validation over and over). Live validation on the other hand is taking too long, after each modification to the model the user has to wait...
I know I can reduce the amount of model modifications (or notifications) using EMF Transactions. This is high on my todo list, but a lot of work (converting my application), so I am also looking at other possibilities.
One is to only validate the elements that are changed.
I already modified EvlValidator to cache the list of results (as the validation checks the complete model, so I am not doing this for each element) and invalidate the results for an object when it is modified (using adapters). This caching scheme seems to work properly.
Only problem is when I change an object (and its results are invalidated), it is going to be revalidated. EvlValidator is only capable of validating the complete model/resource, even though I have most of the results already available... Resulting in extensive validation for a single modification.
Now I was wondering whether someone has be working to modify the EVL validation to only validate a single element.
As this seems to be a lot of work (and hacking into the internals of EVL), I rather not re-invent the wheel...
PS If anyone has other ideas to speed up (live-)validation with EVL: I am open for ideas!
[Updated on: Thu, 07 June 2012 14:49]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.05084 seconds