I'd previously noticed, and coded for, the fact that inactive
Activations were excised from the agenda by Rete.bsave(). Yesterday,
however, a colleague showed me a case in v7.0b6 where the remaining
entries on the agenda were also reordered after calling bsave(). That
is, I was surprised to get different sequences of active Activations
returned by the 2 Iterators below:
Iterator it1 = rete.listActivations();
rete.bsave(byteArrayOutputStream);
Iterator it2 = rete.listActivations();
It appears that the push() calls in
HeapPriorityQueue.writeObject(ObjectOutputStream) can reorder the
reconstituted agenda. Could you provide a public method that performs
the algorithm in HeapPriorityQueue.writeObject(ObjectOutputStream) yet
skips the actual object serialization call? In other words, could I get
a look at what the agenda will look like after bsave() without the
performance cost of object serialization (of the entire Rete)? Thanks
very much,
Jonathan Sewall
--------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the list
(use your own address!) List problems? Notify [EMAIL PROTECTED]
--------------------------------------------------------------------
