The KieContainer is a container for the JAR + transitive reps. Think of it as how you mount your JAR, and how you access the defined kbases and ksessions in that JAR. So if you deploy a JAR, you access it via the KieContainer. One JAR == One KieContainer. The KieContainer provides the the root class path for all the JAR classes + transitive dependencies classes.

On 1 Jul 2013, at 13:21, Charles Moulliard <> wrote:


I have questions about kcontainer & kbase. Do we have to create a container to manage the kbases and ksessions ? What is the goal of the kcontainer ? Can we define kcontainer, kbase and ksession in kmodules files or only ksessions ? Is there a document describing that or web page ?


Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog :

rules-dev mailing list