> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of David
> Jencks
> Sent: 25 April 2001 04:20
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] Rule Engine Improvements
>
>
> Hi,
>
> Jeops _is_ a freely available RETE based rule engine. It is unusual in
> that it operates on java objects rather than data tuples.
Isn't JEOPS a kind of codegen/compiler that build an inference engine for a
specified set of rules as opposed to an engine that can be given a set of
rules in a text file for example?
- How does this affect the modification of rules in a system?
- Will anything break when rules change and the engine is regenerated and,
how can this be automated for use by non-programmers?
- How does such an architecture affect the resource requirements for the
[all the] inference engine instances? By this I mean that since we can
expect a number of rulesets that deal with "areas" of functionality (perhaps
on a high-level usecase basis), how does the fact that JEOPS creates
essentially independent, hardcoded, unreusable engine instances affect the
resources used compared to say JESS where one could keep a pool of instances
and (re)load different rulesets from a text file as needed?
You are saying that the generated inference engine(s) are based on the Rete
algorithm?
> I would really like some information about what the community
> process group
> is thinking of in terms of rule engine activation. I like what I came up
> with, which is essentially before and after triggers on ejb method
> invocations. If they have a really different idea I'd like to know about
> it.
Anyone have any idea what's cooking in the community process?
Micheal
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
