tag:blogger.com,1999:blog-2592381182145606344.post5309297883094382126..comments2023-11-08T11:39:39.159+01:00Comments on Maxence's technical corner: Using WLDF to trace the time taken by your methodsMaxence Buttonhttp://www.blogger.com/profile/03432797928549149364noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2592381182145606344.post-17977682071984474512008-12-29T11:56:00.000+01:002008-12-29T11:56:00.000+01:00:) you're right Alex ! That's the price I have to ...:) you're right Alex ! <BR/>That's the price I have to pay for writing articles in the train or in the hotel : I may be "slightly" mistaken sometimes.<BR/><BR/>I will update the article according to your remarks.<BR/><BR/>Thanks buddy !Maxence Buttonhttps://www.blogger.com/profile/03432797928549149364noreply@blogger.comtag:blogger.com,1999:blog-2592381182145606344.post-91856716102635559932008-11-28T12:56:00.000+01:002008-11-28T12:56:00.000+01:00WLDF instrumentation does not rely on AspectJ alth...WLDF instrumentation does not rely on AspectJ although a large influence came from AspectJ work we did at BEA.<BR/>The instrumentation is tailored to be very fast and lightweight, and the pointcut are limited so that you can't shoot in your feet.<BR/>The actions (advice) are also limited to what is bundled by WLS - same here - so that you can't shoot in your feet (ie no action will change the control flow or threading).<BR/>Also WLDF since 10.3 (I think) support runtime class definition so you should be able to add actions and pointcuts at runtime.<BR/><BR/>If you want to go beyond the semantics limitations of WLDF you can certainly use AspectJ or SpringAOP in your apps.Alexhttps://www.blogger.com/profile/02000951254466645137noreply@blogger.com