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:[EMAIL PROTECTED]
> 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: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
