Something to consider, that if you start an entire AspectJ framework
you're increasing your server startup time (whether it's large or
not). I liked the solution Roo brings to the table, and that is it
compiles AspectJ out of the source by the time it is deployed simply
by inserting the Java code
Hi Sudhir,
Try using interfaces for your objects. I have been able to use aspects
in my applications using Spring interceptors instead of weaving, which
is triggered (I may be wrong here) when your class does not implement
any interfaces.
Bottom line: inject interfaces instead of bean
