Thanks, Edson, Mark, for such a quick reply.
Mark, I'm not sure why you are saying that creating rules programmatically
would be too complex for users? Maybe by 'users' we mean different things. In
my case, a user will use a UI and create rules by selecting some pre-defined
properties (like cont
Marina,
My first advise for you is to forget JSR94. It is not worth to use it.
Regarding the creation of rules via API, you can use the descriptor
classes in the package: org.drools.lang.descr.
There is not much documentation (anyone up to help on that?) but it is
easy to understand
Marina wrote:
Hello,
I am working on a project that requires a rules engine to handle numerous rules
for approval chain determination. My main choice at the moment is JBoss Rules
engine. One issue came up though that I could not find a good answer in the
documentation:
Is it possible to crea
Hello,
I am working on a project that requires a rules engine to handle numerous rules
for approval chain determination. My main choice at the moment is JBoss Rules
engine. One issue came up though that I could not find a good answer in the
documentation:
Is it possible to create rules program
Interesting. I had never tried it without the ".class" static field in
the class name. I need to investigate this a further but I think what is
happening behind the scenes is that since you are using nested accessors
(option.class), it is getting transparently re-written into an inline
eval(). T
