Ok, I absolutely agree that "name" is not the best name for this
attribute...
The problem is:
- I don't want to have different attributes in the standard/el version
of the tag: I'll probably try to have only on tag class for both
versions and I want to avoid the need for different documentation/tag
reference.
- absolutely don't want to keep 2 different attributes in the EL version
(one with the EL sintax, one with the beanutils sintax). They do the
same thing and EL has always been thought as a replacement for the
original sintax.
- "list" would be a better name, but the list attribute was deprecated
recently in favor of name and I don't want to reintroduce it without an
"intermediate" release.
Probably deprecating "name" and modifying "list" to handle both list
objects and expressions could have been the solution... But since we
started with "name" in the 1.0 branch I will wait at least after the
definitive 1.0 release before deprecating it and introduce a new
attribute for 1.1.
So, probably the best solution IHMO is:
- keep "name" till 1.0 (absolutely, if we want to release it soon)
- after 1.0: remove all the deprecated attributes, deprecate "name" and
introduce a better named attribute for both the standard/el version
("items", "source"?)
fabrizio
-------------------------------------------------------
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_id70&alloc_id638&op=click
_______________________________________________
displaytag-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
