PseudoClockScheduler clock;
private void advance( Date eventDate ){
long currentTime = clock.getCurrentTime();
long eventTime = eventDate.getTime();
clock.advanceTime( eventTime - currentTime, TimeUnit.MILLISECONDS );
}
This simple but great piece of
The question is more or less where to begin.
1. If there is a Fact in working memory (e.g. Person) and I invoke
fireAllRules() twice, I would expect to have the following rule fire both times:
rule alwaysFire
when
$room : Room( )
then
System.out.println(there is a room);
end
I
1. A fact doesn't change until it *is* changed or the knowledge base
destined to operate it changes: so why should reasoning due to
the unchanged fact be repeated, with all consequential actions.
Continuing your line of thought would result in a hopeless muddle
if all consequences are re-executed
I got the following scenario:
- I need a Web Service that reasons over received sensor events (1000+ per
day and client) in realtime and send messages if certain patterns occur.
- The web service has many clients (100-1000) but their events / facts do
not interfere (each client has his own state
What did not happen as you expected?
The HTTP session to Knowledge session association seems reasonable; but I
assume you are trying with a more simple configuration initially.
Sent on the move
On 8 Sep 2013 17:42, amarok m...@alexander-wolf.net wrote:
I got the following scenario:
- I need a
