Its definitely up for considation, I just don't want to rush it as there
are several ways to do this. I already have to dothe abomination "named
facts" for 3.1; so users can seamlessly share variable contexts across
applications - this is for jBPM and Seam integration, where they need to
know that variable "a" in jBPM is "a" in Drools - although they atleast
think they need that.
Mark
Geoffrey Wiseman wrote:
On 4/11/06, Mark Proctor <[EMAIL PROTECTED]> wrote:
Unfortunately I'm finding that many people just cannot adjust to the
declarative and coupletely decoupled nature of a rule engine. The end
result is that Drools is used as a script execution framework.
Personally, I'm with many of the commenters here -- I think 'else' isn't
really in the spirit of Drools.
That said, I think a lot of people do think that way, and if Drools supports
this model, it'll be more accessible, and possibly increase the adoption
rate, which has some value.
So ... I can see the benefits of both, although if I were going to vote, I'd
vote for "No else".
--
Geoffrey Wiseman
