[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aspectj-users] Can AOP really solve the "logging problem"?
|
My experience is AspectJ as it is right now can't nicely solve the logging
problem. The reason is logging often involves intermediate states of the
program which largely involves temporary or local information. Accessing
local information is prohibited by AspectJ. The usual hack I do is to
write temporary methods to expose the logging context. That is bad because
it requires the coordination of the base program.
Just a thought.
Charles Zhang
Graduate Student, Middleware Systems Research Group
ECE, U. of Toronto (http://www.eecg.utoronto.ca/~czhang)
" Yawn!!"
On Fri, 11 Apr 2003, John W. Cocula wrote:
> I have seen references to the hypothesis that AOP in general, and
> AspectJ in particular, can separate out the concern of *logging* (not
> tracing) in large systems. In fact, an excellent Xerox PARC
> presentation referenced Tomcat's extremely messy logging as a target for
> AOP.
>
> But I have yet to find a detailed treatment of how logging could be
> cleanly separated with AOP or AspectJ. Does anyone have any concrete
> references?
>
> Many thanks for your help.
>
> Regards,
> John
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/aspectj-users
>
