Mark Proctor wrote:
Umesh Wankhede wrote:
Mark Proctor wrote:
Umesh Wankhede wrote:
Hi
I am trying to evaluate various features (rules and workflow) of
Drools 5.0. What I understand from docs (drools-docs-flow.pdf -
page 5) is that the Drools flow engine is based on generic process
eng
David Boaz wrote:
Your answer refered to Statefull session. My question was regarding a
stateless session, that do not extend WorkingMemory.
you are using an event, that event exposes the knowledgeruntime in the
event listener - stateless and stateful use the same event model and
both expose
Umesh Wankhede wrote:
Mark Proctor wrote:
Umesh Wankhede wrote:
Hi
I am trying to evaluate various features (rules and workflow) of
Drools 5.0. What I understand from docs (drools-docs-flow.pdf - page
5) is that the Drools flow engine is based on generic process engine
that allows the exe
Your answer refered to Statefull session. My question was regarding a
stateless session, that do not extend WorkingMemory.
Currently, I did an ugly work-around. The Activation returns a
Collection, and I noticed that in runtime, the FactHandle is
instanceof InternalFactHandle, that do have a getOb
Mark Proctor wrote:
Umesh Wankhede wrote:
Hi
I am trying to evaluate various features (rules and workflow) of
Drools 5.0. What I understand from docs (drools-docs-flow.pdf - page
5) is that the Drools flow engine is based on generic process engine
that allows the execution of different pro
Anyone give me a better explanation of the differences between these two
joins node types? Per the documentation
*XOR means that it continues if one of its incoming branches has been
completed.
**Discriminator means that it continues if one of its incoming branches has
been completed. *
Reading
David Boaz wrote:
Thanks Mark,
The post bellow doesn't deal with the event listener registration. Assuming
the registration was solved, now I have another issue. How to retrieve the
Facts given Fact-handles? In a stateless session, I have no access to the
working memory.
If you are using Sta
Umesh Wankhede wrote:
Hi
I am trying to evaluate various features (rules and workflow) of
Drools 5.0. What I understand from docs (drools-docs-flow.pdf - page
5) is that the Drools flow engine is based on generic process engine
that allows the execution of different process languages like
Ru
Hi
I am trying to evaluate various features (rules and workflow) of Drools
5.0. What I understand from docs (drools-docs-flow.pdf - page 5) is that
the Drools flow engine is based on generic process engine that allows
the execution of different process languages like RuleFlow, BPEL,
OSWorkflo
Thanks Mark,
The post bellow doesn't deal with the event listener registration. Assuming
the registration was solved, now I have another issue. How to retrieve the
Facts given Fact-handles? In a stateless session, I have no access to the
working memory.
David
Mark Proctor wrote:
>
> David Boa
10 matches
Mail list logo