The new idea of a "global" interceptor factory would take care of applying one interceptor to multiple service points. We might want to consider something similar to the Spring "autoproxy" facility which allows us to define "selector" implementations based on different criteria. One criteria implementation might take an AspectJ joinpoint definition string and see if it matches the method/class. Another might just be a simpler regex implementation. Anyway, I think you get the point.
-----Original Message----- From: Knut Wannheden [mailto:[EMAIL PROTECTED] Sent: Friday, August 04, 2006 11:20 AM To: [email protected] Subject: Re: Core service implementation instantiation hook I assume you want to wrap the core service implementation inside a proxy. Don't think you can currently do what you want with HiveMind. It would however be nice if you could specify that an interceptor should apply to many (or all) services. Can you maybe use AspectJ? Just a thought... --knut On 8/4/06, Pablo Lalloni <[EMAIL PROTECTED]> wrote: > I would like to have a hook somewhere in the process of services instantiation > to be able to customize how core service implementation instances are > created. > > Looking around in the framework code I can't find an obvious way of doing this > using just descriptors, it seems like I will need to make some changes for > doing this so, I was hoping someone here, with better knowledge of internals, > could point me to right direction. > > Just FYI what I'm trying to do is put monitoring proxies everywhere (without > needing to put explicit <interceptor/> in every service point). > > -- > Pablo I. Lalloni <[EMAIL PROTECTED]> > > [EMAIL PROTECTED] . ICQ#6322141 . [EMAIL PROTECTED] > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~ > G No room for line, 0:1 > >
