Transaction Controller <Transaction Controller>
Business logic:
The controller in the control and no special business logic, can be understood as a statistical added functionality on the basis of a simple controller.
Transaction execution logic controller does not generate its child nodes affected, the effect is generated when the monitored statistics in order to separate a statistical point count, the indicators may be indicator of the controller and the child node.
When the execution result fails, the transaction controller of any child nodes under a transaction controller will be counted in failure.
Generate parent sample <generate the parent sample>:
Check to see the results tree will monitor the results of the transaction controller and its child nodes merge the current display, click on the + to expand the view statistics details; polymerization will report on the results of the current transaction controller statistics, which are not recorded separately statistical results for each child node.
Unchecked, monitor the results of the current transaction will see the results tree controller and its child nodes independent display, and the results can not be a collection. The results of the controller is the result of the child nodes and; polymerization will report on the current transaction controller and its child nodes are statistical results.
Include duration of timer and pre-post processors in generated sample <statistics include a timer and a post-processor execution time>:
When unchecked, the result listener controller statistics only count the execution time of its child nodes, timer and postprocessors are not counted
When checked this time, the result listener statistics on the controller, it will self-timer child nodes, the response time of postprocessors are included in the statistics
Demo script: Demo_ Transaction Controller