Are you merely trying to set up a group of reusable interceptors to add to a bunch of different services?
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, July 26, 2004 4:45 AM To: [email protected] Subject: service for interceptor configuration Hi, I came to think of a something I'd like to get an opinion on from you other HiveMinders. I thought it would be nice with a service which would set up interceptors for a bunch of services. Let's say I have a module with some services and I'd like to wrap the logging interceptor (or maybe a custom security interceptor) around each of them. Currently I'd do this by adding a <implementation> with a nested <interceptor> element for each service. My idea was to let a new service setup all the interceptors. With contributions I could specify which target services a specific interceptor should be wrapped around. E.g. contribution (configuation-id=InterceptorInjections) { injection (interceptor=hivemind.LoggingInterceptor services=my.*) } The configuration would use a very primitive pointcut language (pattern matching on service ids) to identify the services which the interceptor should be wrapped around. Would something like this be useful? --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]
