Return-Path: 
 <user-return-146610-apmail-struts-user-archive=struts.apache.org@struts.apache.org>
Delivered-To: apmail-struts-user-archive@www.apache.org
Received: (qmail 33646 invoked from network); 10 Nov 2005 01:47:55 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 10 Nov 2005 01:47:55 -0000
Received: (qmail 21311 invoked by uid 500); 10 Nov 2005 01:47:44 -0000
Delivered-To: apmail-struts-user-archive@struts.apache.org
Received: (qmail 21058 invoked by uid 500); 10 Nov 2005 01:47:42 -0000
Mailing-List: contact user-help@struts.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:user-unsubscribe@struts.apache.org>
List-Help: <mailto:user-help@struts.apache.org>
List-Post: <mailto:user@struts.apache.org>
List-Id: "Struts Users Mailing List" <user.struts.apache.org>
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
Delivered-To: mailing list user@struts.apache.org
Received: (qmail 21047 invoked by uid 99); 10 Nov 2005 01:47:42 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Nov 2005 17:47:42 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of rahul.akolkar@gmail.com
 designates 64.233.184.206 as permitted sender)
Received: from [64.233.184.206] (HELO wproxy.gmail.com) (64.233.184.206)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Nov 2005 17:47:34 -0800
Received: by wproxy.gmail.com with SMTP id i31so251582wra
        for <user@struts.apache.org>; Wed, 09 Nov 2005 17:47:19 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=E1MxTUh8BLZS+4ayU3czVsSElp/bXk1F7hlSMX9uBEMPOSLphMSqBthMZfmSI2WoVlFxS4cDIi8rBB6fXid4wNADs0LVs+aRVDuHTty91jQe+7hdRAxmZzke0cDA/l0gL3O797RYyG49tEJaMeCbUa+cDOAP4P6umQSyD0wp4WE=
Received: by 10.65.224.11 with SMTP id b11mr232580qbr;
        Wed, 09 Nov 2005 17:47:19 -0800 (PST)
Received: by 10.65.52.4 with HTTP; Wed, 9 Nov 2005 17:47:19 -0800 (PST)
Message-ID: <ce1f2ea80511091747l43f8de0dpc38d34e533bccdb2@mail.gmail.com>
Date: Wed, 9 Nov 2005 20:47:19 -0500
From: Rahul Akolkar <rahul.akolkar@gmail.com>
To: Struts Users Mailing List <user@struts.apache.org>
Subject: Re: Lists within lists issue
In-Reply-To: <43721D63.3060900@reumann.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <20051108003822.74954.qmail@web32614.mail.mud.yahoo.com>
	 <4371239E.50308@reumann.net>
	 <1db115340511081615t2bb2a327r54614738734575e2@mail.gmail.com>
	 <43721D63.3060900@reumann.net>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

On 11/9/05, Rick Reumann <struttin@reumann.net> wrote:
> Michael Jouravlev wrote the following on 11/8/2005 7:15 PM:
>
> >> <html:textarea
> >> property=3D"someObject[${aProp.someIndex}].subobject[${bProp.someIndex=
}].someField"/>
>
> > Any idea how to simplify input using JSTL 1.1 (JSP 2.0) only?
>
> Well, that would be pretty much impossible without writing a tag to do
> it (since as it stands how could JSP or JSTL have any idea what your
> nested property names are?). If you did make a tag to do it you would
> end up with is something similar to the nested tag:) I think a generic
> "nestedGeneric" tag would be nice which acts like the nested tag but is
> used to just output the correctly structured name property for nested
> elements.
>
<snip/>

Indeed, nested tags work cleaner because they already understand the
contracts between the names on the HTML controls and the form bean
population mechanism used by Struts. This give and take is a very
frameworky thing, and also the reason why the Struts documentation
recommends JSTL replacements for specific tags within specific Struts
taglibs (one can go beyond that, with a pain threshold to match).

Rick -

If you are taking suggestions about your code snippets, which offer a
nice comparison for nested lists, maybe they'd be better off without
the Struts HTML tags? ... since:

 * The HTML tags in that usecase are simple enough to write out as
HTML markup, so this:
<html:text property=3D"foo" value=3D"bar" />
can become this:
<input type=3D"text" name=3D"foo" value=3D"bar"/>

 * Doing so will remove all Struts taglibs from that snippet, not just
the nested one (with the assumption that if someone's trying to avoid
one, they're probably trying to avoid all).

-Rahul


> --
> Rick
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org