[EMAIL PROTECTED] ha scritto:
I'm sorry, but I'm behind in my reading and haven't been paying close
enough attention to the messages on Tiles 2.
You had to do it :-) All discussions on these kind of things have been
made in the mailing list.
Could you explain the
reasoning behind this
Antonio Petrelli wrote:
In the Struts Users and Shale Users mailing lists we (Greg and I)
encountered several people confused by the different meaning of
tiles:insert, so we decided to specialize this tag in
different tags,
I chose only the names.
And I don't think that anyone used
[EMAIL PROTECTED] ha scritto:
Antonio Petrelli wrote:
In the Struts Users and Shale Users mailing lists we (Greg and I)
encountered several people confused by the different meaning of
tiles:insert, so we decided to specialize this tag in
different tags,
I chose only the names.
And I don't
, October 27, 2006 7:33 AM
To: Struts Developers List
Subject: [tiles2] Changes in tag libraries
Hi
As you may have seen, I replace tiles:insert tag with three
specialized tags:
tiles:insertDefinition, tiles:insertTemplate,
tiles:attribute. I hope you don't hate me for the change
:-) I
Antonio Petrelli asked:
[EMAIL PROTECTED] ha scritto:
Antonio Petrelli wrote:
In the Struts Users and Shale Users mailing lists we (Greg and I)
encountered several people confused by the different meaning of
tiles:insert, so we decided to specialize this tag in
different tags,
David H. DeWolf ha scritto:
There are probably two types of people that will need to port:
1) Those that use tile. They register the listener and use the tags.
(probably mostly Struts1 users)
...
IMHO we should do everything possible to keep migration for #1 simple.
...
The tag in question,
I wonder if it would be possible to provide the combined
tiles:insert tag as well for people who are porting applications.
There are two questions that come to mind: 1) Have we already made
porting to Tiles 2 a non-trivial task by all the changes we've made,
and 2) are we ready for the
There are probably two types of people that will need to port:
1) Those that use tile. They register the listener and use the tags.
(probably mostly Struts1 users)
2) Those that integrate tiles into their framework. They access the api
and want to be able to customize it.
IMHO we should
Hi
As you may have seen, I replace tiles:insert tag with three
specialized tags:
tiles:insertDefinition, tiles:insertTemplate, tiles:attribute.
I hope you don't hate me for the change :-)
I thought that an eventual tiles:insertString is useless, since there
are better tags to put strings.
