Either wrapper or inheritante - to solve this specific issue - is a burden. Shall we establish a roadmap to make Avalon supports another strategies?
Btw what are the personal activities of each 'avaloner' 'til end of this year? What we want to see in Avalon in the end of this year? My goals: - See Avalon# talking to Merlin through SOAP and IIOP Merlin providing services to Avalon# and vice-versa - Avalon# supporting different strategies (I'm tired of 'IoC level' thing) - Avalon# 1.0 Released - Castle 1.0 Released -- hammett -----Mensagem original----- De: Alex Karasulu [mailto:[EMAIL PROTECTED] Aaron, > > > 1. Support of other dependency management schemes in Avalon > > > 2. Making it easier to reuse Avalon components in non-Avalon > frameworks > > > > to make Eve's components available to other containers like Pico. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
