[
https://issues.jboss.org/browse/DROOLS-147?page=com.atlassian.jira.plugin...
]
Prashant Hariharan commented on DROOLS-147:
-------------------------------------------
Hi,thanks for the reply.
Couple of things i want to point out,
1) For the attached code which i had sent , i had already added the jBPM 5.4 dependency.
2) In the attached code i have commented the part wherein i am using knowledge builders
,knowledgepackages and stateless knowledge sessions.
The code works fine for te same scenario when i use the above mentioned classes.
The problem is with the usage of of PackageBuilders and that too in a peculiar way in
which the rule flow is called.
Initially we are calling a rule and from the rule we are invoking the rule flow using the
drools.getWorkingMemory().startProcess(<rule flow id>)
Kindly refer the drl and rf files attached.
In the above scenario the first rule is executed successfully but the execution of 2nd
rule fails(ie the call to rule flow).But the exact case works fine with the knowledge
builders.
Is it possible to provide a workaround / patch for the case to work with packagebuilders?
After upgrading the drools jars to 5.5.0 from 5.0.1 we are unable to
execute the rule flows.
--------------------------------------------------------------------------------------------
Key: DROOLS-147
URL:
https://issues.jboss.org/browse/DROOLS-147
Project: Drools
Issue Type: Component Upgrade
Security Level: Public(Everyone can see)
Affects Versions: 5.5.0.Final
Environment: Websphere application server 6.1
Reporter: Prashant Hariharan
Assignee: Mark Proctor
Attachments: rfissue.zip
After upgrading the drools jars to 5.5.0 from 5.0.1 we are unable to execute the rule
flows. The drools engine throws a null pointer exception the stackrace of which is as
follows : The stacktrace of the same can be seen below: Exception executing consequence
for rule "Initialisation For All" in
com.mastek.groupelixir.schemeuw.rules.controller: java.lang.NullPointerException at
org.drools.runtime.rule.impl.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:39)
at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1297) at
org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1221) at
org.drools.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1456) at
org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:710) at
org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:684) at
org.drools.reteoo.ReteooStatelessSession.execute(ReteooStatelessSession.java:206)
After some detailed analysis the problem seems to be with the usage of Rule
base,PacakgeBuilder and StatlessSessions as opposed to the set of
KnowledgeBaes,KowledgeBuilders and StatelessKnowledgeSessions for executing the rule
flows. The rule flow,drl and the standalone program has been attached for reference. The
problem is that the application still uses the packagebuilder and it will be difficult to
upgrade it to knowledge builders So is there any workaround for the same?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira