12:42 p.m.
I am having a hard time trying to figure this out, maybe it is obvious and I
have overlooked it.... I am trying to evaluate properties of a object
contained within a nested collection of a nested collection on the LHS.
Here is an example of the object model I am working with.
*AutoManufacturer* is the parent class, with *Brand* residing in a
collection on the object, with *Model* residing in a collection on *Brand*,
and finally, *Part* residing in a collection of *Model*. These classes were
created for illustration purposes for this question.....
My question more specifically would be, on the LHS, how would I write a rule
for instance that would find all *Part* objects with a Vendor of "PV999999".
Secondly, on the RHS, how could I iterate the resulting collection of Part
objects to print something like the partname for each of them.
Here are the class objects:
AutoManufacturer class
-----------------------------------------------------
package com.nabble.demo.model;
import java.util.ArrayList;
import java.util.List;
/**
* Class that represents an automobile manufacturer
*/
public class AutoManufacturer
{
private String manufacturerName;
private String manufacturerId;
private List<Brand> brandsCollection;
/**
* Default constructor
*/
public AutoManufacturer()
{
this.brandsCollection = new ArrayList<Brand>();
}
/**
* @return the manufacturerName
*/
public String getManufacturerName()
{
return this.manufacturerName;
}
/**
* @param manufacturerName the manufacturerName to set
*/
public void setManufacturerName( String manufacturerName )
{
this.manufacturerName = manufacturerName;
}
/**
* @return the manufacturerId
*/
public String getManufacturerId()
{
return this.manufacturerId;
}
/**
* @param manufacturerId the manufacturerId to set
*/
public void setManufacturerId( String manufacturerId )
{
this.manufacturerId = manufacturerId;
}
/**
* @return the brandsCollection
*/
public List<Brand> getBrandsCollection()
{
return this.brandsCollection;
}
/**
* @param brand the Brand to add to the collection
*/
public void addBrand( Brand brand )
{
this.brandsCollection.add(brand);
}
}
Brand class
------------------------------------------------------
package com.nabble.demo.model;
import java.util.ArrayList;
import java.util.List;
public class Brand
{
private String brandName;
private String brandId;
private List<Model> brandModels;
public Brand()
{
this.brandModels = new ArrayList<Model>();
}
/**
* @return the brandName
*/
public String getBrandName()
{
return brandName;
}
/**
* @param brandName the brandName to set
*/
public void setBrandName( String brandName )
{
this.brandName = brandName;
}
/**
* @return the brandId
*/
public String getBrandId()
{
return brandId;
}
/**
* @param brandId the brandId to set
*/
public void setBrandId( String brandId )
{
this.brandId = brandId;
}
/**
* @return the brandModels
*/
public List<Model> getBrandModels()
{
return brandModels;
}
/**
* @param model the Model to add
*/
public void addModel( Model model )
{
this.brandModels.add(model);
}
}
Model class
--------------------------------------------------------
package com.nabble.demo.model;
import java.util.ArrayList;
import java.util.List;
/**
* Class that represents a particular model of an automaker's brand of car
*/
public class Model
{
private String modelName;
private String modelId;
private List<Part> partsList;
public Model()
{
this.partsList = new ArrayList<Part>();
}
/**
* @return the modelName
*/
public String getModelName()
{
return this.modelName;
}
/**
* @param modelName the modelName to set
*/
public void setModelName( String modelName )
{
this.modelName = modelName;
}
/**
* @return the modelId
*/
public String getModelId()
{
return this.modelId;
}
/**
* @param modelId the modelId to set
*/
public void setModelId( String modelId )
{
this.modelId = modelId;
}
/**
* @return the partsList
*/
public List<Part> getPartsList()
{
return this.partsList;
}
/**
* Method to add new part to collection
*
* @param part
*/
public void addPart( Part part )
{
this.partsList.add(part);
}
}
Part Class
----------------------------------------------------------------
package com.nabble.demo.model;
/**
* Class that represents a part used on a Model of car
*/
public class Part
{
private String partsId;
private String partsName;
private String partVendor;
/**
* Default constructor
*/
public Part()
{
}
/**
* @return the partsId
*/
public String getPartsId()
{
return this.partsId;
}
/**
* @param partsId the partsId to set
*/
public void setPartsId( String partsId )
{
this.partsId = partsId;
}
/**
* @return the partsName
*/
public String getPartsName()
{
return this.partsName;
}
/**
* @param partsName the partsName to set
*/
public void setPartsName( String partsName )
{
this.partsName = partsName;
}
/**
* @return the partVendor
*/
public String getPartVendor()
{
return partVendor;
}
/**
* @param partVendor the partVendor to set
*/
public void setPartVendor( String partVendor )
{
this.partVendor = partVendor;
}
}
Finally...... here is my class to create an instance of the AutoManufacturer
object that would become the FACT for the rule to fire upon.
package com.nabble.demo;
import com.nabble.demo.model.AutoManufacturer;
import com.nabble.demo.model.Brand;
import com.nabble.demo.model.Model;
import com.nabble.demo.model.Part;
/**
* Class to demonstrate using Autommaker model objects
*/
public class ProcessAutomaker
{
/**
* @param args
*/
public static void main( String[] args )
{
//Create instance of AutoManufacturer
AutoManufacturer automanf = new AutoManufacturer();
automanf.setManufacturerId("123456");
automanf.setManufacturerName("Large Auto Maker");
//Create instance of Model
Model model = new Model();
model.setModelName("LargeSUV");
model.setModelName("MN444555");
//Create instances of Part, add to current Model instance
Part part = new Part();
part.setPartsId("PP123456");
part.setPartsName("Steering Wheel");
part.setPartVendor("PV999999");
model.addPart(part);
part = new Part();
part.setPartsId("PP123499");
part.setPartsName("Brake Pedal");
part.setPartVendor("PV999999");
model.addPart(part);
part = new Part();
part.setPartsId("PP123499");
part.setPartsName("Floor Mat");
part.setPartVendor("PV111111");
model.addPart(part);
//Create instance of Brand
Brand brand = new Brand();
brand.setBrandName("Brand1");
brand.setBrandId("BB123456");
brand.addModel(model);
automanf.addBrand(brand);
}
}
--
View this message in context:
http://drools.46999.n3.nabble.com/Accessing-properties-of-an-object-withi...
Sent from the Drools: User forum mailing list archive at Nabble.com.
12:52 p.m.
Consider not only inserting a single This-is-my-Universe fact but all
of its component objects: Brands, Models and Parts.
rule "parts of PV999999"
when
$p: Part( partVendor == "PV999999" )
then
...(...$p.getPartsName()...)
end
(In a plain old database: would you have just a single AutoManufacturer record?)
-W
On 02/05/2012, aa034373 <james_kosa(a)verizon.net> wrote:
I am having a hard time trying to figure this out, maybe it is
obvious and
I
have overlooked it.... I am trying to evaluate properties of a object
contained within a nested collection of a nested collection on the LHS.
Here is an example of the object model I am working with.
*AutoManufacturer* is the parent class, with *Brand* residing in a
collection on the object, with *Model* residing in a collection on *Brand*,
and finally, *Part* residing in a collection of *Model*. These classes
were
created for illustration purposes for this question.....
My question more specifically would be, on the LHS, how would I write a
rule
for instance that would find all *Part* objects with a Vendor of
"PV999999".
Secondly, on the RHS, how could I iterate the resulting collection of Part
objects to print something like the partname for each of them.
Here are the class objects:
AutoManufacturer class
-----------------------------------------------------
package com.nabble.demo.model;
import java.util.ArrayList;
import java.util.List;
/**
* Class that represents an automobile manufacturer
*/
public class AutoManufacturer
{
private String manufacturerName;
private String manufacturerId;
private List<Brand> brandsCollection;
/**
* Default constructor
*/
public AutoManufacturer()
{
this.brandsCollection = new ArrayList<Brand>();
}
/**
* @return the manufacturerName
*/
public String getManufacturerName()
{
return this.manufacturerName;
}
/**
* @param manufacturerName the manufacturerName to set
*/
public void setManufacturerName( String manufacturerName )
{
this.manufacturerName = manufacturerName;
}
/**
* @return the manufacturerId
*/
public String getManufacturerId()
{
return this.manufacturerId;
}
/**
* @param manufacturerId the manufacturerId to set
*/
public void setManufacturerId( String manufacturerId )
{
this.manufacturerId = manufacturerId;
}
/**
* @return the brandsCollection
*/
public List<Brand> getBrandsCollection()
{
return this.brandsCollection;
}
/**
* @param brand the Brand to add to the collection
*/
public void addBrand( Brand brand )
{
this.brandsCollection.add(brand);
}
}
Brand class
------------------------------------------------------
package com.nabble.demo.model;
import java.util.ArrayList;
import java.util.List;
public class Brand
{
private String brandName;
private String brandId;
private List<Model> brandModels;
public Brand()
{
this.brandModels = new ArrayList<Model>();
}
/**
* @return the brandName
*/
public String getBrandName()
{
return brandName;
}
/**
* @param brandName the brandName to set
*/
public void setBrandName( String brandName )
{
this.brandName = brandName;
}
/**
* @return the brandId
*/
public String getBrandId()
{
return brandId;
}
/**
* @param brandId the brandId to set
*/
public void setBrandId( String brandId )
{
this.brandId = brandId;
}
/**
* @return the brandModels
*/
public List<Model> getBrandModels()
{
return brandModels;
}
/**
* @param model the Model to add
*/
public void addModel( Model model )
{
this.brandModels.add(model);
}
}
Model class
--------------------------------------------------------
package com.nabble.demo.model;
import java.util.ArrayList;
import java.util.List;
/**
* Class that represents a particular model of an automaker's brand of car
*/
public class Model
{
private String modelName;
private String modelId;
private List<Part> partsList;
public Model()
{
this.partsList = new ArrayList<Part>();
}
/**
* @return the modelName
*/
public String getModelName()
{
return this.modelName;
}
/**
* @param modelName the modelName to set
*/
public void setModelName( String modelName )
{
this.modelName = modelName;
}
/**
* @return the modelId
*/
public String getModelId()
{
return this.modelId;
}
/**
* @param modelId the modelId to set
*/
public void setModelId( String modelId )
{
this.modelId = modelId;
}
/**
* @return the partsList
*/
public List<Part> getPartsList()
{
return this.partsList;
}
/**
* Method to add new part to collection
*
* @param part
*/
public void addPart( Part part )
{
this.partsList.add(part);
}
}
Part Class
----------------------------------------------------------------
package com.nabble.demo.model;
/**
* Class that represents a part used on a Model of car
*/
public class Part
{
private String partsId;
private String partsName;
private String partVendor;
/**
* Default constructor
*/
public Part()
{
}
/**
* @return the partsId
*/
public String getPartsId()
{
return this.partsId;
}
/**
* @param partsId the partsId to set
*/
public void setPartsId( String partsId )
{
this.partsId = partsId;
}
/**
* @return the partsName
*/
public String getPartsName()
{
return this.partsName;
}
/**
* @param partsName the partsName to set
*/
public void setPartsName( String partsName )
{
this.partsName = partsName;
}
/**
* @return the partVendor
*/
public String getPartVendor()
{
return partVendor;
}
/**
* @param partVendor the partVendor to set
*/
public void setPartVendor( String partVendor )
{
this.partVendor = partVendor;
}
}
Finally...... here is my class to create an instance of the
AutoManufacturer
object that would become the FACT for the rule to fire upon.
package com.nabble.demo;
import com.nabble.demo.model.AutoManufacturer;
import com.nabble.demo.model.Brand;
import com.nabble.demo.model.Model;
import com.nabble.demo.model.Part;
/**
* Class to demonstrate using Autommaker model objects
*/
public class ProcessAutomaker
{
/**
* @param args
*/
public static void main( String[] args )
{
//Create instance of AutoManufacturer
AutoManufacturer automanf = new AutoManufacturer();
automanf.setManufacturerId("123456");
automanf.setManufacturerName("Large Auto Maker");
//Create instance of Model
Model model = new Model();
model.setModelName("LargeSUV");
model.setModelName("MN444555");
//Create instances of Part, add to current Model instance
Part part = new Part();
part.setPartsId("PP123456");
part.setPartsName("Steering Wheel");
part.setPartVendor("PV999999");
model.addPart(part);
part = new Part();
part.setPartsId("PP123499");
part.setPartsName("Brake Pedal");
part.setPartVendor("PV999999");
model.addPart(part);
part = new Part();
part.setPartsId("PP123499");
part.setPartsName("Floor Mat");
part.setPartVendor("PV111111");
model.addPart(part);
//Create instance of Brand
Brand brand = new Brand();
brand.setBrandName("Brand1");
brand.setBrandId("BB123456");
brand.addModel(model);
automanf.addBrand(brand);
}
}
--
View this message in context:
http://drools.46999.n3.nabble.com/Accessing-properties-of-an-object-withi...
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
1:04 p.m.
Luane - Yes, it would be a normalized database, there would be only one entry
for a manufacturer with all of the child records related by Foreign Keys or
relational tables.
Excuse my ignorance I am relatively new to Drools, can you please expand on
the following:
"...(...$p.getPartsName()...) "
This is where I am having a hard time on how to navigate into the nested
collections. Or are you saying to insert the PART, MODEL, BRAND, etc as
individual facts? How would I relate it back Automanufacturer fact?
--
View this message in context:
http://drools.46999.n3.nabble.com/Accessing-properties-of-an-object-withi...
Sent from the Drools: User forum mailing list archive at Nabble.com.
1:42 p.m.
You wouldn't be able to query just the AutoManufacturer record though.
You'd need to perform a join across tables, e.g.:-
when
$p: Part( partVendor == "PV999999" )
$m: Model( partsList contains $p )
$b: Brand( brandModels contains $m )
$a : AutoManufacturer( brandsCollection contains $b )
then
System.out.println( $p + ", " + $m + ", " + $b + ", " + $a
);
end
On 2 May 2012 19:04, James K <james_kosa(a)verizon.net> wrote:
Luane - Yes, it would be a normalized database, there would be only
one
entry
for a manufacturer with all of the child records related by Foreign Keys or
relational tables.
Excuse my ignorance I am relatively new to Drools, can you please expand on
the following:
"...(...$p.getPartsName()...) "
This is where I am having a hard time on how to navigate into the nested
collections. Or are you saying to insert the PART, MODEL, BRAND, etc as
individual facts? How would I relate it back Automanufacturer fact?
--
View this message in context:
http://drools.46999.n3.nabble.com/Accessing-properties-of-an-object-withi...
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
9:16 a.m.
Thank you laune and manstis for the excellent / relevant information! I have
a follow on question based on my findings the last couple of days using the
information you have provided. I am using Drools Flow, firing the following
rule in a *Rules Task* in my flow. Initially, I am only inserting a
populated *AutoManufacturer* into the flow as my transport object. In the
flow, I am able to access the sub-objects / collections on the parent to
control flow. I prefer to keep it this way.
However, it does not appear the sub-objects on the parent object are
available for LHS evaluation in the rule. So, I am creating a memory entry
for the automanufacturer objects and then iterating collections on the
object / sub-objects to insert them as facts. This is working, however, is
there not a way to do some sort of introspect on collections on the parent
object instead of inserting all of the additional facts and joining them
back together? Is there a better way to be doing this? Another perspective
to approach this?
Rule Code
--------------------------------------------------------------
package com.nabble.demo
import com.nabble.demo.model.Part;
import com.nabble.demo.model.Brand;
import com.nabble.demo.model.Model;
import com.nabble.demo.model.AutoManufacturer;
rule "Insert additional facts from AutoManufacturer Base Class"
ruleflow-group "determineVendors"
when
$autoMfg : AutoManufacturer()
then
for(Brand brand : $autoMfg.getBrandsCollection()){
System.out.println ("Adding Brand Fact: " + brand.getBrandName());
insert(brand);
for (Model model : brand.getBrandModels())
{
System.out.println ("Adding Model as Fact: " +
model.getModelName());
insert(model);
for (Part part : model.getPartsList())
{
System.out.println ("Adding Part as Fact: " +
part.getPartsName());
insert(part);
}
}
}
end
rule "Part Vendor = PV999999"
ruleflow-group "determineVendors"
when
$p: Part( partVendor == "PV999999" )
$m: Model( partsList contains $p )
$b: Brand( brandModels contains $m)
$a : AutoManufacturer( brandsCollection contains $b )
then
System.out.println( "Manf: " +$a.getManufacturerName() + " , Brand
Name: " + $b.getBrandName() + " , Brand ID: " + $b.getBrandId() + " ,
Model
Name: " + $m.getModelName() + " , Part ID: " + $p.getPartsId()+ " ,
Part
Name: " + $p.getPartsName());
end
--
View this message in context:
http://drools.46999.n3.nabble.com/Accessing-properties-of-an-object-withi...
Sent from the Drools: User forum mailing list archive at Nabble.com.
2:19 p.m.
Yes, the idea is to insert Models, Brands, Parts, and possibly additional facts.
You might want to keep lists of child objects or used parts in the
parent objects - see Michael's rule.
Otherwise:
Relating a Model to a Brand and a Brand to a Manufacturer is simple: a
"parent" reference is sufficient. For Parts, you might want to
establish a Gozinto fact, combining a Part and a Model.
rule "whereIsPV999999"
when
$part: Part( partName == "PV999999" )
Gozinto( part == $part, $model: model )
Model( this == $model, $brand: brand )
Brand( this == $brand, $manu: manufacturer )
Manufacturer( this == $manu )
then
System.out.println( "PV999999 used in " + $model + "/" + $brand
+
" by " + $manu );
end
For deciding between using this or the "contains" search in potential parents,
there are issues w.r.t. the number of objects you have, the rules
you'd really use, and how frequently what is evaluated, and concerning
the ease of rule maintenance.
It is indeed possible to extract all from a small set of Manufacturer
facts, but nested "from" CEs are most likely bad for performance.
-W
On 02/05/2012, James K <james_kosa(a)verizon.net> wrote:
Luane - Yes, it would be a normalized database, there would be only
one
entry
for a manufacturer with all of the child records related by Foreign Keys or
relational tables.
Excuse my ignorance I am relatively new to Drools, can you please expand on
the following:
"...(...$p.getPartsName()...) "
This is where I am having a hard time on how to navigate into the nested
collections. Or are you saying to insert the PART, MODEL, BRAND, etc as
individual facts? How would I relate it back Automanufacturer fact?
--
View this message in context:
http://drools.46999.n3.nabble.com/Accessing-properties-of-an-object-withi...
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
3:30 p.m.
Since the auto manufacturers data is reasonably static you could also use a
"bootstrap" rule that inserts all Parts, Models and Brands from the
AutoManufacturer objects inserted by your java code.
I assume your rules will probably look at supply or costing decisions
updating the static reference data less frequent than the decisions you
make based on the reference data - but I could easily be wrong!
sent on the move
On 2 May 2012 20:20, "Wolfgang Laun" <wolfgang.laun(a)gmail.com> wrote:
Yes, the idea is to insert Models, Brands, Parts, and possibly
additional
facts.
You might want to keep lists of child objects or used parts in the
parent objects - see Michael's rule.
Otherwise:
Relating a Model to a Brand and a Brand to a Manufacturer is simple: a
"parent" reference is sufficient. For Parts, you might want to
establish a Gozinto fact, combining a Part and a Model.
rule "whereIsPV999999"
when
$part: Part( partName == "PV999999" )
Gozinto( part == $part, $model: model )
Model( this == $model, $brand: brand )
Brand( this == $brand, $manu: manufacturer )
Manufacturer( this == $manu )
then
System.out.println( "PV999999 used in " + $model + "/" + $brand
+
" by " + $manu );
end
For deciding between using this or the "contains" search in potential
parents,
there are issues w.r.t. the number of objects you have, the rules
you'd really use, and how frequently what is evaluated, and concerning
the ease of rule maintenance.
It is indeed possible to extract all from a small set of Manufacturer
facts, but nested "from" CEs are most likely bad for performance.
-W
On 02/05/2012, James K <james_kosa(a)verizon.net> wrote:
> Luane - Yes, it would be a normalized database, there would be only one
> entry
> for a manufacturer with all of the child records related by Foreign Keys
or
> relational tables.
>
> Excuse my ignorance I am relatively new to Drools, can you please expand
on
> the following:
>
> "...(...$p.getPartsName()...) "
>
> This is where I am having a hard time on how to navigate into the nested
> collections. Or are you saying to insert the PART, MODEL, BRAND, etc as
> individual facts? How would I relate it back Automanufacturer fact?
>
>
> --
> View this message in context:
>
http://drools.46999.n3.nabble.com/Accessing-properties-of-an-object-withi...
> Sent from the Drools: User forum mailing list archive at Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
9:42 a.m.
Thank you laune and manstis for the excellent / relevant information! I have
a follow on question based on my findings the last couple of days using the
information you have provided. I am using Drools Flow, firing the following
rule in a Rules Task in my flow. Initially, I am only inserting a populated
AutoManufacturer into the flow as my transport object. In the flow, I am
able to access the sub-objects / collections on the parent to control flow.
I prefer to keep it this way.
However, it does not appear the sub-objects on the parent object are
available for LHS evaluation in the rule. So, I am creating a memory entry
for the automanufacturer objects and then iterating collections on the
object / sub-objects to insert them as facts. This is working, however, is
there not a way to do some sort of introspect on collections on the parent
object instead of inserting all of the additional facts and joining them
back together? Is there a better way to be doing this? Another perspective
to approach this?
Rule Code
--------------------------------------------------------------
package com.nabble.demo
import com.nabble.demo.model.Part;
import com.nabble.demo.model.Brand;
import com.nabble.demo.model.Model;
import com.nabble.demo.model.AutoManufacturer;
rule "Insert additional facts from AutoManufacturer Base Class"
ruleflow-group "determineVendors"
when
$autoMfg : AutoManufacturer()
then
for(Brand brand : $autoMfg.getBrandsCollection()){
System.out.println ("Adding Brand Fact: " + brand.getBrandName());
insert(brand);
for (Model model : brand.getBrandModels())
{
System.out.println ("Adding Model as Fact: " +
model.getModelName());
insert(model);
for (Part part : model.getPartsList())
{
System.out.println ("Adding Part as Fact: " +
part.getPartsName());
insert(part);
}
}
}
end
rule "Part Vendor = PV999999"
ruleflow-group "determineVendors"
when
$p: Part( partVendor == "PV999999" )
$m: Model( partsList contains $p )
$b: Brand( brandModels contains $m)
$a : AutoManufacturer( brandsCollection contains $b )
then
System.out.println( "Manf: " +$a.getManufacturerName() + " , Brand
Name: " + $b.getBrandName() + " , Brand ID: " + $b.getBrandId() + " ,
Model
Name: " + $m.getModelName() + " , Part ID: " + $p.getPartsId()+ " ,
Part
Name: " + $p.getPartsName());
end
--
View this message in context:
http://drools.46999.n3.nabble.com/Accessing-properties-of-an-object-withi...
Sent from the Drools: User forum mailing list archive at Nabble.com.
11:34 a.m.
It's also possible to create "relation" objects in addition to the data
objects
and insert these. In this situation, it might be a quadruple of Manufaturer,
Brand, Model and Part. These facts can be used in a number of ways, e.g.,
for obtaining all Models of a Brand, all Parts of a Model, all Models where
a
Part is used, etc.
-W
On 4 May 2012 16:42, James K <james_kosa(a)verizon.net> wrote:
Thank you laune and manstis for the excellent / relevant information!
I
have
a follow on question based on my findings the last couple of days using the
information you have provided. I am using Drools Flow, firing the
following
rule in a Rules Task in my flow. Initially, I am only inserting a
populated
AutoManufacturer into the flow as my transport object. In the flow, I am
able to access the sub-objects / collections on the parent to control flow.
I prefer to keep it this way.
However, it does not appear the sub-objects on the parent object are
available for LHS evaluation in the rule. So, I am creating a memory entry
for the automanufacturer objects and then iterating collections on the
object / sub-objects to insert them as facts. This is working, however,
is
there not a way to do some sort of introspect on collections on the parent
object instead of inserting all of the additional facts and joining them
back together? Is there a better way to be doing this? Another perspective
to approach this?
Rule Code
--------------------------------------------------------------
package com.nabble.demo
import com.nabble.demo.model.Part;
import com.nabble.demo.model.Brand;
import com.nabble.demo.model.Model;
import com.nabble.demo.model.AutoManufacturer;
rule "Insert additional facts from AutoManufacturer Base Class"
ruleflow-group "determineVendors"
when
$autoMfg : AutoManufacturer()
then
for(Brand brand : $autoMfg.getBrandsCollection()){
System.out.println ("Adding Brand Fact: " + brand.getBrandName());
insert(brand);
for (Model model : brand.getBrandModels())
{
System.out.println ("Adding Model as Fact: " +
model.getModelName());
insert(model);
for (Part part : model.getPartsList())
{
System.out.println ("Adding Part as Fact: " +
part.getPartsName());
insert(part);
}
}
}
end
rule "Part Vendor = PV999999"
ruleflow-group "determineVendors"
when
$p: Part( partVendor == "PV999999" )
$m: Model( partsList contains $p )
$b: Brand( brandModels contains $m)
$a : AutoManufacturer( brandsCollection contains $b )
then
System.out.println( "Manf: " +$a.getManufacturerName() + " , Brand
Name: " + $b.getBrandName() + " , Brand ID: " + $b.getBrandId() + " ,
Model
Name: " + $m.getModelName() + " , Part ID: " + $p.getPartsId()+ " ,
Part
Name: " + $p.getPartsName());
end
--
View this message in context:
http://drools.46999.n3.nabble.com/Accessing-properties-of-an-object-withi...
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
4589
days inactive
4591
days old
8 comments
4 participants
participants (4)
-
aa034373 -
James K
-
Michael Anstis -
Wolfgang Laun