[jboss-jira] [JBoss JIRA] (DROOLS-1327) Drools declared types cannot be references in jBPM Drools expressions due to compilation order.

Duncan Doyle (JIRA) issues at jboss.org
Fri Oct 14 03:54:00 EDT 2016


    [ https://issues.jboss.org/browse/DROOLS-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13306990#comment-13306990 ] 

Duncan Doyle commented on DROOLS-1327:
--------------------------------------

And the PR with the unit-test in jBPM: https://github.com/droolsjbpm/jbpm/pull/636

> Drools declared types cannot be references in jBPM Drools expressions due to compilation order.
> -----------------------------------------------------------------------------------------------
>
>                 Key: DROOLS-1327
>                 URL: https://issues.jboss.org/browse/DROOLS-1327
>             Project: Drools
>          Issue Type: Bug
>          Components: core engine
>    Affects Versions: 6.4.0.Final
>         Environment: JBoss BPM Suite 6.3.3.GA
>            Reporter: Duncan Doyle
>            Assignee: Duncan Doyle
>
> When you declare a type in a DRL using the "declare" syntax, that type cannot be referenced by Drools LHS expressions in a Sequence Flow (for example in the context of an X-OR Gateway). The DRL and BPMN2 file are in the same project.
> The problem is the order of compilation of CompositeKnowledgeBuilderImpl. The builder compiles the process definitions before the DRLs, which results in a situation where the declared types used in the process are not yet available in the Drools ProjectClassloader when. the process is compiled.
> Easy fix is to compile the process after the rules, which makes sense as the rules will normally not really on processes, but processes can really on rules.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jboss-jira mailing list