Our team is developing a rule-based system, and we worked out a clp
version. After converting the clp rules into JessML format using XMLPrinter,
we found there was an exception when we used "batch" command to execute the
JessML rules. The cmd-line message is as follows:
Jess> (batch "e
Hi Erich,
First, let me mention that I'm happy to see someone using the
brand-new "static imports" feature -- the thing that lets you use
(CarClass.MINI) as a constant.
Second, your code looks fine except that the defclass defines a short
template tag RentalCarReservation, but the rules are usin
I think Wong Dong wrote:
> Our team is developing a rule-based system, and we worked out a clp
> version. After converting the clp rules into JessML format using XMLPrinter,
> we found there was an exception when we used "batch" command to execute the
> JessML rules.
Anytime the parser can'
First, let me mention that I'm happy to see someone using the
brand-new "static imports" feature -- the thing that lets you use
(CarClass.MINI) as a constant.
[alan]
Nice, this makes things a *lot* cleaner. Thanks!
Third, let me mention, as I often do on this list (I really need to
make this p
My group has been evaluating rules engines for an upcoming project.
After reading Jess In Action, we've decided that Jess is our rules
engine of choice. As we looked at various engines, we noticed that
many offerings promoted "Rules Repositories." During our evaluation
of Jess, we typically bun
I think Alan Moore wrote:
>
> > Third, let me mention, as I often do on this list (I really need to
> > make this point more strongly in the manual) that direct matching
> > should always be preferred to function calls, and anything else should
> > be preferred to the "test" CE; this is not only a
