<p>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.</p>
<p>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!</p>
<p>sent on the move</p>
<p>On 2 May 2012 20:20, "Wolfgang Laun" <<a href="mailto:wolfgang.laun@gmail.com">wolfgang.laun@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Yes, the idea is to insert Models, Brands, Parts, and possibly additional facts.<br>
<br>
You might want to keep lists of child objects or used parts in the<br>
parent objects - see Michael's rule.<br>
<br>
Otherwise:<br>
Relating a Model to a Brand and a Brand to a Manufacturer is simple: a<br>
"parent" reference is sufficient. For Parts, you might want to<br>
establish a Gozinto fact, combining a Part and a Model.<br>
<br>
rule "whereIsPV999999"<br>
when<br>
$part: Part( partName == "PV999999" )<br>
Gozinto( part == $part, $model: model )<br>
Model( this == $model, $brand: brand )<br>
Brand( this == $brand, $manu: manufacturer )<br>
Manufacturer( this == $manu )<br>
then<br>
System.out.println( "PV999999 used in " + $model + "/" + $brand +<br>
" by " + $manu );<br>
end<br>
<br>
For deciding between using this or the "contains" search in potential parents,<br>
there are issues w.r.t. the number of objects you have, the rules<br>
you'd really use, and how frequently what is evaluated, and concerning<br>
the ease of rule maintenance.<br>
<br>
It is indeed possible to extract all from a small set of Manufacturer<br>
facts, but nested "from" CEs are most likely bad for performance.<br>
<br>
-W<br>
<br>
<br>
<br>
On 02/05/2012, James K <<a href="mailto:james_kosa@verizon.net">james_kosa@verizon.net</a>> wrote:<br>
> Luane - Yes, it would be a normalized database, there would be only one<br>
> entry<br>
> for a manufacturer with all of the child records related by Foreign Keys or<br>
> relational tables.<br>
><br>
> Excuse my ignorance I am relatively new to Drools, can you please expand on<br>
> the following:<br>
><br>
> "...(...$p.getPartsName()...) "<br>
><br>
> This is where I am having a hard time on how to navigate into the nested<br>
> collections. Or are you saying to insert the PART, MODEL, BRAND, etc as<br>
> individual facts? How would I relate it back Automanufacturer fact?<br>
><br>
><br>
> --<br>
> View this message in context:<br>
> <a href="http://drools.46999.n3.nabble.com/Accessing-properties-of-an-object-within-a-Nested-Collection-of-a-Nested-Collection-tp3955591p3956880.html" target="_blank">http://drools.46999.n3.nabble.com/Accessing-properties-of-an-object-within-a-Nested-Collection-of-a-Nested-Collection-tp3955591p3956880.html</a><br>
> Sent from the Drools: User forum mailing list archive at Nabble.com.<br>
> _______________________________________________<br>
> rules-users mailing list<br>
> <a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
><br>
_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
</blockquote></p>