Thanks Christopher. I had read that a while back. I do think it's a very cool option when you need to give your aspect some specific info about each method. In the example, Chris creates a generic LoggingAdvice and he uses this custom metadata to tell the logger what to log for each method.
However, I don't think that will work in the situations I am describing. What I need is for actual cfargument tags to be generated in the cffunction tags that are written into the remote proxy, essentially changing the remote proxy's metadata. And the only way I can see to do that is to change how the remote proxy bean itself is generated. Also I think the metadata Chris is using in his logger is different for every method (ie what to log) so it makes sense to do it on a method by method basis. This metadata approach is, at least so far, really meant to apply to all (or most) of the methods being proxied in the same way. Regards, Brian On 7/11/07, Christopher Bradford <[EMAIL PROTECTED]> wrote:
Brian, Have you seen Chris Scott's post from about 6 months back on using custom metadata in the components to drive AOP? It's a little different approach than you're taking, but maybe something like it could work for you: http://cdscott.blogspot.com/2007/01/unlocking-power-of-cf-metadata.html Brian Kotek wrote: > I wanted to get some input about a hack that I just created in > ColdSpring. -- Christopher Bradford Alive! LLP
