What makes you think that using entry points "speeds things up"? The
Engine still has to evaluate the entry-point attribute of a fact (handle),
just like any other attribute.
Or do you have conclusive evidence based on solid benchmarks?
-W
On 10/12/2013, dunnlow <dunnlow(a)yahoo.com> wrote:
I am sending events to drools integration server (5.5). I have a
good
number
of rules so I am looking at using entry points to speed things up. My
client app will send to an entry point based on the value of one of the
event attributes. While I will typically know all possible attributes, I
may occasionally get an event that has an attribute value that I have 1)
not
foreseen, and/or 2) don't need any rules for. Whenever I insert an event
to
an endpoint however for which I have no rules, I get a nullpointerexception
from the drools server.
Is there a way to handle this? I am considering having my client app do a
lookup in the ksession (which is persisted to a db) to determine all of the
entry points and then, if the event attribute received isn't one of them,
send to the DEFAULT entry point. Is there an easier way?
Here's a sample use case: I have am receiving events based on automobile
models. I have rules for Ford models at the Ford entry point and Honda
models at the Honda entry point. I don't care about a car if it's a
Toyota,
so I have no rules (/entry points) for them. However, all events go to the
rule engine. If I send the Toyota event to the drools server, I get an
internal server error from the drools server.
Any thoughts?
Thank you,
-J
--
View this message in context:
http://drools.46999.n3.nabble.com/Insert-to-non-existing-entry-point-caus...
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