[
https://issues.jboss.org/browse/DROOLS-3307?page=com.atlassian.jira.plugi...
]
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)