excalibur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leo Simons <lsim...@jicarilla.org>
Subject Re: [RT] Components and Handlers
Date Tue, 29 Jun 2004 17:58:00 GMT
Hamilton Verissimo de Oliveira (Engenharia - SPO) wrote:
> Having a separated handler for POJOs and other for Avalon would kill us if
> the user'd like to code his components using both of them. Ok, so now we can
> make the AvalonHandler extends PojoHandler.

better use delegation.

> That's fine. Now we'd like to
> write a InterceptorHandler that gives components interceptors/aop
> capabilities. We should extend what?

what is interceptor capability? If you want to add interceptors you add 

> Creating a chain of handler can solve this situation, or composing them. But
> this can be a bit harsh to configure, don't you think?

Not really. Can use a builder pattern for example.

handler = myHandlerBuilder
   .newHandler( MyBasicHandlerImplementation.class )
   .addInterceptor( MyAdvice.class )
   .enableLifecycleExtension( MyLifecycleExtension.class )

or whatever. Have all the composition is behind the scenes (which is 
also not /that/ difficult to implement well).

> Speaking of thinking,
> what do you guys think? ;-)



Some others:

googling for '"Leo Simons" container' or something like that should pop 
up a whole lot of thoughts from a while back ;)

> (Btw I'm not trying to push this model here, just asking for opinions.)

hehehe :D

You (and Leo Sutic :-D ) are not so far from what in my current thinking 
is the best architecture. Berin is a few steps ahead of me; Pico nor the 
current fortress are actually /that/ different when you get down to it.

In fact, I decided pico was "good enough" in terms of architecture and 
"a whole lot better" in terms of community and maturity so I rm -Rfed my 
own container experiments and joined Paul 'n Aslak 'n friends. /If/ a 
from-scratch-rewrite of fortress is a good idea (I'm not so sure that it 
is), I think it would be a good idea to start with pico and build on that.


To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/

View raw message