...
The fragment being evaluated is identified by an entry formated like >>>> calling <fragmentName>.isApplicable( <userLoginID> ).
having that fragment name followed by a representation of the syntax of the "isApplicable" method call. So the test of the Student fragment starts on line 3 and returns on line 13 showing that it was not applicable to user mboyd. Now remember that fragments can have zero to many audience evaluators. So the first nested evaluator that is called for any fragmentFrom the log entries below you can see the evaluation of the top level "OR" paren and its nested "AND" paren s it can be seen that the mboyd user is a faculty member and hence is elligible for the Faculty fragmentfragment is an OR paren. Within that evaluator you then begin to see the evaluators reflected by the configuration above. The AND paren is entered followed by the attribute evaluator that compares all roles held by mboyd to the role of student and finds that none match. Hence it then exits with a value of false causing the AND paren and OR parens to do likewise. Only the Faculty fragment is found to be applicable to user mboyd.
Note that the leading timestamp, class, lines, etc., have been removed for brevity.
...