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

Bug 123315

Summary:	Error not reported during import from annotated Java
Product:	[Modeling] EMF	Reporter:	David Holz <david_holz>
Component:	Core	Assignee:	Marcelo Paternostro <marcelop>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3
Version:	2.1
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description David Holz

2006-01-10 16:03:34 EST

Given this method declaration:

/**
 * model opposite="something"
 */
MyClass getSomething();

if MyClass is not flagged with @model, then no error is reported for the misuse of "opposite", and the Select Packages dialog during the EMF model creation wizard will be empty, no matter how many properly formed models reside in the rest of the project.

Note that a nice descriptive error is properly produced when the "opposite" parameter does not exist in a modelled MyClass.

Comment 1 Ed Merks

2006-01-17 15:22:10 EST

There's a very long list of things we don't properly report.  :-(

I'll return this as a duplicate of the more general defect covering this set of problems.

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

Comment 2 Dave Steinberg

2006-05-17 14:34:53 EDT

Reopening to mark WORKSFORME.

Comment 3 Dave Steinberg

2006-05-17 14:37:23 EDT

I cannot reproduce this problem.  If I neglect the @model on an interface, no EClass will be created in the model. Instead, I'll get a reference to EObject and an error complaining that the opposite refers to a feature that doesn't exist.