Oh, to further explain...
Sometimes, we'll take 2 nodes out of the attachableNodes set,
create a JoinNode with the 2 nodes as children, and place the
join back into the set, as it hasn't yet been glued to the tree,
I think.
ie:
## Start with 2 nodes...
an = { node-A, node-B }
## Remove them, create a Join node, with them as children, placing
## the Join node back into the attachableNodes set.
an = { join-node-1( {node-a, node-b} ) }
## Now, remove that node, and attach to the existing RETE network...
an = { }
-bob
On Fri, 24 May 2002, Maheedhar (STP) wrote:
> Hi there
>
> In the Builder Class, the methods
>
> 'attachAssignmentConditions' and 'attachFilterConditions'
>
> replace some of the existing Attachable Nodes(TupleSources). During the
> process the TupleSink of the node being replaced is set as the node that is
> replacing it. My problem is what is the use of setting the TupleSink for a
> node when is removed from the set of AttachableNodes. Also, when a node is
> removed how does a ReteTuple reaches it for getting propagated.
>
> please respond.
>
> Thank you,
>
> ----Maheedhar Vishwanathula
>
>
> _______________________________________________________________
>
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>
> _______________________________________________
> drools-interest mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/drools-interest
>
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
drools-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/drools-interest
