<aop:config>
<aop:pointcut id="servicePointcut" expression="execution(* com.me.xwe.reporting.transaction.TransactionReportGenerator.getReport(..))" />
<aop:aspect id="loggingAspect" ref="methodLogger">
<aop:before method="logMethodEntry" pointcut-ref="servicePointcut" />
<aop:after-returning method="logMethodExit"
returning="result" pointcut-ref="servicePointcut" />
</aop:aspect>
</aop:config>
All desirable things in life are either illegal, banned, expensive or married to someone else !!!
All desirable things in life are either illegal, banned, expensive or married to someone else !!!
All desirable things in life are either illegal, banned, expensive or married to someone else !!!
All desirable things in life are either illegal, banned, expensive or married to someone else !!!
All desirable things in life are either illegal, banned, expensive or married to someone else !!!
All desirable things in life are either illegal, banned, expensive or married to someone else !!!
Praful Thakare wrote:yeha i mean if your pointcut is specific to the class and not to package or wildcard level then that class should have the method,not very sure , but what i think is spring first makes list of all the defined aspects and the pointcuts and then before making object of every bean,it tries to resolve if any of the joinpoint (methods in spring) corrosponds to any of pointcut.
so if pointcut is specific to a class, in your case org.springsource.service.OrderServiceImpl.findOrder then before loading a bean of OrderServiceImpl, spring will try to find existance of findOrder method in static class file not object and it wont find it.
Just wild logical thinking might be completely worng..
-Praful
Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters? |