Incidentally I use a HUGE amount of AOP stuff and logging is the only thing I am not using with it.
I use AOP for the following Declarative security management ( down to filtering returned Collections by an ACL ) Declarative transaction management ( so that I don't have any transaction management garbage in my code ) Automatically managing hibernate sessions. In fact anywhere that you find yourself writing more boilerplate than business code or repeating the same code again and again and again ... you might find AOP saves you a lot of time and energy. --b On Mon, 29 Nov 2004 17:34:29 -0600, Joe Germuska <[EMAIL PROTECTED]> wrote: > >>Would there be a simpler way of enabling automatic logging across > >>entire application so that I do not have to modify all of my classes > >>and JSP pages? > > Sounds like the textbook use case for aspect oriented programming. > Logging is about the only thing they all talk about! > > But realistically, I'm with Eddie -- what logging can you really > apply consistently and automatically in a way that is more useful > than noisy? If you have a bunch of fairly repetitive stuff spit out, > then finding the real information is fairly tedious. > > On the other hand, I don't find it all that burdensome to establish a > static log instance for each class and toss around a few > log.debug(...) lines, especially when I'm working on figuring out > someone elses ill-documented code! > > Unfortunately, I don't know a whole lot about AOP, but there has been > plenty written about it in the last couple of years if you decide to > look further. > > Joe > > -- > Joe Germuska > [EMAIL PROTECTED] > http://blog.germuska.com > "Narrow minds are weapons made for mass destruction" -The Ex > -- http://www.revoltingdigits.com https://jestate.dev.java.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
