On the struts dev list, we had a thread about some changes to the Tiles tags (see http://www.nabble.com/-Tiles2--JSTL-functions-for-Tiles-taglib--t2961079.html )
Today on the struts user list, someone asked a question about the PutList tag which relates to something which is fixed in there. Can we wrap up that previous thread -- Antonio, hope you're not super busy right now -- I'd mostly like to hear if you still have concerns about the changes which were made which would make it premature to build a new SNAPSHOT based on SVN head. Joe On 1/16/07, Joe Germuska <[EMAIL PROTECTED]> wrote:
I'm sorry, I'm afraid I'm just not understanding you. If I use "<tiles:insertAttribute name="foo" /> and Foo was defined as a string, the end result is a visible string in the page. I have trouble perceiving that as a definition, while it naturally fits my concept of "insert." Perhaps your concern is that there might be some indeterminacy between whether any given attribute value might refer to a specific definition or is actually intended as a mere string value. I'm open to the position that this is unnecessarily confusing, although my current feeling is that that's not such a serious problem. The original point, however, was that it is valuable to be able to have a tag which inserts content based on an attribute's value whether that value is a "template" (any valid servlet path) or a "definition" (something which Tiles can use to invoke a servlet include including other tilesprocessing.) If the tag which does this never includes a literal string, I would not find that a big problem. But if I need to know ahead of time whether I want to insert a template or a definition, I think that's a shortcoming. Joe On 1/16/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote: > > Sorry for not writing, but a job "storm" hit me, and I am changing place > of work (and town). > Anyway, comments are below. > > Greg Reddin ha scritto: > > I like the idea that a tag that displays something on > > the page should indicate so in the tag name. Maybe we need to clarify > > the > > difference between "defining" and "inserting". > > The problem is that "defining" and "inserting" an attribute is made by > the same tag. > In other words, I see "defining" as specifying a "setAttributeName" > method in a class, while "inserting" is the use of that attribute. > In the case of <tiles:attribute> (or <tiles:insertAttribute>) it is > defined (you can fill this attribute) and used (where the tag is, the > attribute is inserted). > The problem is that inserting an attribute is substantially different to > inserting a template or a definition (layout pages for attributes, > composite pages for the latter ones), so a simple "insertAttribute" does > not give a complete idea of what it is. > > Ciao > Antonio > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- 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
-- 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
