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

Bug 143478

Summary:	EMF annotation composing and validate helper
Product:	[Modeling] EMF	Reporter:	steeven <steeven>
Component:	Edit	Assignee:	Dave Steinberg <davidms>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	bhunt, Ed.Merks, kutter
Version:	2.2
Target Milestone:	---
Hardware:	All
OS:	All
URL:	http://www.blogjava.net/steeven/archive/2006/05/24/47883.html
Whiteboard:

Description steeven

2006-05-24 10:59:44 EDT

writing annotation in emf editor is hard. there is no constraints for annotation. the source is normally a long URL and the content key-value pairs is not complex too. for example, ExtendedMetaData has defined some extra-contraints supported by code generator, ecore author have to search javadoc to find source URL and supported metadata keys.

A wizard will make life easier by choosing KNOW Source URL from Combo box or choose unkown schema/ecore file from workspace/system, provide property sheet to input/choose desired value only, the author may preview result and validate inputs.

a proto type plugin has been worked out, and I was glad to contibute it to eclipse. for more details, please see:
http://www.eclipse.org/newsportal/article.php?id=17545&group=eclipse.tools.emf#17545
screen shots:
http://www.blogjava.net/steeven/archive/2006/05/24/47883.html

Comment 1 Philipp W. Kutter

2007-10-10 03:51:24 EDT

Ed suggested that the following is relevant to this bug:
> 2. Write an article which show how to use the Validation framework, to 
> add constraints to Ecore iself, guaranteeing that the OCL annotations in 
> the Christian Damus article are correct. For instance, a constraint that 
> checks that if a OCL "derive" is here, the corresponding ERererence 
> is derived=true, volatile=true, transient=true. Or a constraint that 
> checks that an OCL constraints is then as well mentioned in the 
> corresponding ECORE annotation "constraints"

Ed commented:
I think this is related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=143478.  I could imagine some type of mechanism whereby based on the source URI of an EAnnotation, a validator could be registered to validate EAnnotations with that source URI.

Comment 2 Ed Merks

2017-09-22 09:29:17 EDT

The changes committed for https://bugs.eclipse.org/bugs/show_bug.cgi?id=418619 provide extensive support for validating and authoring annotations.

*** This bug has been marked as a duplicate of bug 418619 ***