...
The paren and attribute evaluators each log an entry as they enter the isApplicable method and as they exit. When exiting they indicate if the result was true or false. The nesting is part of the logging and serves to help see the nesting of the evaluator hierarchy built up based on configuration found in the Sample dlm.xml file page.
For example, the Student fragment is configured with this element in dlm.xml
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
<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>
|
From the logs 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.
...