Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 80247 invoked from network); 6 Dec 2003 23:11:11 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 6 Dec 2003 23:11:11 -0000 Received: (qmail 83148 invoked by uid 500); 6 Dec 2003 23:10:55 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 82877 invoked by uid 500); 6 Dec 2003 23:10:53 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 82864 invoked from network); 6 Dec 2003 23:10:53 -0000 Received: from unknown (HELO main.gmane.org) (80.91.224.249) by daedalus.apache.org with SMTP; 6 Dec 2003 23:10:53 -0000 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1ASlZj-0001b7-00 for ; Sun, 07 Dec 2003 00:10:59 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: dev@cocoon.apache.org Received: from sea.gmane.org ([80.91.224.252]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1ASlZi-0001az-00 for ; Sun, 07 Dec 2003 00:10:58 +0100 Received: from news by sea.gmane.org with local (Exim 3.35 #1 (Debian)) id 1ASlZi-00009x-00 for ; Sun, 07 Dec 2003 00:10:58 +0100 From: Sylvain Wallez Subject: Re: Fixing store design (long) (was Re: CocoonForms server sizing?) Date: Sun, 07 Dec 2003 00:10:57 +0100 Lines: 46 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: fr, en, en-us In-Reply-To: Sender: news 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 Carsten Ziegeler wrote: >Sylvain Wallez wrote: > > >>This is a subject which is itching me badly: cocoon.xconf is way too big. We should remove every component definition that has the default built-in values (eventually leave them as comment) to simplify this frightening configuration file. The same applies to web.xml. >> >> >Oh, I thought Fortress and blocks solves this all... > > Mmmh... they should make the files organized differently, but the problem will remain I guess. >Seriously (I should stop drinking champaigne (champain?) > Hips! Go to http://www.champagne.fr/ ;-) >while answering mails and trying to blog), I really like it to see all possibilities in the xconf; otherwise you have to look into the code :(, > Well, this should normally be described in the docs... "the what?" do I hear ;-) >but ok, perhaps uncommenting theme is a solution but makes the file not less frightend I fear. And if you're afraid of such a file, don't touch it... > > Yeah, but sometimes you have to touch it. Consider Vadim's remark that max-object="100" is for the _sample_ config file. How many people take this sample xconf file and use it as is on their production servers, because they're afraid to break something by touching it? Sylvain -- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } Orixo, the opensource XML business alliance - http://www.orixo.com