Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 56067 invoked by uid 500); 3 Apr 2003 03:23:02 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 56054 invoked from network); 3 Apr 2003 03:23:02 -0000 Received: from smtp800.mail.sc5.yahoo.com (66.163.168.179) by daedalus.apache.org with SMTP; 3 Apr 2003 03:23:02 -0000 Received: from adsl-66-141-54-62.dsl.rcsntx.swbell.net (HELO MAUCHI) (ivelin@sbcglobal.net@66.141.54.62 with login) by smtp-sbc-v1.mail.vip.sc5.yahoo.com with SMTP; 3 Apr 2003 03:23:11 -0000 Message-ID: <0b5201c2f990$16e0e700$0100a8c0@MAUCHI> From: "ivelin" To: References: <07fc01c2f807$2d009e70$0100a8c0@MAUCHI> <3E895DAD.6050605@apache.org> <0a2f01c2f8cb$79616230$0100a8c0@MAUCHI> <3E8ABFD8.8090207@apache.org> <3E8AD44D.9@anyware-tech.com> Subject: Re: XMLForm & JSF Date: Wed, 2 Apr 2003 21:21:15 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N In response to the multiple messages in the recent days about using commons validator, I am currently studying hard JavaServer Faces EA3. I will be looking to incorporate the JFC model into XMLForm without the JSP taglib part. Any comments in this direction are welcome. -=Ivelin=- ----- Original Message ----- From: "Sylvain Wallez" To: Sent: Wednesday, April 02, 2003 6:15 AM Subject: Re: [ANN] New version of XMLForm released > Stefano Mazzocchi wrote: > > > > > During the last year of consultancies, I found out that several people > > identified XMLForm as the possible way to turn cocoon into better > > webapp-capable system. > > > And having a good form-handling package in Cocoon is absolutely > necessary to have it adopted to build web applications. I can't remember > how many people asked me about Struts vs Cocoon. I know they are not > comparable, but these people were actually asking for a good forms > handling package. > > And web applications are key for Cocoon's future, since even > publication-oriented sites now want CMS functions that are basically web > applications. > > > > > and include all that 'somewhat-business-logic' that is sooooo common > > between webapps that should be factored out and provided directly by > > cocoon (as struts, somewhat, does). > > > And we should as far as possible build on some common mechanisms such as > commons-validator that will both factorize development effort, promote > cross-project pollinization and help people migrate from JSP/Struts > environments to Cocoon. > > > But I'm more than happy to see XMLForm being factored out because: > > > > 1) this removes the wrong marketing perception that XMLForm is *the* > > solution for data-logic control. > > > > 2) allows people to experiment different approaches (XForm-based or > > not) with the same level of confidence. > > > FormValidationAction did not prevent XMLForm nor Precept to appear, but > these are good arguments to ensure further innovation and development in > this area. And, BTW, Precept is already a block. > > So +1 for a block, but I'm still wanting the current XMLForm code base > to stay in Cocoon's CVS. > > Sylvain > > -- > Sylvain Wallez Anyware Technologies > http://www.apache.org/~sylvain http://www.anyware-tech.com > { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } >