[jboss-jira] [JBoss JIRA] (DROOLS-3307) Refactor jBPM out of Drools core
Edoardo Vacchi (Jira)
issues at jboss.org
Mon Nov 26 09:49:00 EST 2018
[ https://issues.jboss.org/browse/DROOLS-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edoardo Vacchi updated DROOLS-3307:
-----------------------------------
Description:
Use the Assembler/Weaver mechanism to move jBPM out of drools core
other notes:
current impl exposes both drools-specific and jbpm-specific methods
core should not account for the underlying type: we'd rather give a wrapper or a common super-type instead of a different map for rules and processes.
aim for API like:
{code} kpg.get(Rules.class).getRules() {code}
was:
current impl exposes both drools-specific and jbpm-specific methods
core should not account for the underlying type: we'd rather give a wrapper or a common super-type instead of a different map for rules and processes.
aim for API like:
{code} kpg.get(Rules.class).getRules() {code}
Summary: Refactor jBPM out of Drools core (was: Make KnowledgePackage agnostic to Drools/jBPM)
> Refactor jBPM out of Drools core
> --------------------------------
>
> Key: DROOLS-3307
> URL: https://issues.jboss.org/browse/DROOLS-3307
> Project: Drools
> Issue Type: Enhancement
> Reporter: Edoardo Vacchi
> Assignee: Edoardo Vacchi
> Priority: Major
> Labels: drools-core
>
> Use the Assembler/Weaver mechanism to move jBPM out of drools core
> other notes:
> current impl exposes both drools-specific and jbpm-specific methods
> core should not account for the underlying type: we'd rather give a wrapper or a common super-type instead of a different map for rules and processes.
> aim for API like:
> {code} kpg.get(Rules.class).getRules() {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the jboss-jira
mailing list