| Re: [incquery-dev] eclipsecon example |
Hi
If nobody has started to deal with this issue then I can fix this thing today.
Cheers,
Tamas
I should have recognised the symptoms (QBF inside query doesn't work) earlier, but you shouldn't have ignored that warning all the way until now :)
The engine will not traverse a feature when building the pattern matchers if it is not well-behaving, e.g. derived. However, you can specify that a given feature is well-behaving through the WellBehavingDerivedFeatureRegistry (catchy name, huh?). This is actually documented here: http://wiki.eclipse.org/EMFIncQuery/UserDocumentation/Query_Based_Features#Well-behaving_structural_features
In the dynamic case: use the register method at some point, before engine initialisationIn the generated case: put the proper extension into the plugin.xml, this was done by the @QueryBasedFeature code generator, I haven't thought that you forgot to do that.
Cheers,Ábel Hegedüs
Fault Tolerant Systems Research Group
Department of Measurement and Information Systems
Budapest University of Technology and Economics
On 22 October 2013 23:44, Istvan Rath <rath@xxxxxxxxxx> wrote:
Two more notes:- this behavior is observed with the Query Explorer as well as the QBF on the Properties View- this behavior is observed with the generated domain editor, meaning it probably has nothing to do with our recent code change to avoid using the QuerySpec registry--
Istvan RATH, PhD
Research fellow
Budapest University of Technology and EconomicsFault Tolerant Systems Research GroupOn Tuesday, October 22, 2013 at 11:20 PM, Istvan Rath wrote:
Just to entertain everyone, it seems we've been happy too early to declare that using QBFs inside QBFs work.
@QueryExplorer(display = true)
pattern weirdBook3(B : Book) {
Book.allCitations(B, B); // doesn't work