[
https://issues.redhat.com/browse/DROOLS-6030?page=com.atlassian.jira.plug...
]
Gabriele Cardosi commented on DROOLS-6030:
------------------------------------------
[~mfusco]
After some analysis, it seems point 1) above seems the best course of action.
This would anyway require a series of preparatory step
1) unify rule codegen in one single place: currently is is almost duplicated in Kogito
(PredictionCodegen) and maven plugin (GeneratePMMLModelMojo)
([
DROOLS-5702|https://issues.redhat.com/browse/DROOLS-5702])
2) automatically generate kmodule with required kiebase definitions )
([
DROOLS-6038|https://issues.redhat.com/browse/DROOLS-6038])
3) change the kiebase naming logic: currently it is the (cleaned) model name, but to avoid
eventual name clash with kiebases defined by final user, the hash of such name will be
used ([
DROOLS-6039|https://issues.redhat.com/browse/DROOLS-6039])
Evaluate "KieBase.addPackage" replacement effort from PMML
----------------------------------------------------------
Key: DROOLS-6030
URL:
https://issues.redhat.com/browse/DROOLS-6030
Project: Drools
Issue Type: Task
Reporter: Gabriele Cardosi
Assignee: Gabriele Cardosi
Priority: Major
Currently, the method KieBase.addPackage(s) is used inside PMML in two classes
1) PMMLLoaderService.loadPMMLRuleMappers
2) PMMLRuntimeFactoryInternal.getPMMLRuntime(String, String, KieBase)
3) PMMLRuntimeFactoryInternal.createKieBase(KnowledgeBuilderImpl)
In all those cases the needs is to create a "clean" kiebase that contains only
the model-specific packages, to avoid name/session clashing.
Scope of the current ticket is to evaluate an alternative, since the method itself is
going to be deprecated.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)