Thanks Mark, very helpful.
I'm about to set up a Proof of concept so I'll try it out. Due to the
relatively complex nature of our ruleflows and the fact that many rules can
be used by many transaction types Drools Flow sounds like it will have to be
the way to go. I'm out about to dig out the
I Just need clarification on the injection of POJOs to give access to
application services etc...
I understand the fact that POJOs inserted into the working memory are direct
references to the actual objects inserted by the calling application, that's
great. However, currently in Jrules (sorry
Hi Chaps,
We currently use Jrules 5 and are looking at our options going forward. We
are going to evaluate Drools alongside some other products. So far I like
the look of Drools but there are a couple of things that are puzzling me...
- In our Jrules implementation our BOM/XOM exposes some of
