So it's either discard the messages with a repeated time stamp or fix
the time stamp? If you can assume a constant channel delay you can
modify the time stamp.
I'm not sure whether either one should be done by a rule in the regular
processing set - it's not really part of the fact handling logic.
It isn't duplicates but corrupted data coming off an vehicle. There is bug
in the vehicle code that isn't zeroing out memory, or updating a time value
during reset procedure which causes a bunch of facts to have the same end
time stamp. We cannot really change the vehicle code because it was
certif
Hi~
Do you have any example about using stringBuilder?
Cheers
--
View this message in context:
http://drools.46999.n3.nabble.com/How-to-create-a-drl-file-or-decision-table-dynamically-tp3772708p3774707.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_
