|
This interceptor logs the amount of time in milliseconds. In order for this interceptor to work properly, the
logging framework must be set to at least the
INFO level.
This interceptor relies on the
Commons Logging API to report its execution-time value.
- logLevel (optional) - what log level should we use (
trace, debug, info, warn, error, fatal )? - defaut is info
- logCategory (optional) - If provided we would use this category (eg.
com.mycompany.app ).
Default is to use com.opensymphony.xwork.interceptor.TimerInterceptor .
The parameters above enables us to log all action execution times in our own logfile.
This interceptor can be extended to provide custom message format. Users should override the
invokeUnderTiming method.
<!-- records only the action's execution time -->
<action name="someAction" class="com.examples.SomeAction">
<interceptor-ref name="completeStack"/>
<interceptor-ref name="timer"/>
<result name="success">good_result.ftl</result>
</action>
<!-- records action's execution time as well as other interceptors-->
<action name="someAction" class="com.examples.SomeAction">
<interceptor-ref name="timer"/>
<interceptor-ref name="completeStack"/>
<result name="success">good_result.ftl</result>
</action>
This second example uses our own log category at debug level.
<!-- records only the action's execution time -->
<action name="someAction" class="com.examples.SomeAction">
<interceptor-ref name="completeStack"/>
<interceptor-ref name="timer">
<param name="logLevel">debug</param>
<param name="logCategory">com.mycompany.myapp.actiontime</param>
<interceptor-ref/>
<result name="success">good_result.ftl</result>
</action>
<!-- records action's execution time as well as other interceptors-->
<action name="someAction" class="com.examples.SomeAction">
<interceptor-ref name="timer"/>
<interceptor-ref name="completeStack"/>
<result name="success">good_result.ftl</result>
</action>
author: Jason Carreira author: Claus Ibsen |