commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship" <hls...@comcast.net>
Subject RE: [HiveMind] Selective intercepting
Date Fri, 19 Sep 2003 12:42:47 GMT
Right ... it's similar to the BuilderFactory that defines the <construct> element as
its parameter.
This hypothetical interceptor would define <method> elements as its parameter.

--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
http://jakarta.apache.org/commons/sandbox/hivemind/
http://javatapestry.blogspot.com

> -----Original Message-----
> From: james@carmanconsulting.com [mailto:james@carmanconsulting.com] 
> Sent: Friday, September 19, 2003 8:28 AM
> To: commons-dev@jakarta.apache.org
> Subject: Re: [HiveMind] Selective intercepting
> 
> 
> Now, HiveMind itself doesn't need to be aware of this 
> security stuff here, right?  These "method" elements are 
> specific to this type of interceptor, right?
> 
> ----- Original Message ----- 
> From: "Howard M. Lewis Ship" <hlship@comcast.net>
> To: "'Jakarta Commons Developers List'" 
> <commons-dev@jakarta.apache.org>
> Sent: Friday, September 19, 2003 7:58 AM
> Subject: RE: [HiveMind] Selective intercepting
> 
> 
> > Actually, that's why we allow parameters to an interceptor.  I can
> envision something like:
> >
> > <service-point ...
> >   <interceptor service-id="foo.security">
> >     <method name="read" role="system"/>
> >     <method name="update" role="admin"/>
> >     <method name="*" role="user"/>
> >   </interceptor>
> >
> > --
> > Howard M. Lewis Ship
> > Creator, Tapestry: Java Web Components 
> > http://jakarta.apache.org/tapestry
> > http://jakarta.apache.org/commons/sandbox/hivemind/
> > http://javatapestry.blogspot.com
> >
> > > -----Original Message-----
> > > From: Harish Krishnaswamy [mailto:hkrishnaswamy@comcast.net]
> > > Sent: Thursday, September 18, 2003 11:56 PM
> > > To: 'Jakarta Commons Developers List'
> > > Subject: [HiveMind] Selective intercepting
> > >
> > >
> > > 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!
> > >
> > > -Harish
> > >
> > >
> > > 
> --------------------------------------------------------------------
> > > -
> > > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: 
> commons-dev-help@jakarta.apache.org
> > >
> >
> >
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 


Mime
View raw message