A new configuration and convention method to developing knowledge bases is introduced in version 6.0.
Building now makes use of Maven and follows Maven guidelines. Simply said, a KIE project or module
a Maven Java project or module, with the META-INF/kmodule.xml file serving as additional metadata. The
The descriptor that chooses and configures resources for knowledge bases is the kmodule.xml file.
those sessions and knowledge bases. Additional XML support is provided by OSGi and Spring.
KIE resources can be built and packaged using regular Maven, but validation at
build period To obtain build time validation, it is advised to use a Maven plugin. The
The screenshot shows the Maven POM descriptor and an example project layout.
To reduce the amount of settings, KIE employs defaults. Having an empty kmodule.xml
the most basic set up. A kmodule.xml file is required at all times, even if it is empty.
A KieModule can be installed by Maven with the command “mvn install” on the local system, where all other
It is used by local machine programs. Alternatively,’mvn deploy’ can be used to push the KieModule to a
remote repository for Maven. When the application is built, the KieModule will be retrieved and filled with data.
There are two ways to deploy JARs. either added, like any other JAR, to the classpath
They can either be dynamically loaded at runtime or listed in a Maven dependency listing. Using KIE, the
to search the classpath for all JARs that contain a kmodule.xml file. The discovered JARs are each represented by a
interface for KieModule. Classpath KieModule and dynamic KieModule are keywords that are used to describe the
two methods of loading Classpath does not support side-by-side versioning while dynamic modules do.
modules fail to. Additionally, no additional versions of a module may be loaded once it is on the classpath.
The following sections contain comprehensive API references; the impatient may skip through to those.
right to the examples section, which covers the various use cases in fairly self-explanatory detail.
Creating and building a Kie Project
With the exception of one oddity, a Kie Project has the same structure as a typical Maven project.
the Maven project’s resources/META-INF folder, and all the other Kie artifacts, such as
It is required to keep DRL or Excel files in the resources folder or any other subfolder under it.
Since there are meaningful defaults for every area of setting, the most basic
A kmodule.xml file may only have an empty kmodule tag, such as this: