Personally, I never use DRL functions. I create my functions in a java class module, and
I import functions into drools. I have noticed that in earlier versions of Drools (I
don't know about recent versions), that using drl functions put a larger load on
system than using imported external functions. Plus you gain the added benefit of being
able to use your IDE's built-in debugger to step through the function logic.
From: rules-users-bounces(a)lists.jboss.org [mailto:email@example.com] On
Behalf Of ipeshev
Sent: Wednesday, January 25, 2012 10:17 PM
Subject: [rules-users] Debug rule functions ?
could some give me some tips for debugging *functions* in .drl ?
by now I'm not able to debug *inside the functions* which are called by the
I follow the
JBoss Drools Tools Reference Guide but what is show there is how to debug a
very simple *rule sequence*. I have no problem with that - following the
guide everything is ok.
There is nothing shown about a more complex case when there are functions
(java-like) in the .drl file and the rule calls one or more of these
functions. And one function calls another etc. (just like in normal
When a put a breakpoint inside functions I cannot debug them.
I can only debug the *rule* ("then" section)
Any help would be appreciated?
Or any official info if this supported at all.
View this message in context:
Sent from the Drools: User forum mailing list archive at Nabble.com
rules-users mailing list