[
http://jira.jboss.com/jira/browse/JBSEAM-1020?page=comments#action_12355775 ]
Christian Bauer commented on JBSEAM-1020:
-----------------------------------------
Only the logger throws this exception. Otherwise you should really release an immediate
fix for this - a rules engine that confuses the types of operands? :)
So I'm just not going to use logging, from what I'm reading here it's not much
good for what I want to see anyway.
Issues with Drools debug logging
--------------------------------
Key: JBSEAM-1020
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1020
Project: JBoss Seam
Issue Type: Bug
Components: Security
Reporter: Christian Bauer
Assigned To: Shane Bryzak
Priority: Minor
I want to see what is going on when my rules are evaluated, according to the Drools docs
this is how:
workingMemory.addEventListener( new DebugWorkingMemoryEventListener() );
I have to do that in code right now, would be nice to be able to configure the identity
component externally in config file. It also doesn't work, at least not in JBoss with
a WAR deployment. I don't see any debug printed on System.out. Task: Ask the drools
guys how we get logging for Seam users.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira