Recent changes to EMFQueryProcessor

WikiPage EMFQueryProcessor modified by Radu Comaneci

Radu Comaneci — Mon, 17 Sep 2012 15:00:26 -0000

--- v23
+++ v24
@@ -30,7 +30,8 @@
     results.get(0);    //returns the first tuple of elements
     results.get(0).getElements();    //returns the list of elements which represents the tuple
     results.get(0).getElements().get(0);    //returns the first element from the first tuple
-    results.get(0).getElements().get(0).getName();    //returns the alias of the first element
+    results.get(0).getElements().get(0).getName();    //returns the name of the first element as specified in the rule
+    results.get(0).getElements().get(0).getAlias();    //returns the alias of the first element as specified in the rule
     results.get(0).getElements().get(0).getContent();    //returns the EObject which is stored in the first element of the first tuple

WikiPage EMFQueryProcessor modified by Radu Comaneci

Radu Comaneci — Mon, 10 Sep 2012 13:54:43 -0000

--- v22
+++ v23
@@ -39,6 +39,10 @@
 An important component of EMFQueryProcessor is TuplesProcessor. This is responsible for generating the tuples which are sent as input to the query. The query iterates over these tuples, aplies the condition and reveals the results. 
 Normally, a TuplesProcessor object cannot be instantiated manually. It is part of the EMFQueryProcessor. However, if you really need to generate tuples based on a rule definition you can instantiate it using the following commands:
 
+    List tuples;
+    TuplesProcessor tuplesProcessor = new TuplesProcessor(accessLayer, project);
+    tuples = tuplesProcessor.run(elementsFromRepository);
+
 
 The tuples processor returns a list of EMFQueryElement objects which represents the tuples of meta models from the EMFStore repository. The elements from this list can be accessed the same as the elements from the list of results since the structure of lists is the same (see the above section). 
 For the following ElementDefinition objects from a rule:
@@ -57,4 +61,3 @@
 ConditionsProcessor
 
 ConditionsProcessor is another component which is part of EMFQueryProcessor. It is responsible for generating the EObjectCondition based on the LogicCondition object from the rule definition. 
-

WikiPage EMFQueryProcessor modified by Radu Comaneci

Radu Comaneci — Tue, 28 Aug 2012 14:54:05 -0000

--- v21
+++ v22
@@ -54,5 +54,7 @@
 
 where Class, Parameter and Function are all possible combinations of meta models from the EMFStore repository. 
 
+ConditionsProcessor
 
+ConditionsProcessor is another component which is part of EMFQueryProcessor. It is responsible for generating the EObjectCondition based on the LogicCondition object from the rule definition.

WikiPage EMFQueryProcessor modified by Radu Comaneci

Radu Comaneci — Tue, 28 Aug 2012 14:49:59 -0000

--- v20
+++ v21
@@ -33,6 +33,7 @@
     results.get(0).getElements().get(0).getName();    //returns the alias of the first element
     results.get(0).getElements().get(0).getContent();    //returns the EObject which is stored in the first element of the first tuple
 
+
 TuplesProcessor
 
 An important component of EMFQueryProcessor is TuplesProcessor. This is responsible for generating the tuples which are sent as input to the query. The query iterates over these tuples, aplies the condition and reveals the results.

WikiPage EMFQueryProcessor modified by Radu Comaneci

Radu Comaneci — Tue, 28 Aug 2012 14:49:42 -0000

--- v19
+++ v20
@@ -40,14 +40,18 @@
 
 
 The tuples processor returns a list of EMFQueryElement objects which represents the tuples of meta models from the EMFStore repository. The elements from this list can be accessed the same as the elements from the list of results since the structure of lists is the same (see the above section). 
-For the following ElementDefinition objects inside of a rule:
+For the following ElementDefinition objects from a rule:
 
     
       
       
       
 
-sdfsfs
+the TupleProcesor would generate a list of EMFQueryElement objects with the following structure:
+
+    results = [Class, Parameter, Function]
+
+where Class, Parameter and Function are all possible combinations of meta models from the EMFStore repository.

WikiPage EMFQueryProcessor modified by Radu Comaneci

Radu Comaneci — Tue, 28 Aug 2012 14:47:17 -0000

--- v18
+++ v19
@@ -40,6 +40,14 @@
 
 
 The tuples processor returns a list of EMFQueryElement objects which represents the tuples of meta models from the EMFStore repository. The elements from this list can be accessed the same as the elements from the list of results since the structure of lists is the same (see the above section). 
+For the following ElementDefinition objects inside of a rule:
+
+    
+      
+      
+      
+
+sdfsfs

WikiPage EMFQueryProcessor modified by Radu Comaneci

Radu Comaneci — Tue, 28 Aug 2012 14:43:16 -0000

--- v17
+++ v18
@@ -39,7 +39,7 @@
 Normally, a TuplesProcessor object cannot be instantiated manually. It is part of the EMFQueryProcessor. However, if you really need to generate tuples based on a rule definition you can instantiate it using the following commands:
 
 
-The tuples processor returns a list of EMFQueryElement objects which represents the tuples of meta models from the EMFStore repository. The way the elements from this list can be accessed is the same as the way the list of results can be accessed (see the above section). 
+The tuples processor returns a list of EMFQueryElement objects which represents the tuples of meta models from the EMFStore repository. The elements from this list can be accessed the same as the elements from the list of results since the structure of lists is the same (see the above section).

WikiPage EMFQueryProcessor modified by Radu Comaneci

Radu Comaneci — Tue, 28 Aug 2012 14:42:12 -0000

--- v16
+++ v17
@@ -36,7 +36,9 @@
 TuplesProcessor
 
 An important component of EMFQueryProcessor is TuplesProcessor. This is responsible for generating the tuples which are sent as input to the query. The query iterates over these tuples, aplies the condition and reveals the results. 
-Normally, a TuplesProcessor object cannot be instantiated manually. It is part of the EMFQueryProcessor. However, if you really need to generate tuples based on a rule definition you can instantiate it. 
+Normally, a TuplesProcessor object cannot be instantiated manually. It is part of the EMFQueryProcessor. However, if you really need to generate tuples based on a rule definition you can instantiate it using the following commands:
+
+
 The tuples processor returns a list of EMFQueryElement objects which represents the tuples of meta models from the EMFStore repository. The way the elements from this list can be accessed is the same as the way the list of results can be accessed (see the above section).

WikiPage EMFQueryProcessor modified by Radu Comaneci

Radu Comaneci — Tue, 28 Aug 2012 14:41:26 -0000

--- v15
+++ v16
@@ -33,5 +33,11 @@
     results.get(0).getElements().get(0).getName();    //returns the alias of the first element
     results.get(0).getElements().get(0).getContent();    //returns the EObject which is stored in the first element of the first tuple
 
+TuplesProcessor
+
+An important component of EMFQueryProcessor is TuplesProcessor. This is responsible for generating the tuples which are sent as input to the query. The query iterates over these tuples, aplies the condition and reveals the results. 
+Normally, a TuplesProcessor object cannot be instantiated manually. It is part of the EMFQueryProcessor. However, if you really need to generate tuples based on a rule definition you can instantiate it. 
+The tuples processor returns a list of EMFQueryElement objects which represents the tuples of meta models from the EMFStore repository. The way the elements from this list can be accessed is the same as the way the list of results can be accessed (see the above section). 
 
 
+

WikiPage EMFQueryProcessor modified by Radu Comaneci

Radu Comaneci — Tue, 28 Aug 2012 14:35:44 -0000

--- v14
+++ v15
@@ -6,7 +6,7 @@
 * Actions - which are represented as a list of ActionDefinition objects
 * Conditions - which are represented as a LogicCondition object
 
-However, EFMQueryProcessor doesn't crash and works even if the rule that is received doesn't contain all of this fields. But for getting the desired results you should specify all of these tree fields. 
+However, EFMQueryProcessor doesn't crash and works even if the rule that is received doesn't contain all of this fields. But for getting the desired results you should specify all of these three fields. 
 
 Requirements and restrictions: