Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 344034 - Provide a means to set the validation level during migration
Summary: Provide a means to set the validation level during migration
Status: RESOLVED FIXED
Alias: None
Product: Edapt
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal
Target Milestone: ---   Edit
Assignee: Markus Herrmannsdoerfer CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-27 15:33 EDT by Markus Herrmannsdoerfer CLA
Modified: 2011-04-27 15:38 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Herrmannsdoerfer CLA 2011-04-27 15:33:51 EDT 
Currently, the validation, that the model conforms to the metamodel, is performed after each change. This has the advantage that migration errors can be better located. But it has the disadvantage that a lot of performance is required to perform validation. In order to support both cases, the validation level needs to be customizable.
Comment 1 Markus Herrmannsdoerfer CLA 2011-04-27 15:38:46 EDT 
The validation level can now be set in the migrator. Validation can be performed after each change, after custom migrations, after each release, before and after the complete migration or not at all.