Hi Cedric!
I'm pleased you joined the discussion!
Cedric Dumoulin ha scritto:
In some case, I have the feeling that we are going backward :-).
I think it is somewhat intentional :-) AFAIK you wrote Tiles as a
stand-alone software, then you integrated into Struts, then we are
removing the dependency, we're going back in the future :-P
* <get> was changed to <insert> - because we mainly say that we want
to insert something
Insert in the page you mean? I'd say include, as in <jsp:include>
* Attributes "template=" and "component=" were changed to "page=" -
because we specify the page to insert. Tiles is more than a
templating mechanism, and the inserted page is not necessary a
template :-). Maybe we can use "tile=" now that tile is a very
well established name.
This is a nice idea, from my POV
* The controllers were added to allows stand alone use of tiles to
be able to do some kind of computation associated to the tiles.
When used with Struts, there is a redundancy (with the use of
actions), but when used alone, the controller mechanism is very
useful to separate view rendering from controller business
The problem with Tiles controllers is that the controller is not able to
choose between different destination pages. It misses an important part
of a controller: the dispatcher.
But using a normal url as a template (or tile :-) ) it can do both
calling the model and dispatching. If you download the latest version
from SVN, there is a test with a simple servlet that includes a (fixed
for the moment) JSP page.
And I think that including a Controller in a View layer technology is
not a good idea.
It is true that Tiles2 gives us the opportunity to remove all the
redundancies, but we have to take care to not fall again into the
previous mistakes :-)
You're the right person that can help us not to make mistakes :-)
Thanks again
Ciao
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
