What's not clear :
- how to centralize the execution in order to know exactly what's executed,
by whom, and how (be able to log which facts are sent, to which rules, and
be able to read the execution plan
> centralised execution could (possibly) be achieved using
drools-server.
> WorkingMemoryEventListeners can provide a log of facts inserted - you'd
need to provide the glue for "whom"
> AgendaEventListeners can provide a log of rule activations
- if it exists a "real" stand alone centralized engine that match this need
(Drools Expert ?)
> Not Drools Expert. Drools server might be what you're after -
but I don't
know too much about it.
With kind regards,
MIke
On 14 April 2011 09:11, delirii <martindavid(a)free.fr> wrote:
A few months ago a question was asked about the difference and the
use case
involving Drools Expert and Drools Guvnor.
To be honest, it isn't clear for me too and as there wasn't any answer to
this first question, so I'm trying to have an answer with your help :)
What's clear :
- Guvnor is a repository for the assets
- The easiest (?) and certainly the mainly available as a tutorial solution
is to create in each application an agent that grabs the assets and execute
the whole thing in its own context.
What's not clear :
- how to centralize the execution in order to know exactly what's executed,
by whom, and how (be able to log which facts are sent, to which rules, and
be able to read the execution plan
- if it exists a "real" stand alone centralized engine that match this need
(Drools Expert ?)
If some can explain this a little bit more, I'll be really happy to read !
And if it can be added to the current documentation, it could be a great
idea too.
Thanks for your help.
--
View this message in context:
http://drools.46999.n3.nabble.com/Expert-versus-Expert-tp1739141p2819515....
Sent from the Drools: User forum mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users