Can anyone tell me what's wrong with this wait state constraint?
System.currentTimeMillis() = (startWait + 3000)
The exception I'm getting ist:
[5,33]: [ERR 102] Line 5:33 mismatched input '=' expecting 'then' in rule
RuleFlow-Milestone-drools.test.timer-6
but I don't think that is really getting
what are the condition from both rules?
Can you share with us your processes definitions? did you check the process
ids?
Greetings
2010/7/22 santosh mukherjee sam.sensat...@gmail.com
Hi,
My rule file is like this:
rule1:
when something
then
start process(p1);
rule2:
when something
Hi,
I am trying to integrate Drools with Apama. I have Apama installed and want
to pass the events mathched through Apama into Drools. Need help as to how
to proceed doing this. Basically I want that whenever a certain event
matches and is caught by Apama. I want to send it to the drl files which
Hello,
I have a problem with defining rules. I insert many, many objects (facts) to
ksession object (StatefulKnowledgeSession). I want to fire rules for
*all*of them(facts), but I want to fire only one rule from all rules
for each one
fact(not always this same rule is fired, because I use
You could always have a pool of StatefulSessions that you reuse. (This would
allow you to run concurrently in multiple threads as well.) As long as these
billions of facts don't need to interact that'll work fine. However I'd
suggest that you try the rule latch method that Thomas suggested.
Thanks for the reply.
Just for the records: Chapter 3.5 of the Drools Flow User Guide says that
there are two kinds of constraints: (a) code constraints and (b) rule
constraints, where code constraints are boolean expressions.
So wait states obviously don't support code constraints... correct?
Thanks for reacting ;)
I did some simulations, and after them, I want of course to parallelize this
process of processing 2 billions facts. But as far as I wrote, Drools
engine, can't do this. And I have to create threads manually in application
(with pool of sessions). Am I right? Tuning number
Considering that googling on rule latch will return this thread on gmane as
the 2nd link, you might find research difficult. :) I think Tom coined that
term in this context, but it fits. The basic idea is that you use an object as
an indicator of what processing has happened, and whether or
Reto,
This seems to be a conflict with similar actions in different processes
overriding each other. I'll take a look at this and try to fix it asap,
and keep you updated.
Kris
Quoting retoy reto.lampre...@allianz-suisse.ch:
Hi Kris
Here is a small project which demonstrates a similar
Hi,
Regarding the designer integration, it is probably important to know
that Oryx is still using the BPMN2 beta 1 format, while Drools Flow has
already updated to a more recent BPMN2 format. As a result, you
probably can't open the processes that are generated by the Drools Flow
graphical
Reto,
State nodes only support rule constraints. The reason is that a
constraint in a wait state should be continuously evaluated (while the
state is active), and the only way to do that efficiently is to use a
rule for that (as that is basically what a rules engine is good at).
I know the docs
Hi thanks for reply
Do I need drools server
I am mainly using drools flow
Regards
Sonu
Sent from my iPod
On 23-Jul-2010, at 9:26 AM, Mark Proctor mproc...@codehaus.org wrote:
On 23/07/2010 01:54, sonyt...@gmail.com wrote:
Hi all
I would like to integrate drools with spring
If any body have
On 23/07/2010 02:50, sonyt...@gmail.com wrote:
Hi thanks for reply
Do I need drools server
I am mainly using drools flow
drools-server uses drools-spring and drools-camel.
drools-spring can be used alone. Drools-server can just be used as an
example project to get an idea of how it works,
Hello,
After adding a few hundred rules, and with the same code, KnowledgeBase
serialization has started to generate StackOverflowError. I have increased the
VM stack size as a workaround, but I was hoping to implement something more
robust.
I specifically need to serialize the KnowledgeBase,
14 matches
Mail list logo