Hello,
I have an issue with JESS where I wonder which is the best solution.
Most of my facts are Java objects, that are imported in JESS as shadow
facts. They are declared dynamic and implement PropertyChangeSupport.
They inform JESS of every single field change.
But usually I change more than one field at a time. What is the best
way to inform JESS of multiple changes?
- If I generate an events for every field change, JESS will update the
Rete network with every field change. That looks a bit overkill to me.
- If I create a kind of transaction on my objects that buffer all
changes and send the events at the end, JESS will still get individual
propertyChangeEvents and still update the Rete newtork with every
event. I guess it won't improve anything.
- If as before I create a transaction but at the end tell JESS to reload
the whole shadow fact, I will have a single update, but I will loose the
benefit of slot-specific.
So I wonder:
- Is there a way to send a propertyChangeEvent with a list of changed
fields?
- Is there a way to reload a shadow fact and ask JESS to sort out which
field has actually changed?
or more generally:
- Is there a standard way to address the question of multi-field changes
in shadow facts?
Regards,
Florian Fischer
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
