Hi Paul,
I have to agree with everyone here. I've enjoyed working with Jess since
about version 2.0, and have been actively supporting it since 6.0 onward.
Ease of use, stability, and robustness have been its hallmarks. Don't let
the LISP syntax of the Jess language dissuade you. Once you do a
I have been waiting a LONG time for someone besides me to ask this question.
Can't wait to hear the answer ;-)
On Tue, May 31, 2011 at 5:35 PM, Paul Gifford pggiff...@gmail.com wrote:
Hi,
We're looking at a couple of Java rules engines, Jess among them. It's
been a couple of years since
Jess in Action is still valid; there are some newer features since
then, and some newer best practices, but nothing in the book is
*wrong*. The release notes in the Jess 7.0 manual explicitly address
the 6.x - 7.x transition and things that you might want to change, so
they serve as a nice
I’m using Jess on a large DARPA project, and I find it to be a mature and
stable platform. The mailing list goes quiet but responds quickly when people
ask questions. The Jess language is a subset of LISP, which is an obvious
touchpoint for religious debates, so if you’re looking for a “reason”
Great, thank you!
On Tue, May 31, 2011 at 8:20 PM, Ernest Friedman-Hill ejfr...@sandia.govwrote:
Jess in Action is still valid; there are some newer features since then,
and some newer best practices, but nothing in the book is *wrong*. The
release notes in the Jess 7.0 manual explicitly
Hi Paul,
We have two applications that are deployed operationally. One is a real time
data driven decision support system processing health data. Its been in
operation for two years, running non-stop without an error. The second is an
operational app that provides risk assessment for