Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 7541 invoked from network); 20 Nov 2000 21:48:51 -0000 Received: from mercury.sun.com (192.9.25.1) by locus.apache.org with SMTP; 20 Nov 2000 21:48:51 -0000 Received: from shorter.eng.sun.com ([129.144.252.35]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA20761 for ; Mon, 20 Nov 2000 13:48:47 -0800 (PST) Received: from sun.com (d-ucup02-251-150 [129.144.251.150]) by shorter.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id NAA18408 for ; Mon, 20 Nov 2000 13:48:44 -0800 (PST) Message-ID: <3A199BF9.B4138E15@sun.com> Date: Mon, 20 Nov 2000 13:47:37 -0800 From: Pierre Delisle X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: tomcat-dev@jakarta.apache.org Subject: Re: Proper jsp:setProperty behavior for Tomcat 3.2 References: <764CA2FF49EC054BA086FC8253A52DD743323F@merc09.us.sas.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Larry Isaacs wrote: > ... > I'll try to commit a patch that fixes just the following: > > 1) Fix value="" without allowing param="..." to set. > 2) For a String array property, make "?prop=&prop=text" set the > property for property="*". Currently property="*" handling > assumes only simple properties and skips the set because > the first argument is empty. > > Since proper behavior with respect to empty array element is > still unclear, I'll wait on the removal of empty array elements. > This should be addressed in a separate patch anyway. Sounds good. Thanks. -- Pierre