Home » Modeling » EMF » Problem markers from the genmodel editor
|
| Re: Problem markers from the genmodel editor [message #415608 is a reply to message #415600] |
Fri, 21 December 2007 19:38   |
 Ed Merks
Messages: 33141
Registered: July 2009 |
Senior Member |
|
|
Eric,
When I try to duplicate this, i.e., add an EClass without a name, open
the GenModel, tell it to create markers, open Ecore editor and give it a
name, and then invoke validate on the root package and hit OK on the
dialog that says there are no problems the problem markers go away. So
I'm not sure what's going wrong in your case. Is this with EMF 2.3.1?
Eric Rizzo wrote:
> A while ago I had some error in my .ecore model that was reported when
> I tried to open the genmodel. One of the buttons in the genmodel
> editor offered to create problem markers, which I happily used to find
> the problem. Now I've fixed the model and the genmodel opens and
> works. But how do I get rid of the problem markers in my Problems
> view? I've tried invoking Validate on both the .ecore and .genmodel
> files, tried touching and saving both files, and a full project
> rebuild via Project > Clean. None of which will remove the markers.
>
> TIA,
> Eric
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Problem markers from the genmodel editor [message #415613 is a reply to message #415608] |
Fri, 21 December 2007 20:16 |
Eric Rizzo
Messages: 3070
Registered: July 2009 |
Senior Member |
|
|
Ed Merks wrote:
> Eric,
>
> When I try to duplicate this, i.e., add an EClass without a name, open
> the GenModel, tell it to create markers, open Ecore editor and give it a
> name, and then invoke validate on the root package and hit OK on the
> dialog that says there are no problems the problem markers go away. So
> I'm not sure what's going wrong in your case. Is this with EMF 2.3.1?
EMF 2.3.0
The step I was missing was to Validate the root package. I had tried
invoking Validate on the file (from Navigator) and on the root *node*
(parent of the root package) with no results. Validating the root
package did the trick.
Should I file a bug about this - it is not very intuitive to the user
how to get rid of those markers. Is it documented anywhere?
Thanks,
Eric
> Eric Rizzo wrote:
>> A while ago I had some error in my .ecore model that was reported when
>> I tried to open the genmodel. One of the buttons in the genmodel
>> editor offered to create problem markers, which I happily used to find
>> the problem. Now I've fixed the model and the genmodel opens and
>> works. But how do I get rid of the problem markers in my Problems
>> view? I've tried invoking Validate on both the .ecore and .genmodel
>> files, tried touching and saving both files, and a full project
>> rebuild via Project > Clean. None of which will remove the markers.
>>
>> TIA,
>> Eric
|
|
|
| Re: Problem markers from the genmodel editor [message #415614 is a reply to message #415613] |
Fri, 21 December 2007 20:39 |
Ed Merks
Messages: 33141
Registered: July 2009 |
Senior Member |
|
|
Eric,
Is there a validate action on the file itself? I think that's one of
those annoying WTP contributions that really shouldn't be there at all
(because it's useless for a .ecore file) and there is a bugzilla about
it, though I don't remember the number. All EMF editors, not just the
Ecore editor, support instance validation the same way and I don't
really want to provide it as an action on the files...
Eric Rizzo wrote:
> Ed Merks wrote:
>> Eric,
>>
>> When I try to duplicate this, i.e., add an EClass without a name,
>> open the GenModel, tell it to create markers, open Ecore editor and
>> give it a name, and then invoke validate on the root package and hit
>> OK on the dialog that says there are no problems the problem markers
>> go away. So I'm not sure what's going wrong in your case. Is this
>> with EMF 2.3.1?
>
> EMF 2.3.0
> The step I was missing was to Validate the root package. I had tried
> invoking Validate on the file (from Navigator) and on the root *node*
> (parent of the root package) with no results. Validating the root
> package did the trick.
> Should I file a bug about this - it is not very intuitive to the user
> how to get rid of those markers. Is it documented anywhere?
>
> Thanks,
> Eric
>
>
>
>> Eric Rizzo wrote:
>>> A while ago I had some error in my .ecore model that was reported
>>> when I tried to open the genmodel. One of the buttons in the
>>> genmodel editor offered to create problem markers, which I happily
>>> used to find the problem. Now I've fixed the model and the genmodel
>>> opens and works. But how do I get rid of the problem markers in my
>>> Problems view? I've tried invoking Validate on both the .ecore and
>>> .genmodel files, tried touching and saving both files, and a full
>>> project rebuild via Project > Clean. None of which will remove the
>>> markers.
>>>
>>> TIA,
>>> Eric
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Problem markers from the genmodel editor [message #415615 is a reply to message #415614] |
Fri, 21 December 2007 20:42 |
Ed Merks
Messages: 33141
Registered: July 2009 |
Senior Member |
|
|
Eric,
That being said, it might make sense that since the GenModel was used to
create the markers, and actually always does a validation, for it to
remove validation markers when it does a validation that's successful.
I think that would be a reasonable feature request and would eliminate
this point of confusion. After all, if you invoke validate directly
from the popup and it creates markers, it will be obvious to repeat the
process to remove them, but when it's happens by virtue of the GenModel,
you might well not realize there is such a popup action. We've also
been talking about automatically validating the Ecore model before you
save so that you find out about the problem earlier...
Ed Merks wrote:
> Eric,
>
> Is there a validate action on the file itself? I think that's one of
> those annoying WTP contributions that really shouldn't be there at all
> (because it's useless for a .ecore file) and there is a bugzilla about
> it, though I don't remember the number. All EMF editors, not just
> the Ecore editor, support instance validation the same way and I
> don't really want to provide it as an action on the files...
>
>
> Eric Rizzo wrote:
>> Ed Merks wrote:
>>> Eric,
>>>
>>> When I try to duplicate this, i.e., add an EClass without a name,
>>> open the GenModel, tell it to create markers, open Ecore editor and
>>> give it a name, and then invoke validate on the root package and hit
>>> OK on the dialog that says there are no problems the problem markers
>>> go away. So I'm not sure what's going wrong in your case. Is this
>>> with EMF 2.3.1?
>>
>> EMF 2.3.0
>> The step I was missing was to Validate the root package. I had tried
>> invoking Validate on the file (from Navigator) and on the root *node*
>> (parent of the root package) with no results. Validating the root
>> package did the trick.
>> Should I file a bug about this - it is not very intuitive to the user
>> how to get rid of those markers. Is it documented anywhere?
>>
>> Thanks,
>> Eric
>>
>>
>>
>>> Eric Rizzo wrote:
>>>> A while ago I had some error in my .ecore model that was reported
>>>> when I tried to open the genmodel. One of the buttons in the
>>>> genmodel editor offered to create problem markers, which I happily
>>>> used to find the problem. Now I've fixed the model and the genmodel
>>>> opens and works. But how do I get rid of the problem markers in my
>>>> Problems view? I've tried invoking Validate on both the .ecore and
>>>> .genmodel files, tried touching and saving both files, and a full
>>>> project rebuild via Project > Clean. None of which will remove the
>>>> markers.
>>>>
>>>> TIA,
>>>> Eric
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Goto Forum:
Current Time: Fri Apr 26 03:57:17 GMT 2024
Powered by FUDForum. Page generated in 0.03271 seconds |
] 
Search
Help
Register
Login
Home
