Hi Mark,
 
The part in the document where it says:

"At this point, ruleflow-groups should not be reused in more than one ruleflow, and you should not

start a new instance of a process before the previous one has ended."

will be the weak link in the chain, i.e. there should not be any reason why rule-flow-groups should not be reused nor having multiple instances since rules are implicitly parallel in operation. This was what I found to be the problem with ILOG's JRules back in the v4.0 edition. It turned JRules into a clunky procedural processing engine (which was not what we needed at that time).

However, I am very proud to see that Jboss Rules (JBRules) has successfully evolved to this point. You (and your team) are to be commended for your efforts.

Tally-ho !!

Rich Halsey

 

 

 

 
 
 
"GENIUS IS THE ULTIMATE WEAPON"
 
....God grant me...
The senility to forget the people I never liked
The good fortune to run into the ones that I do
And the eyesight to tell the difference."
----- Original Message -----
From: Mark Proctor
To: Rules Dev List
Sent: Monday, February 26, 2007 5:12 AM
Subject: RuleFlow preview

I thought everyone on the dev list would be interested in reviewing and providing feedback on Kris' excellent work on RuleFlow - includes screenshots :)

Mark
-------- Original Message --------
Date: Mon, 26 Feb 2007 01:51:29 +0100
From: Kris Verlaenen <kris.verlaenen@gmail.com>
Subject: Ruleflow


I've attached a document describing how ruleflow is implemented /
could be used in the future.  If anyone has got any suggestions or
improvements (on the API I'm proposing, or things you would like to
see differently), just let me know asap.

I think I'll be able to commit a first working version on svn soon.
Still have to include conditional connections (where a connection is
only selected if its condition evaluates to true), and some smaller
stuff.

Kris