Having still never encountered a use case myself for using the lists in tiles (anyone care to share one or more with me, just to give me a reference?), I feel like I shouldn't make much fuss over those areas of the application; in any case, nothing here would lead me to make a fuss, as it all seems reasonable.
However, what is the solution that you are erasing with this change? Joe On 2/5/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
Hi all! It seems that there are some incoherences between how <tiles:putList> works and the <putList> element inside tiles-defs.xml. In particular: - <tiles:putList>, with <tiles:putAttribute>, creates a list of ComponentAttribute; - <putList>, with element <add>, creates a list of values. Now I wish to "refactor" all this stuff, but I would like your opinion on it: - Rename the <put> element to <putAttribute>, just as the tag name. - Rename the <add> element to <putAttribute>, and it adds attributes and not values. Values are still stored by <item> and <bean> (this erases the solution for a previous issue that I corrected, gulp!). - Rename <tiles:putList> and <putList> to <tiles:putAttributeList> and <putAttributeList>, for coherence. - Remove the "required" clause to the name attribute of <tiles:insertAttribute>, and add a "value" attribute (with "rtexprvalue" set) to insert an attribute contained inside an iterated list attribute value. Thoughts? Antonio
-- Joe Germuska [EMAIL PROTECTED] * http://blog.germuska.com "The truth is that we learned from João forever to be out of tune." -- Caetano Veloso
