Eclipse Community Forums: EMF "Technology" (Ecore Tools, EMFatic, etc) » [EMF Search] Some random questions on implementing custom model search engine

Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc) » [EMF Search] Some random questions on implementing custom model search engine

Show: Today's Messages :: Show Polls :: Message Navigator

[EMF Search] Some random questions on implementing custom model search engine [message #133306]

Fri, 20 February 2009 12:20

Victor Roldan Betancort

Messages: 524
Registered: July 2009

Senior Member

Hi,

I've been recently experimenting a bit on how to define my own model
search component using EMF Search extension points.

1) Is there something like a generic search engine? I mean, there is the
Ecore search engine implementation, but is an engine that could search
in any Ecore based model? For instance, using Ecore reflective mechanisms?

2) Are some some guidelines on how to reuse all the already available
functionality instead of creating my own implementation?

3) AbstractModelSearchParticipantArea.getSelectedFeatures() is final. I
guess I could do my own implementation but... In my case I haven't
defined any eID in my classes, so in the end I get an array of null
eStructuralFeatures. This method defines the criteria to select the list
of EStructuralFeatures where to search for the incoming query (I guess).
Is there a reason why It cannot be non-final?

I would appreciate anyone sharing their experience with the creation of
a custom model search using EMF Search.

Cheers,
Víctor.

Report message to a moderator

Re: [EMF Search] Some random questions on implementing custom model search engine [message #133353 is a reply to message #133306]

Fri, 20 February 2009 18:43

Victor Roldan Betancort

Messages: 524
Registered: July 2009

Senior Member

:(

After successfully implementing by hand a custom model search engine, I
realized EMF Search has a generator :(

Argh, 2 days wasted.

Cheers,
Víctor.

Víctor Roldán Betancort escribió:
> Hi,
>
> I've been recently experimenting a bit on how to define my own model
> search component using EMF Search extension points.
>
> 1) Is there something like a generic search engine? I mean, there is the
> Ecore search engine implementation, but is an engine that could search
> in any Ecore based model? For instance, using Ecore reflective mechanisms?
>
> 2) Are some some guidelines on how to reuse all the already available
> functionality instead of creating my own implementation?
>
> 3) AbstractModelSearchParticipantArea.getSelectedFeatures() is final. I
> guess I could do my own implementation but... In my case I haven't
> defined any eID in my classes, so in the end I get an array of null
> eStructuralFeatures. This method defines the criteria to select the list
> of EStructuralFeatures where to search for the incoming query (I guess).
> Is there a reason why It cannot be non-final?
>
> I would appreciate anyone sharing their experience with the creation of
> a custom model search using EMF Search.
>
> Cheers,
> Víctor.

Report message to a moderator

Re: [EMF Search] Some random questions on implementing custom model search engine [message #133365 is a reply to message #133353]

Fri, 20 February 2009 18:54

Eike Stepper

Messages: 6682
Registered: July 2009

Senior Member

Vik,

I'm not sure if you found it already, but there's a wiki:
http://wiki.eclipse.org/EMF_Search#Custom_Textual_Search_Cod e_Generation

Cheers
/Eike

----
http://thegordian.blogspot.com

Víctor Roldán Betancort schrieb:
> :(
>
> After successfully implementing by hand a custom model search engine,
> I realized EMF Search has a generator :(
>
> Argh, 2 days wasted.
>
> Cheers,
> Víctor.
>
> Víctor Roldán Betancort escribió:
>> Hi,
>>
>> I've been recently experimenting a bit on how to define my own model
>> search component using EMF Search extension points.
>>
>> 1) Is there something like a generic search engine? I mean, there is
>> the Ecore search engine implementation, but is an engine that could
>> search in any Ecore based model? For instance, using Ecore reflective
>> mechanisms?
>>
>> 2) Are some some guidelines on how to reuse all the already available
>> functionality instead of creating my own implementation?
>>
>> 3) AbstractModelSearchParticipantArea.getSelectedFeatures() is final.
>> I guess I could do my own implementation but... In my case I haven't
>> defined any eID in my classes, so in the end I get an array of null
>> eStructuralFeatures. This method defines the criteria to select the
>> list of EStructuralFeatures where to search for the incoming query (I
>> guess). Is there a reason why It cannot be non-final?
>>
>> I would appreciate anyone sharing their experience with the creation
>> of a custom model search using EMF Search.
>>
>> Cheers,
>> Víctor.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Report message to a moderator

Re: [EMF Search] Some random questions on implementing custom model search engine [message #133378 is a reply to message #133365]

Fri, 20 February 2009 19:09

Victor Roldan Betancort

Messages: 524
Registered: July 2009

Senior Member

Indeed :(

Thanks anyway, Eike!

Eike Stepper escribió:
> Vik,
>
> I'm not sure if you found it already, but there's a wiki:
> http://wiki.eclipse.org/EMF_Search#Custom_Textual_Search_Cod e_Generation
>
> Cheers
> /Eike
>
> ----
> http://thegordian.blogspot.com
>
>
>
> Víctor Roldán Betancort schrieb:
>> :(
>>
>> After successfully implementing by hand a custom model search engine,
>> I realized EMF Search has a generator :(
>>
>> Argh, 2 days wasted.
>>
>> Cheers,
>> Víctor.
>>
>> Víctor Roldán Betancort escribió:
>>> Hi,
>>>
>>> I've been recently experimenting a bit on how to define my own model
>>> search component using EMF Search extension points.
>>>
>>> 1) Is there something like a generic search engine? I mean, there is
>>> the Ecore search engine implementation, but is an engine that could
>>> search in any Ecore based model? For instance, using Ecore reflective
>>> mechanisms?
>>>
>>> 2) Are some some guidelines on how to reuse all the already available
>>> functionality instead of creating my own implementation?
>>>
>>> 3) AbstractModelSearchParticipantArea.getSelectedFeatures() is final.
>>> I guess I could do my own implementation but... In my case I haven't
>>> defined any eID in my classes, so in the end I get an array of null
>>> eStructuralFeatures. This method defines the criteria to select the
>>> list of EStructuralFeatures where to search for the incoming query (I
>>> guess). Is there a reason why It cannot be non-final?
>>>
>>> I would appreciate anyone sharing their experience with the creation
>>> of a custom model search using EMF Search.
>>>
>>> Cheers,
>>> Víctor.

Report message to a moderator