<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">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.<div><div><br></div><div>Mark<br><div><div>On 1 Jul 2013, at 13:21, Charles Moulliard <<a href="mailto:ch007m@gmail.com">ch007m@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi,<div><br></div><div><p class="">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 ?</p>
<div style="">Regards,</div><div style=""><br></div>-- <br><div dir="ltr"><div>Charles Moulliard</div><div>Apache Committer / Architect @RedHat</div><div>Twitter : @cmoulliard | Blog : <a href="http://cmoulliard.blogspot.com/" target="_blank">http://cmoulliard.blogspot.com</a></div>
<div><br></div></div>
</div></div>
_______________________________________________<br>rules-dev mailing list<br><a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/rules-dev</blockquote></div><br></div></div></body></html>