What I was suggesting was that the above two declarations could be
replaced by the following:
contribution (configuation-id=InterceptorInjections)
{
injection (interceptor=hivemind.LoggingInterceptor
services=com.foo.*)
}
The configuration contributed to would be used by the suggested service,
let's call it InterceptorInjector, to apply the
hivemind.LoggingInterceptor to every service in the com.foo module. I
used a pattern to select the services which the interceptor should be
applied to, which is very primitive, but maybe it's good enough.
The InterceptorInjector service could of course also be used with
predefined lists of interceptors, which seems to be what you are talking
about.
Hope this example makes things clearer.
--knut
I think this is a great idea... looks very powerful and much oriented towards AOP.I, being now implementing security interceptor stuff, could really use a thing like this...
-- Pablo I. Lalloni <[EMAIL PROTECTED]> Teléfono +54 (11) 4347-3177 Proyecto Pampa Dirección Informática Tributaria AFIP > In 2010, M$ Windows will be a quantum processing emulation layer for a > 128-bit mod of a 64-bit hack of a 32-bit patch to a 16-bit GUI for an > 8-bit operating system written for a 4-bit processor from a 2-bit > company that can't stand 1 bit of competition. |
