|
|
| Re: EcoreValidator - EClassifier::WellFormedInstanceTypeName constraint [message #418506 is a reply to message #418501] |
Thu, 17 April 2008 11:59  |
 Adolfo Sanchez-Barbudo Herrera
Messages: 260
Registered: July 2009 |
Senior Member |
|
|
I see..It makes sense.
For my concrete use, in which I throw a lot of information in console
derived from a lot of test cases, would be helpful. However I should not
modify my validator because it will be used my textual and Sample Core
Editor as well, and the markers could get me to the erroneous class.
Thank you very much !!!
Cheers,
Adolfo.
Ed Merks escribió:
> Adolfo,
>
> Comments below.
>
>
> Adolfo Sánchez-Barbudo Herrera wrote:
>> Hi Ed,
>>
>> Working on a QVTo-EValidator based on OCL-EValidator which is based on
>> Ecore one, I had the following error:
>>
>> Validator-ERROR in org.eclipse.emf.ecore.model; IfExp.qvto:1 : The
>> instance type name 'null' is not well formed.
>>
>> Which certainly didn't help me too much to know what happened. What
>> about including additional information in the error message such as
>> the name of the Eclassifier which violate the constraint?
> The Diagnostic.getData() has a reference to the object for which this
> error applies and all the code is factored in such a way that clients
> can form their own messages. Generally we expect markers to be created
> and that clicking on the marker will navigate directly to the offending
> instance so it can be corrected. Consider Java errors such as "Syntax
> error, insert ";" to complete statement" which also don't indicate the
> file, class, or method in which the problem appears or any other
> contextual information because it's generally expecting the context
> information will be available in whatever view shows the error...
>>
>> Regards,
>> Adolfo.
|
|
|
Powered by
FUDForum. Page generated in 0.02565 seconds
] 
Search
Help
Register
Login
Home
