Regarding the problem of AOP, the last Java gathering Gigix told the application of AOP, and some of the very persuasive examples, and did mention that the LOG granularity is too small, and distributed in all the procedures, in addition to the operation of the flow of water. In fact, it is not suitable for AOP. Later, when I discussed with Dlee, I thought it is now outside.
Examples AOP will take the log for example, actually not very suitable.
Other code-independent code, such as the transaction is very suitable for AOP.
There are also as PerformanceInterceptors, when you have a performance problem, you can know how much time you consume directly on the method before and after the method.
As for usually said that AOP can be used to use rights aspect, but generally every company permission system is often
Coupled with business code, so permissions are often difficult aspect, but AHBBXIE said to scale JaaS
Http://forum.javaeye.com/viewtopic.php?t=4117, have time to study.
There is also cache aspect, nor very well, one is that a parameter of the contract is ID,
One is the parameter implementation of a specific interface to let Cache aspect find it, but there is a specific agreement.
Business logic can not be fully transparent Cache in the case of Unware, then there is Object to modify the new cache when Field, and it is not very convenient to feel, it is better to directly write.
