[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1020) Issues with Drools debug logging
[ http://jira.jboss.com/jira/browse/JBSEAM-1020?page=comments#action_12355746 ]
Michael Neale commented on JBSEAM-1020:
---------------------------------------
OK, I added sensible toString() in both 3.0.x branch (production) and trunk for these.
Yeah thats definately a bug (the exception) - its the autogenerated extractor stuff
getting confused - is there a test case in Seam for this I can look at?
I am looking at the 3.0.5 source for Drools, I have tried a few things and can't
reproduce or see why it would be using the wrong "extractor" for the Role (which
has nothing to do with User !).
The IDE has a GUI to view the logfiles in a tree view (walking back through the chain of
events) - whilst this is not immediately useful to Seam, it works by using the
WorkingMemoryFileLogger, setting afile, and max number of events in memory to flush etc...
you then open it up in the GUI and can graphically work through the sequence of events.
However, this is really only intended as a debug tool (as it slows down the engine
performance due to all the logging), but it may prove useful.
Please let me know more about the other exceptions so we can look into them.
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