Red Hat Bugzilla – Bug 1276379
kie-camel does not load rules when installed in JBoss EAP Module
Last modified: 2016-10-14 10:12:17 EDT
Description of problem:
when kie-camel and other necessary dependencies are installed in JBoss EAP Module, they are not loading the rules bundled in *.war app deployed on the same EAP instance.
Version-Release number of selected component (if applicable):
BPM Suite 6.1
JBoss EAP 6.4
Steps to Reproduce:
1) Unzip third-party-modules.zip to your favorite location (let's say /tmp/modules).
2) Unzip the sample-kie-service.tgz to another location and compile it using a simple 'mvn install'
I have added these two repositories to my settings.xml in order to successfully build this project:
3) copy the compiled sample-kie-service.war from the target folder to your eap6 deploy directory
4) start jboss using the standalone.sh script, and specifying the extra modules folder. I use the following command:
$ cd jboss-eap-6/bin
$ JBOSS_MODULEPATH=../modules:/tmp/modules ./standalone.sh
5) in server.log, you should see the timer ticking, but not the message from the rule1.drl file:
[route2] (Camel (camel) thread #0 - timer://mytimer) Rule Execution
6) You can also see the message "No files found for KieBase kbase1" in server.log.
Rule files bundled in a *.war are NOT loaded
Rule file bundled in a *.war are loaded
This is my *.war structure during the tests:
If I remove the provided scope of kie-camel in pom.xml and bundles everything within the *.war under web-inf/lib so my WAR structure looks like this:
Then the kie-camel loads the rule, and the camel routes executes the rule as expected.
At first I thought this may be related to
but I'd like to request technical verification, whether this is not issue within our code..
Created attachment 1087582 [details]
 Samel camel app - *.war
I fixed this issue with the following 2 commits:
However also with this 2 fixes in place the provided test case was not working because the attached kie module missed antlr and ecj among their dependencies. I manually added these dependencies to the module and this definitively fixed the problem.
Roger, since you are investigating the reason of the missing dependencies, can you please add your findings here?