Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 56169 invoked from network); 2 Jul 2002 17:25:22 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 2 Jul 2002 17:25:22 -0000 Received: (qmail 18881 invoked by uid 97); 2 Jul 2002 17:25:17 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 18742 invoked by uid 97); 2 Jul 2002 17:25:16 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 18690 invoked by uid 98); 2 Jul 2002 17:25:15 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <3D21E1DB.7010108@apache.org> Date: Tue, 02 Jul 2002 19:24:43 +0200 From: Nicola Ken Barozzi Reply-To: nicolaken@apache.org Organization: Apache Software Foundation User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Avalon Developers List Subject: Re: [ISSUE] containerkit References: <001901c221e1$c5e591b0$0801a8c0@Lagrange> <3D21D0DF.5080507@osm.net> <3D21DBE4.3060100@apache.org> <3D21E012.2040108@osm.net> 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 Stephen McConnell wrote: > > > Nicola Ken Barozzi wrote: > >> >> Stephen McConnell wrote: >> >>> >>> >>> Leo Sutic wrote: >>> >>>> >>>> >>>>> From: Nicola Ken Barozzi [mailto:nicolaken@apache.org] >>>>> To be concrete, this is the Cocoon Context: >>>>> >>>>> >>>> >>>> >>>> >>>> >>>> Nicola, I do not understand what you're getting at. >>> >>> >> >> I'm just telling you what Cocoon uses as a Context *now*. >> It's just a fact. >> >> What I would like is to see suggestions from you on how it should be >> done instead, or if it's ok as-is. >> >>>> My point is that if the context is only constants that >>>> are entered by an assembler (a person), then it is not >>>> different from a Configuration. >>> >>> >> >> And the Cocoon one is not entered by an assembler. >> It contains also params that change *per request*. >> >>> Disagree - a configuration is an object model that provides access to >>> basic types (Strings, booleans, long, int, etc.). It has no support >>> for complex types (e.g. java.io.File). A context object created >>> using directives prepared by an assembler can contain directives for >>> the creation of basic AND complex types (see earlier example and >>> ContextFactory source). I can write directives for creation of >>> objects with multiple argument constructors - which basically means >>> that minimal effort is needed. >> >> >> >> This is what happens now, but IMHO it's not a definition of what a >> context should do (and I don't think you were giving a definition BTW ;-) >> >> Can you guys please tell me what you would do for the CocoonContext or >> you don't have a clue? >> > > http://marc.theaimsgroup.com/?l=avalon-dev&m=102562981120502&w=2 I recieved the mail late 8-) Thank you for the reply :-) -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- -- To unsubscribe, e-mail: For additional commands, e-mail: