Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
pgSenderHost: bdhp4103.na.pg.com [192.44.184.138]
Message-ID: <002601c37eaa$668aac10$6bb6769b@NAMRAC2247>
From: james@carmanconsulting.com
To: commons-dev@jakarta.apache.org
References: <3F6A7E6B.6070200@comcast.net>
 <16234.59424.624505.535452@lisa.zopyra.com>
Subject: Re: [HiveMind] Selective intercepting
Date: Fri, 19 Sep 2003 08:34:42 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

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" <rael@zopyra.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
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: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>