I agree with this. For the EL tag, it doesn't make sense to use the 'name'
attribute in this case. In the tag without EL, name is still a valid
attribute.
How does the JSTL forEach tag handle this? Glancing at it, it looks like
you always need to specify ${} around everything. If you don't, it just
assumes that what was specified for 'items' is the item itself:
<c:forEach items="item1" var="item">
<c:out value="${item}"/>
</c:forEach>
prints out 'item1', which kinda surprised me.
On Thu, 11 Mar 2004, Tim McCune wrote:
> Then how about renaming the "name" attribute to "list", since, as you
> said, it is a reference to a list object, and no longer the name of a
> list object? It still seems silly to me to have an attribute that can
> never be used without escaping the value with ${}, but it's not my
> project. :)
>
> On Thu, 2004-03-11 at 10:43, Fabrizio Giustina wrote:
> > Right, you will never use <display:table name="userList"> without ${}...
> >
> > the "name" attribute expects a reference to a list object: in the "old style" this
> > was done using a custom sintax, in the EL version this is done using the standard
> > expression language. It works in the same way all the other jstl tags work.
> > If you need your list to be choosen dinamically you can set a different variable
> > before the display:table tag.
> >
> > Sorry Tim, but I still don't think that using el to generate an expression which
> > is then re-evaluated using a different sintax can be a good design...
> >
> > fabrizio
> >
> >
> > ________________________________
> >
> > From: [EMAIL PROTECTED] on behalf of Tim McCune
> > Sent: Thu 11/03/2004 16.36
> > To: [EMAIL PROTECTED]
> > Subject: RE: [displaytag-devel] EL Tag and getting lists in the "name"attribute
> >
> >
> >
> > Fabrizio, that seems wrong. With that implementation, when would you
> > ever use the "name" attribute without ${}? A proper implementation
> > should look like either:
> >
> > <display:table name="userList">
> >
> > or
> >
> > <display:table name="${listName}">
> >
> > The second case uses double indirection, so it would only be used in a
> > situation where you have several different lists in the page context
> > that you can choose from, keyed by names, and the name of the list you
> > choose needs to be dynamic. Granted, this is a very odd-sounding use
> > case, but it could happen. The reason that EL tags seem weird in this
> > case is because the value of the "name" attribute should be a variable
> > reference. EL tags make much more sense in attributes that are
> > constants, e.g.
> >
> > <display:table name="userList" cellspacing="${cellspacing}">
> >
> > On Thu, 2004-03-11 at 10:19, Fabrizio Giustina wrote:
> > > yes, this is absolutely intentional, see my first mail on the thread:
> > > http://sourceforge.net/mailarchive/message.php?msg_id=7406316
> > >
> > > fabrizio
> > >
> > > ________________________________
> > >
> > > From: [EMAIL PROTECTED] on behalf of Matt Raible
> > > Sent: Thu 11/03/2004 16.04
> > > To: [EMAIL PROTECTED]
> > > Subject: [displaytag-devel] EL Tag and getting lists in the "name" attribute
> > >
> > >
> > >
> > > One thing I noticed with the nightly build. Before I was using the
> > > following with the EL tag and it worked:
> > >
> > > <display:table name="userList" cellspacing="0" cellpadding="0"
> > >
> > > Now I have to use:
> > >
> > > <display:table name="${userList}" cellspacing="0" cellpadding="0"
> > >
> > > I just want to make sure this is intentional. I'll update my code to
> > > reflect this (as it makes sense). I guess my main question is - will
> > > this change or is this behavior from here on out. Will the name in the
> > > EL tag always require ${}? If I try to use name="userList", I get:
> > >
> > > Exception: [.LookupUtil] Error looking up property "username" in object
> > > type "java.lang.String"
> > > Cause: Unknown property 'username'
> > >
> > > Thanks,
> > >
> > > Matt
> > >
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.Net email is sponsored by: IBM Linux Tutorials
> > > Free Linux tutorial presented by Daniel Robbins, President and CEO of
> > > GenToo technologies. Learn everything from fundamentals to system
> > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> > > _______________________________________________
> > > displaytag-devel mailing list
> > > [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/displaytag-devel
> > >
> > >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: IBM Linux Tutorials
> > Free Linux tutorial presented by Daniel Robbins, President and CEO of
> > GenToo technologies. Learn everything from fundamentals to system
> > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> > _______________________________________________
> > displaytag-devel mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/displaytag-devel
> >
> >
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> displaytag-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/displaytag-devel
>
--
John York
Software Engineer
CareerSite Corporation
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
displaytag-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
