avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bennett, Timothy (JIS/Applications)" <TimothyBenn...@jis.nashville.org>
Subject RE: Avalon Versions
Date Mon, 12 Jul 2004 19:36:31 GMT
> -----Original Message-----
> From: Niclas Hedhman [mailto:niclas@hedhman.org] 
> Sent: Monday, July 12, 2004 2:18 PM
> To: Avalon Developers List
> Subject: Re: Avalon Versions
> 
> Where is the technical problem between AF v4.1.5 and v4.2?
> 
> 1. No change in the AF code itself.
> 
> 2. A Specification Clarification that 4.2 components can 
> declare the Life cycle artifacts in their constructor, 
> instead of the phased population. Containers that does not 
> support this feature, will not be considered 4.2 compatible.
> 
> 3. All 4.1.x components will work in 4.1.x and 4.2 compliant 
> containers.
> 
> 4. Avalon is saying to its users; "Framework is NOT enough to 
> declare a compatible component contract. Containers SHOULD go 
> beyond Framework, and Avalon is providing the tools." You are 
> free to use or ignore this recommendation.
> 
> 5. The roadmap will be pointing to an Avalon 5, which will 
> REQUIRE containers to support a water tight component 
> contract, and not free to introduce incompatibilities in the 
> component-side contract, but free to add extensions 
> elsewhere. Hence the introduction of a "Facility" concept in 
> Merlin to make the distinction clear.
> 

Bingo.

I fail to see why AF4 is a *moving target* for the containers outside of
Apache-Avalon. It's not a moving target.

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


Mime
View raw message