I think James Gallogly wrote: > > My goal is to serialize the Rete. I am definstanceing a Fact based off of a > non-serializble object, doing a bunch of stuff, then undefinstancing the > non-serializble objects Fact just before Serializing the Rete. I get an > exception thrown saying it was unable to Serialize the non-serializable > object. This implies that somehow a reference to this retracted fact is > hanging around in the Rete and is attempting to be serialized. >
Thanks for the report; see below: And I also think Alan Moore wrote: > I don't know if there is a problem beyond what is described in > Ernest's earlier post but this should clear some things up for you (I > am including the post here since I couldn't find a link to it in the > archives... go figure): Good call Alan; this is almost certainly the cause of Mr. Gallogly's problem. I should be able to fix this for 6.1a3, which shouldn't be too far in the future. One way to fix it without disturbing anything at runtime would be to add an Agenda.writeObject() which removed any deactivated Activation objects. --------------------------------------------------------- Ernest Friedman-Hill Distributed Systems Research Phone: (925) 294-2154 Sandia National Labs FAX: (925) 294-2234 Org. 8920, MS 9012 [EMAIL PROTECTED] PO Box 969 http://herzberg.ca.sandia.gov Livermore, CA 94550 -------------------------------------------------------------------- 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] --------------------------------------------------------------------
