Peter Donald wrote:
On Wed, 13 Nov 2002 10:29, Clemens Marschner wrote:Actually, its the same answer I would have given. For the past 9 or 12 months, Avalon has become optional - and through that Avalon have become a lot more valuable becuase you don't need to make a design decision on how for to go with the "component model". One of the guys I work with constantly makes me feel like a newbie in the component world (he's older and wiser). He's very very strong of pushing the componet model way down deep. I have a tendency to not do as far as he wouold like - but I should confess that when you have a really fine grain component model it feels over componentized. I also have a suspisition that this is also related to adequate tools and services to support this - but that's something we are working on.
Do you think one should apply the general pattern that interfacing to theEither is possible and different situations call for different approaches. Personally I try to keep all of my code as lightly coupled as possible. Which means I tend to have an Avalon independent part and an Avalon specific part.
Avalon framework is only done on top of a system that is able to run
without Avalon, or to use Avalon as a framework that everything else is
built on? I think we are at a point where we design a new system and make
only code reuse where it is applicable.
However sometimes you will find your self recreating different parts of the Avalon lifecycle. ie You will have a custom lifecycle for your apps or custom configuration/whatever - in which case I would highly recomend you move to Avalon.
It all comes down to how fine grain you want your pluggability / componentization. The more fine grain you go the more likely you want to use Avalon for the low level stuff.
I am not sure thats much of an answer though ;)
Cheers, Steve.
-- Stephen J. McConnell OSM SARL digital products for a global economy mailto:mcconnell@;osm.net http://www.osm.net -- To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
