Ahhh, yes! I see what you mean. What I had in mind was something like
this...
interceptor-chain (id="standard-interceptors")
{
interceptor (service-id="hivemind.LoggingInterceptor")
interceptor (service-id="somemodule.SecurityInterceptor")
}
implementation (service-id="MyService")
{
interceptor (chain-id="standard-interceptors")
}
I am not sure that's the best syntax, but you get the idea. This way, I can
save some typing (the more interceptors, the more you save, obviously). It
could also be used in conjunction with your idea! You could inject an
interceptor chain into a group of services, identified using some form of
regular expressions like you propose!
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, July 26, 2004 1:50 PM
To: [email protected]
Subject: RE: service for interceptor configuration
James,
> Maybe I didn't word my question very well, but I think we
> are both talking about the same thing. That's what I was
> trying to find out. I think what you're suggesting is that
> we have a way of defining a reusable list of interceptors
> that can be applied to multiple services as a whole, rather
> than having to re-define the entire list for all the services.
> Is that what you want?
I think we are talking about slightly different things here. Let's take
a look at a more comprehensive example. Imagine a module with the
following descriptor:
module (id=com.foo version="1.0.0")
{
service-point (id=A interface=com.foo.A)
{
invoke-factory (...) {...}
}
service-point (id=B interface=com.foo.B)
{
invoke-factory (...) {...}
}
}
Now I'd like to apply the same interceptor (e.g. the
hivemind.LoggingInterceptor) to both of the declared services. I could
do this in the same module or a different module. Irrespectively it'd
go something like this:
implementation (service-id=com.foo.A)
{
interceptor (service-id=hivemind.LoggingInterceptor)
}
implementation (service-id=com.foo.B)
{
interceptor (service-id=hivemind.LoggingInterceptor)
}
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
