After getting my first output from FLOW3 yesterday I continued my tests and gave aspects a try. It took my some time to get my aspect running but eventually it worked out.

Same as the first "Hello Worl" test, this test is fairly simple. All I do is, definig an aspect called "AspectTest" (Yeah... This some fancy kind of a name) which is executed around every method in all classes beginning with "T3_ThomasTest_":

 
/**
 * Advice to check if the static function is proxied correctly (will result in a fatal error
 * if it doesn't)
 *
 * @around method(T3_ThomasTest_.*->.*())
 */
public function someTestAdvice(T3_FLOW3_AOP_JoinPointInterface $joinPoint) {
	$startTime = microtime(true);
 
	$returnResult = $joinPoint->getAdvicechain()->proceed($joinPoint);
 
	$endTime = microtime(true);
	$logMessage = $joinPoint->getClassName().'->'.$joinPoint->getMethodName().' execution time: '.(($endTime -$startTime)*1000).'ms';
	$this->logger->log($logMessage, T3_Log_LoggerInterface::SEVERITY_DEBUG);
 
	return $returnResult;
}
 

What the advice actually does is nothing outstanding. Before the target method is executed, it stores the timestamp in a variable. The next step is to process the advice chain which means, that all other advices at this point are exceuted until the target method is reached. The result is passed through the calls and eventually arrives our advice.

When it arrives, the timestamp is stored again and the difference between both timestamps is calculated and written to a logmessage.

This logmessage is than handed over to the Logger Interface. How it is processed further is not decided by the advice because we only "talk" to a generic Logger interface. The final implenetation of the logging mechanism has to be configured via a Components.ini file. In my case I configured the usage of the "SimpleFileLogger" Because it's the only implemeted Logging mechanism yet.

You can download the complete "ThomasTest" package at the end of this article.

Greets,
Thomas