Adds JSP Profiling for a fragment of JSP code. The profiling will only be effective if the profiling has been enabled as described in the page developer's guide.

Profiling should be specified for any page where the request has been forwarded. Typically, this happens to be the wireframe file, which is often the outermost page in a request. The path attribute should be set in this outermost tag.

<util:profiler path="/template/ver1/wireframe/normal.jsp">
  <jsp:include ... />

For profiling fragments of a page (for example a loop, or a computationally intensive part), use the fragment attribute:

<util:profiler fragment="compute-1">
  <% new Baby(); %>

Profiling fragments can be useful to track down performance problems in a particular JSP template. It can also be used when the page contains branches (for example <util:switch> tags) where there are several distinct parts are executed independently of each other.


The fully qualified path of the current JSP template. This attribute should only be used in the outer-most profiling tag. collector.

path may not be specified if fragment is specified


An arbitrary name of a fragment of the JSP template. Fragments are typicaly used to profile portion of the JSP.

fragment may not be specified if path is specified