Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 344034

Summary:	Provide a means to set the validation level during migration
Product:	[Modeling] Edapt	Reporter:	Markus Herrmannsdoerfer <herrmama>
Component:	Core	Assignee:	Markus Herrmannsdoerfer <herrmama>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Markus Herrmannsdoerfer

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

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.