Re: [incquery-dev] eclipsecon example

[Tamas Szabo <tamas.szabo@xxxxxxxxx>]

I committed the changes to solve this issue. The registry now uses weak collections to store the features.
Dynamic case: the builder does the work. When you open the editor the builder will be invoked automatically so it is not needed to register the features in some editor code again.
Generated case: the extensions are put to the plugin.xml by the generator and this will be used later.

I have checked it with both cases and it works, please let me know if something is missing.

On second thought, my last idea should NOT be used, as the WellbehavingDerivedFeatureRegistry is in base, which should not have logical or semantic dependency on query-based features!

Weak collections are OK, as dynamic mode is something that BASE is concerned with (and QBF should not be, but that's another issue).

   Ábel Hegedüs

Fault Tolerant Systems Research Group
Department of Measurement and Information Systems
Budapest University of Technology and Economics

On 23 October 2013 12:22, Ábel Hegedüs <abel.hegedus@xxxxxxxxxx> wrote:

Another idea: query-based features have a very specific EAnnotation, that could be checked in the isWellbehaving call (see SDF for an example). In order to increase performance, this check is only needed if the feature is not in the registry. However, the result should not be cached, as that leads back to the weak collection problem again.

Combining the weak collection and the annotation checking, we could completely avoid having to create wellbehaving extensions for query-based features, as they are registered automatically the first time they are encountered. Of course, this works only if the EAnnotations on the feature are always available.

   Ábel Hegedüs

Fault Tolerant Systems Research Group

Department of Measurement and Information Systems

Budapest University of Technology and Economics

On 23 October 2013 12:12, Istvan Rath <rath@xxxxxxxxxx> wrote:

On Wednesday, October 23, 2013 at 12:09 PM, Ábel Hegedüs wrote:

On 23 October 2013 11:30, Tamas Szabo <tamas.szabo@xxxxxxxxx> wrote:

Finally, what about the case when the builder did not run? AFAIK, you created the model editor to work in these cases (thus the query spec registration in the SDF). Shouldn't it (also/instead) register the features?

Yes, it should!

--

Istvan RATH, PhD

Research fellow
Budapest University of Technology and Economics

Fault Tolerant Systems Research Group

_______________________________________________
incquery-dev mailing list
incquery-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/incquery-dev

_______________________________________________
incquery-dev mailing list
incquery-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/incquery-dev

-- 
Tamas Szabo
Software engineer

Tel.:   +49 711 342 191 0
Fax.:   +49 711 342 191 29
Mobil:  +49 171 565 416 9
Web:    www.itemis.de
Mail:   tamas.szabo@xxxxxxxxx
Skype:  szabta89

itemis AG
Niederlassung Süd
Meitnerstr. 10
70563 Stuttgart

Rechtlicher Hinweis:
Registergericht: Amtsgericht Dortmund HRB 20621 | Sitz der Gesellschaft:
Lünen
Vorstand: Jens Wagener (Vorsitzender) | Wolfgang Neuhaus | Dr. Georg
Pietrek | Jens Trompeter | Sebastian Neus
Aufsichtsrat: Prof. Dr. Burkhard Igel (Vorsitzender) | Stephan Grollmann
| Michael Neuhaus