Drools 5.0 solves this much more elegantly, via the CommandExecutor,
which even has built in xml marshalling for remote services. You can see
all the command we impl in the unit test here:
http://fisheye.jboss.org/browse/JBossRules/trunk/drools-pipeline/drools-transformer-xstream/src/test/java/
you can start a process from a rule consequence like this:
drools.getKnowledgeRuntime().startProcess("com.sample.MyProcess");
https://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/docs/drools-flow/html/ch03.html#d0e237
On Mon, Jun 16, 2008 at 1:50 PM, Yoni Mazar
Yoni,
The way I do this is within the ruleset. I have an initialization rule
that looks something like this:
when
then
drools.getWorkingMemory().startProcess("ruleflow id");
end
By not putting anything in the "when" clause, the rule gets activated
and put on the agenda first.
Dan
=
Somewhat better than my reply, now where was that stone I crawled from
under? ;-)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kris Verlaenen
Sent: 26 June 2008 15:49
To: Rules Users List
Subject: Re: [rules-users] Stateless session and rule flows
Hi,
I believe Stateless session is only a wrapper around a stateful session, so
you're only gaining convenience by using a Stateless one.
Why not write your own wrapper that allows for the execution of a rule flow
too?
Cheers,
Mike
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EM
Use a rule (probably without conditions and high salience) to start your
ruleflow:
rule "Start Process" salience 10
when
then
drools.getWorkingMemory().startProcess("yourName");
end
Kris
- Original Message -
From: "Yoni Mazar" <[EMAIL PROTECTED]>
To:
Sent: Thursday, June 26
