Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 15969 invoked from network); 2 Dec 2003 08:38:46 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 2 Dec 2003 08:38:46 -0000 Received: (qmail 11842 invoked by uid 500); 2 Dec 2003 08:38:19 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 11814 invoked by uid 500); 2 Dec 2003 08:38:19 -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 11801 invoked from network); 2 Dec 2003 08:38:18 -0000 Received: from unknown (HELO kerberos) (62.116.51.59) by daedalus.apache.org with SMTP; 2 Dec 2003 08:38:18 -0000 Received: From mail.at.efp.cc ([62.116.51.60]) by kerberos (WebShield SMTP v4.5 MR1a); id 10703543100; Tue, 2 Dec 2003 09:38:30 +0100 Received: from WRPO (wrpo.at.intra.efp.cc [194.107.80.17]) by mail.at.efp.cc (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id hB28cSX08499 for ; Tue, 2 Dec 2003 09:38:29 +0100 From: "Reinhard Poetz" To: Subject: RE: CocoonForms server sizing? Date: Tue, 2 Dec 2003 09:37:40 +0100 Message-ID: <002301c3b8af$8c830450$1e01a8c0@WRPO> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <011601c3b86e$6cc32eb0$eb4bac89@alexk> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal 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 From: Alex Kovacs > Hi Tim, > > I am working on a big project using woody (oops CocoonForms) > with around 1600 forms. We will probably run some benchmarks > to get the sizing info and I will let you know once we get > them done. We however do not know enough about tunning > cocoon, apart from using resource pooling for components set > in the sitemap. Is there other pertinent information that we > should know? > > BTW, woody's widget output type has a flow. If one is using > output for the widget styling in the form template, the > output fields cause the data to be lost in the xml or bean > model. I think what happens is that the binding will try to > map a non existent field and will set the value to > null or empty string. What we did to solve this problem was > to change the woody-field-styling.xsl for the output type as follows: > > > > > <<<<<<<<<< added > line <<<<<<<< > > > > I am not sure where to report this problem and if you > consider a problem at all, so I placed it here :-). Please add it at http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Cocoon%202 -- Reinhard