In this situation, I would recommend that the interceptor use its own configuration file so that it knows what to do. I wouldn't suggest having HiveMind have to "decide" whether to call an interceptor or not.
----- Original Message ----- From: "Bill Lear" <[EMAIL PROTECTED]> To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]> Sent: Friday, September 19, 2003 7:27 AM Subject: Re: [HiveMind] Selective intercepting > On Thursday, September 18, 2003 at 23:56:27 (-0400) Harish Krishnaswamy writes: > >Interceptors, as I know of them in HiveMind right now, can only be > >applied across the board to all methods in the service; there is no > >selectivity. But, I think, selective intercepting will be a requirement > >for other kinds of interceptors (like a security interceptor or a > >transactional interceptor, for example). What do you think? I realize > >this would be treading along the AOP territory; may be this could extend > >into an ultra light aspect framework too! One for all! > > So, for that to happen, would a service-point have to declare a > set of methods? > > > Bill > > --------------------------------------------------------------------- > 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]
