--- "Hamilton Verissimo de Oliveira (Engenharia -
SPO)" <[EMAIL PROTECTED]> 內容：>
> Some pratical references to interceptors:
>
> http://cglib.sourceforge.net/
>
> http://kasparov.skife.org/intercept.html (point out
> by Aaron some time ago)
This one is interesting, also the Dynaop package it
l
--- Niclas Hedhman <[EMAIL PROTECTED]>
> As I have understood it (it is not my idea), is that
> the Interceptor is an
> interface and have any number of implementations,
> each configured and brought
> to life as components in general.
>
> Albert then suggested a "Order" value for each such
> c
Some pratical references to interceptors:
http://cglib.sourceforge.net/
http://kasparov.skife.org/intercept.html (point out by Aaron some time ago)
http://cvs.apache.org/viewcvs.cgi/incubator-geronimo/modules/connector/src/j
ava/org/apache/geronimo/connector/outbound/
Interesting parts:
- Enh
On Wednesday 21 April 2004 00:06, Timothy Bennett wrote:
> I really like this idea. Would there be some notion of chaining
> multiple interceptions acting on a single service together? Ordering, etc?
As I have understood it (it is not my idea), is that the Interceptor is an
interface and have
Niclas Hedhman wrote:
On Monday 19 April 2004 18:49, Albert Kwong wrote:
public interface AbcService
{
String doAbc ();
String doDef ();
}
/** @avalon.interceptor type=AbcService
**/
public interface AbcInterceptor
{
String doAbc ();
}
/** @avalon.interceptor type=AbcService
**/
pu
Niclas Hedhman wrote:
On Monday 19 April 2004 18:49, Albert Kwong wrote:
I have drafted some ideas here. What do you think?
Ok, I have a better picture now, but one assumption still remain;
1. The InterceptorOne and InterceptorTwo are handled as components by the
container.
I kind-of like th
On Monday 19 April 2004 18:49, Albert Kwong wrote:
> I have drafted some ideas here. What do you think?
Ok, I have a better picture now, but one assumption still remain;
1. The InterceptorOne and InterceptorTwo are handled as components by the
container.
I kind-of like the whole notion, but sti
Since I also lost hammett's post, let me reply it
here:
> I used aspects to provide interceptors capabilities.
However this works for
> all components, not for some in particular. What you
are proposing can be
> (or should be) possible using simple extensions.
In my applications, I am using a two
> On Friday 16 April 2004 11:39, Albert Kwong wrote:
> > What do you think?
>
> I think you have thrown in some fresh thinking into
the pot :o)
>
> However, maybe I am a bit tired, or maybe not smart
enough, but I have a bit
> of problems to realize all the details.
>
> Could you elaborate wi
Sorry I thought my post was lost. Let me search for
your reply and get back to you.
Albert
--- Niclas Hedhman <[EMAIL PROTECTED]> 內容：> > I
have drafted some ideas here. What do you
> think?
>
> You posted this on Friday as well, and I had some
> questions, which still
> remains. Would be gre
> I have drafted some ideas here. What do you think?
You posted this on Friday as well, and I had some questions, which still
remains. Would be great if you could clarify a bit.
Niclas
-
To unsubscribe, e-mail: [EMAIL PROTECT
Avalon is so great! It makes almost everything
pluggable. Besides pluggable, I find it also useful
to make component operations interceptable, so that
external logic can be inserted before and after
operations. It would be even better if the container
can support it and make all components easil
.
Cheers,
hammett
- Original Message -
From: "hammett" <[EMAIL PROTECTED]>
To: "Avalon Developers List" <[EMAIL PROTECTED]>
Sent: Friday, April 16, 2004 9:19 AM
Subject: Re: Proposal: container supported interceptable service
> Hi Albert.
ECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 16, 2004 12:39 AM
Subject: Proposal: container supported interceptable service
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Friday 16 April 2004 11:39, Albert Kwong wrote:
> What do you think?
I think you have thrown in some fresh thinking into the pot :o)
However, maybe I am a bit tired, or maybe not smart enough, but I have a bit
of problems to realize all the details.
Could you elaborate with a larger exampl
?
Thanks.
Albert Kwong
Proposal: Container Supported Interceptable Service
===
Objective
=
Allow components (interceptors) to intercept the
operations of another component in a Chain of
Responsibility pattern. Better support for SOC
16 matches
Mail list logo
