Mark, Kris, Thanks for the replies.
1) Yes kris is still working on the decision stuff for ruleflow.
>Some of
the stuff is already partially implemented, but an (X)OR split (where
you
can define which path(s) to follow based on some conditions) is still
on
the TODO list.
I look forward to trying out the XOR decision node stuff. By the looks of
the code in the trunk, the core stuff isn't to far for completion.
2) A rule currently can only belong to one ruleflow-group, but a
ruleflow-group
can belong to multiple ruleflows ...
Reuse of ruleflow-groups is a good start, but allowing rules to belong to
more than one group is definitely worth considering at some point. I may
just give this a go and see what it looks like:) What I've found is that
when you use a decent BRMS (like the new BRMS in JBoss Rules) and have all
your rules in one place, then the potential for reuse really starts to
become apparent.
Incidentally, is there any merit to adding ruleflow management into the
BRMS, if only to allow them to be versioned and added to the repository.
Perhaps they could be an additional element to a package (i.e like Business
rules, models etc.). I can see that defining ruleflows is probably not
something that could be done easily (if at all) in the BRMS web app itself.
3) The Eclipse GUI ruleflow builder doesn't seem to allow loops in
the
flow.
It does support the creation of loops: create an XOR split as the
starting
point
of your loop, you can then always create nodes that link back to this
starting point, resulting in a loop...
Kris, I assume you meant create an XOR Join (not Split) as the starting
point of the loop, in which case I can see how that would work - thanks.
Regards
Shahad
On 5/14/07, Kris Verlaenen <kris.verlaenen(a)cs.kuleuven.be> wrote:
> 1) Yes kris is still working on the decision stuff for ruleflow.
Some of the stuff is already partially implemented, but an (X)OR split
(where you can define which path(s) to follow based on some conditions) is
still on the TODO list.
> 3) The Eclipse GUI ruleflow builder doesn't seem to allow loops in the
flow.
It does support the creation of loops: create an XOR split as the starting
point of your loop, you can then always create nodes that link back to this
starting point, resulting in a loop. Note that looping kind of depends on
the (X)OR split as well, as that would allow you to exit the loop in
specific conditions (now you will probably create an endless loop). I hope
I'll be able to add that piece of functionality pretty soon to trunk.
Kris
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users