Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 23826 invoked from network); 21 Jan 2002 17:29:30 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 21 Jan 2002 17:29:30 -0000 Received: (qmail 6640 invoked by uid 97); 21 Jan 2002 17:28:28 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 6613 invoked by uid 97); 21 Jan 2002 17:28:28 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 6591 invoked from network); 21 Jan 2002 17:28:27 -0000 Message-ID: <3C4C4FB9.5070205@yahoo.com> Date: Mon, 21 Jan 2002 17:28:25 +0000 From: Paul Hammant User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.7) Gecko/20011221 X-Accept-Language: en-us MIME-Version: 1.0 To: Jakarta Commons Developers List Subject: Re: AltRMI Tasks if anyone want to take them References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Sam, >.. as long as it is black. ;-) > >Excellent reply. It touches on one of the significant (IMHO) differences >between commons and avalon. It is a different point than the one I was >going after (the difference between an auto parts store and the parts >counter at a car dealership), but a good point nevertheless. > OK, a quesiton. Commons is about "beanlike" classes that have multiple reuse in servers (though client is not precluded). Avalon-Excalibur is about reusable components that fit the IoC pattern, and in the context of Avalon are decorated at startup from XML configuration, to do this quite a few of them site of Avalon-Framework's componenet abstractions. That a (my) simple view. I've tried to code AltRMI so that is usable in the context of an XML configurable component env like Avalon-Phoenix. It's quite easy if you rigidly separate interface and impl . Of course I could have got it quite wrong... Thus in my view AltRMI is beanlike but because of it's interface/impl separation, it can fit the Avalon-Phoenix env too. I can't help feeling that I have forgotten about the needs of my Excalibur buddies. Regards, - Paul -- To unsubscribe, e-mail: For additional commands, e-mail: