You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At present kogito is based on the premise of a combination of code
generation based on a fluent interface. Nothing at kogito level uses
these parts of KieAssemblerService anymore.
This is causing not moving those test/guards for the functionality in
the new infrastructure causing a few problems:
Functionality loss because those tests are not using the new
infrastructure of fluent interface and code generation.
Create the illusion that those tests are of any use for the current
system and make the system weaker
making the functionality gaps less visible.
The proposal would do:
remove the assembler services and relieve drools from the use of
that infrastructure
remove the old runtime that is only useful for these tests.
This should lead to:
focus only in the fluent interface and codegen
remove unused parts and make the system leaner
identify all the missing parts at level functionality to reduce the gaps
increase the level of guards at codegen level and fluent interface.
elguardian
changed the title
Drop legacy runtime and KieAssemblerService Drools integration
EPIC - Drop legacy runtime and KieAssemblerService Drools integration
Apr 30, 2024
Removing DROOLS jBPM Integration.pdf
At present kogito is based on the premise of a combination of code
generation based on a fluent interface. Nothing at kogito level uses
these parts of KieAssemblerService anymore.
This is causing not moving those test/guards for the functionality in
the new infrastructure causing a few problems:
infrastructure of fluent interface and code generation.
system and make the system weaker
The proposal would do:
that infrastructure
This should lead to:
Test consolidation
v7 features migration
The text was updated successfully, but these errors were encountered: