avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <blorit...@apache.org>
Subject Re: Re [2]: [Fortress] lookup contract [PATCH]
Date Mon, 19 May 2003 15:24:03 GMT
Anton Tagunov wrote:
> Hello, Berin!
> 

> 
> Step #3
> 
> My last idea on this was about how we choose the default
> component if there's more then one for a role and none
> is marked as 'default'. The idea was to create NO default
> component -- that is FORSE THE CONFIG-WRITERS TO PUT
> default='..' WHEN THERE'S MORE THEN ONE COMPONENT FOR A ROLE.
> 
> Good or bad idea?


If you issue an error and close then it becomes a usability
problem (i.e. it seems too trivial an issue to require shutting
down the system).

If you don't provide an automatic default (i.e. the first
instance available or something like that), then you have
a different usability problem in that you cannot allow your
system to use components designed for "selector" lookup of
components as well as use components designed for "default"
lookup of components.

The whole concept of the "default" attribute is to allow the
developers/config writers some degree of control over the
component assembly.  This is one of Fortress's weak areas.


-- 
"You know the world is going crazy when the best
rapper is a white guy, the best golfer is a black guy,
The Swiss hold the America's Cup, France is
accusing the US of arrogance, and Germany doesn't want
to go to war. And the 3 most powerful men in America
are named 'Bush', 'Dick', and 'Colon' (sic)".

-----Chris Rock


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


Mime
View raw message