Input are placed in working memory and then remove Output are disregarded code
Using per process instance as runtime strategy, you will find the same kiesession through all the interaction with the process. This will ensure that the working memory follow the process instance life cycle. The working memory is saved and survive the server restart.
-
Define the Knowledge base
<kbase name="drlRules" equalsBehavior="equality" eventProcessingMode="cloud" default="true"> <ksession name="ksessionDrlRules" default="true" type="stateful" clockType="realtime" /> </kbase>
Some important dependencies:
<dependency>
<groupId>org.kie</groupId>
<artifactId>kie-api</artifactId>
</dependency>
<dependency>
<groupId>org.drools</groupId>
<artifactId>drools-decisiontables</artifactId>
</dependency>
<dependency>
<groupId>org.drools</groupId>
<artifactId>drools-core</artifactId>
</dependency>
<dependency>
<groupId>org.drools</groupId>
<artifactId>drools-workbench-models-guided-dtable</artifactId>
</dependency>