Better Policy Evaluation Logging

[GoogleCodeExporter]

This is a low priority enhancement (thanks for looking into the other
issues!), but it would be nice to have some better logging of policy
evaluation, and maybe even a way to access evaluation information
programmatically. I would especially like to know what rule was matched for
each decision, but it would also be nice to know what operands are being
passed into what functions, etc., to allow for debugging of the XML
policies themselves.

Original issue reported on code.google.com by kenny.pe...@hxti.com on 8 May 2008 at 4:08

[GoogleCodeExporter]

Yes, it should be a nice enhancement, I will think about how to implement such a
mechanism. I would like to first add such information to debug log, and then 
try to
implement a programmatic way.

Original comment by ppz...@gmail.com on 9 May 2008 at 3:40

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

The attached patch adds some TRACE-level logging of policy evaluation. There is 
lots
of room for improvement - I just did what I needed at the moment - but it was 
useful
for me. It also fixes issue 52.

Original comment by kenny.pe...@hxti.com on 9 May 2008 at 3:11

Attachments:

• logging-patch.txt