Chris Scott wrote:
Peter, check out how logging is implemented in the klondike records example app (in the examples folder). This should get you started. I think the best way to go is let your logging service deal with setup of your logging system be it log4j or cflog and then expose generic methods. Use your aspect to introspect the method call and build the log message, pass that to your service. I'm not sure I would entirely call aspects glue components, however. Remember, you can retrieve those components from the bean factory, too. Aspects can have their own instance data and methods that are not used by the aop framework. Food for thought.
Thanks for the response Chris... I'll take a peek at the klondike sample application -- I looked at in the past, but didn't know what I was looking at exactly. After looking at your blog entry again, I now realize that the aspect components are available from the bean factory too. You're probably right about them not being "glue" -- if only I could describe the picture of all of this in my head...maybe it would make more sense. I guess I'm just trying to figure out "where" the aspect components at located in the system -- sorta like where exactly listeners in Mach-II fit into the picture (I considering them more of them the glue between the framework and the model, but on the side of being an user-defined "extension" of the framework)...
.Peter -- Peter J. Farrell :: Maestro Publishing http://blog.maestropublishing.com Rooibos Generator - Version 2.1 Create boilerplate beans and transfer objects for ColdFusion for free! http://rooibos.maestropublishing.com/ Member Team Mach-II
