Filtering and identifiers and logging.

[Cantor, Scott]

On 6/20/13 11:52 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:

>Again the plan is to port this unchanged, but it will have a side effect
>on
>the logging because if someone specifies a rule called "MyAndRule" the
>message logged might be something more like:
>
>Attribute Filter
>'/AttributeFilterPolicyGroup:PolicyExample3/PolicyRequirementRule:
>MyAndRule' Some useful message.

Hmm, I don't really recall all that, so I don't know what the purpose was.
I guess he didn't just use IDREF and link things by IDs directly?

>On the one hand having the qualified name is useful in really locating the
>precise matcher, on the other hand the log line becomes quite long.

I think the stack traces are a lot more obnoxious, and honestly it's for
occasional debugging, not routine logging anyway.

>Because a lot of logging goes through getLogPrefix() changing this to
>strip
>off everything to the left of the right-hand-most ':' would be quite easy,
>but would it add or subtract from the logged message?

That depends on the relevance of the information. If the final atom has to
be unique anyway, it probably doesn't add much to have the rest.

-- Scott