Presanna,
The best (and maybe only) solution is to refactor the code to extract
each of those "points" into separate methods, then log the entry to
and exit from each of those methods. Not only will refactoring solve
this particular logging problem, but your overall design will be
improved by the decomposition of large methods into small methods
(http://wiki.java.net/bin/view/People/SmellsToRefactorings).
Of course, depending on the code base, that might be a lot of work,
but the Eclipse and IntelliJ refactorings make it easy to do.
Good luck,
dean
On Oct 5, 2007, at 1:10 AM, Prasanna LM wrote:
Hi,
I am using AspectJ for the logging concern. I am able to add
the log statements (entering & exiting) for all the public methods
and also in exception cases. But, there are lot of other log
statements inside the methods, which i want add using the aspects.
I am not able to find a solution for this using aspectJ. This is
one of the main requirement, if i want to separate the logging
concern from main business logic.
can any body help me to solve this problem ?
Regards
Prasanna
Moody friends. Drama queens. Your life? Nope! - their life, your
story.
Play Sims Stories at Yahoo! Games.
_______________________________________________
aspectj-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/aspectj-users
Dean Wampler, Ph.D.
dean at objectmentor.com
http://www.objectmentor.com
See also:
http://www.aspectprogramming.com AOP advocacy site
http://aquarium.rubyforge.org AOP for Ruby
http://www.contract4j.org Design by Contract for Java5
I want my tombstone to say:
Unknown Application Error in Dean Wampler.exe.
Application Terminated.
[Okay] [Cancel]
_______________________________________________
aspectj-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/aspectj-users
