I wonder if OP Soumya solved the issue, because at least in my case it is
indeed working fine - I just tested with 610Final as we also wanted to log
from rule via slf4j.
I attach demo that at least for us proves working.
I've also tried back-port the same project attached to test with 610beta2,
a
> @Soumya: Which Drools version are you using? Basically, this situation
> is handled correctly by 5.4 and 5.5.
We are using Drools version 6.1.0.Beta2.
--
View this message in context:
http://drools.46999.n3.nabble.com/Slf4j-Log4j-logger-not-working-with-Drools-6-1-0-Beta2-drl-while-using-as
> Check if the logger isn't null (by adding a System.out in the then part
> of the rule).
We checked, logger is not null here.
--
View this message in context:
http://drools.46999.n3.nabble.com/Slf4j-Log4j-logger-not-working-with-Drools-6-1-0-Beta2-drl-while-using-as-a-global-variable-tp40297
@Geoffrey: did you see the java.lang.ArrayIndexOutOfBoundsException?
Doesn't look like a null pointer causing an exception. The upstairs
exception might add the basic exceptions's message to its message.
@Soumya: Which Drools version are you using? Basically, this situation
is handled correctly by
Check if the logger isn't null (by adding a System.out in the then part
of the rule).
If that's the case, then that error message is pretty poor (or even
incorrect):
java.lang.RuntimeException: cannot invoke method: info
It should clearly talk about a NullPointer instead.
So, if that's the c
I am using global slf4j log4j logger as a global variable within our drl and
inserting that global logger value at runtime into kiesession. While we are
trying to do logger.info with multiple arguments then it's giving the
following exception stack trace -
Exception executing consequence for rule
