Why store serialised kiebases? Is it really that expensive to consume a kjar? As long as
you build with drools maven plugin, it should have a lot of aspects pre-ompiled now.
Our incremental “diff” will take care of static and dynamic aspects, if you always build
and deploy new jars, using the drools maven plugin.
Mark
On 22 Jan 2014, at 14:54, Soumya.plavaga <soumya.bose(a)plavaga.in> wrote:
We have two set of rules. Some of them are static. Some of them
changes
frequently. We need to find a way to keep the pre-compiled version of those
rules into filesystem and import them into knowledge base at run time. So
that over all performance to prepare the knowledge base will minimize.
I am trying the following approach with drools 6.0.1 -
Having two drools project say A & B. Both having 1 drl. I have stored the
serialized version of kiebases for project A & B in two different fiile
systems say a.txt & b.txt. Now at the run time I am De-serializing the
kiebases from the above text files and getting two kieBase objects. Now if I
need to include both the kiebases at run time to fire all the rules within
project A & project B what I need to do? Any help will be really
appreciated.
--
View this message in context:
http://drools.46999.n3.nabble.com/Need-a-way-to-import-multiple-pre-compi...
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