Return-Path: Delivered-To: apmail-jakarta-struts-dev-archive@www.apache.org Received: (qmail 82791 invoked from network); 3 Jan 2004 02:43:22 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 3 Jan 2004 02:43:21 -0000 Received: (qmail 18327 invoked by uid 500); 3 Jan 2004 02:42:59 -0000 Delivered-To: apmail-jakarta-struts-dev-archive@jakarta.apache.org Received: (qmail 18273 invoked by uid 500); 3 Jan 2004 02:42:58 -0000 Mailing-List: contact struts-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Struts Developers List" Reply-To: "Struts Developers List" Delivered-To: mailing list struts-dev@jakarta.apache.org Received: (qmail 18260 invoked from network); 3 Jan 2004 02:42:58 -0000 Received: from unknown (HELO mail30.internethostingsolutions.com) (69.49.100.30) by daedalus.apache.org with SMTP; 3 Jan 2004 02:42:58 -0000 X-Authenticated-User: batien.duong.dbgroups.com Received: from dbgroups.com (s142-179-180-163.ab.hsia.telus.net [142.179.180.163]) (authenticated bits=0) by mail30.internethostingsolutions.com (8.12.10/8.12.9) with ESMTP id i032h6mv038141 for ; Fri, 2 Jan 2004 21:43:07 -0500 (EST) Message-ID: <3FF62C67.8030909@dbgroups.com> Date: Fri, 02 Jan 2004 19:43:51 -0700 From: BaTien Duong User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Struts Developers List Subject: Re: [Proposal] ActionFactory refactoring References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Vic Cekvenich wrote: > > > Don Brown wrote: > It would take probably a few hours > >> to code so little effort is "wasted" when the struts-chain move takes >> place. >> > > I think that is the key at the end of the day. I think it be more > effective the few hours be spent on integrating IoC into struts-chain.... Yes, integration of Struts-chain and IoC seems to hold a key for managing a group of services that are passed via Struts-Chain as a controller. I am exploring this with PicoContainer (using DefaultLifeCyclePicoContainer which provides both life cycle management and Config object). BaTien DBGROUPS > but I do not need to remind anyone I am not a commiter, and even then > each comiter can commit what they please, but I would rather see a > design of IoC in CoR. If CoR already does digester, it can't be to far > away from some level of alpha. I think it easier to work with a clean > sheet of paper, but your preference, thanks for contributions. > Maybe if there is a way to create a commons-IoC-api of interfaces that > could be implemented as Nano, Hivemind, etc. and .... I duno. > > .V > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: struts-dev-help@jakarta.apache.org > > . > --------------------------------------------------------------------- To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: struts-dev-help@jakarta.apache.org