Page Comparison

...

#  <dlm:fragment name='Students' ownerID='student-lo' precedence='100'>
#   <dlm:role>student</dlm:role>
   <dlm:audience evaluatorFactory='com.pipeline.uportal.dlm.provider.CPPersonEvaluatorFactory'>
     <paren mode="AND">     
       <attribute name='role' mode='equals' value='student'/>
       <paren mode="NOT">
         <attribute name='role' mode='equals' value='faculty'/>
       </paren>
     </paren>
   </dlm:audience>
 </dlm:fragment>

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. 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 fragment.

...