Re: developing with avalon questions

comments noted, appreciated, incorporated! I will commit what I
have ASAP.

cheers,

- Leo

Schaible, Jörg wrote:
> Hi Berin and Leo,
> 
> 
>>-----Original Message-----
>>From: Berin Loritsch [mailto:[email protected]]
>>Sent: Tuesday, March 11, 2003 9:08 PM
> 
> [snip]
> 
>>True, but the purpose was to demonstrate how to provide better
>>containers by encapsulating the logic for managing a component
>>into a single class.  I would like the spirit of the information
>>to remain.
> 
> 
> Since I guess you're referencing chapter "Using Avalon Framework" 
> here - this was exactly the place were I lost track (or at least 
> was misleaded). I did not realize that the life-cycle described 
> in the chapter before ("Framework and Foundations") is normally
> ensured by the different *available* container implementations.
> Reading the "Using Avalon chapter" I got the impression, that I 
> have to implement all these checkings everytime and all the code
> ensuring the life-cycle in my own containers (defined as components 
> using oterh components). While the chapter tries to show that this
> is not that problematic using ECM, the situation escalated for me
> when I realized, that I was working with ECM on a lot deprecated 
> API.
> 
> What I missed therefore in or following "Framework and Foundataion"
> was a description of responsibilities and task of a container and
> a presentation of the already available container implementations
> (ECM and Phoenix were around at the time of writing DwA) and that 
> I have just to derive my container implementation from their 
> standard container to fulfill these responsibilities. The container's
> descriptions should also explain the differences in short words and 
> what people gain from using one or the other implementation.
> 
> After this description I would try to enable the user to realize the
> described example from chapter "Decomposing a System" with one of
> these containers (possibly Fortress now). This will give the reader
> a good overview of the ease of use of the Avalon ideas using a ready-
> to-go container implementation. IIRC Didier already started such a 
> description at the wiki.
> 
> The following chapter would be assembled from the current "Using 
> Avalon Framework", since here you describe in detail, what kind of
> magic the default containers do and what it takes to write an own 
> simple container implementation.
> 
> The last part of the manual should give an overview of the available 
> components as it is currently done for some ECM components.
> 
> Regards,
> Jörg