Is there any interest in a Tiles Convention?
ie. a Tile found by the TilesResult based on the package and name of the
action.
The problem I'm trying to solve is that with ajax html results (page
fragments) a TilesResult can easily:
- substitute a Tile based on the theme; and/or
- substitute a Tile based on the locale; and
- embed Tiles within another page without concern for the location and
theme/locale (much better IMHO than s:include, jsp:include, ftl:include)
Unfortunately when using CodeBehind/Convention I still have to declare
each TilesResult explicitly, which is a drag and fragile and I'm
beginning to question its value.
I'm not sure how it would work, but some solutions are:
1. Stop using Tiles, instead extend Convention to allow a locale
and/or theme to be included in its search for a jsp/ftl/vm result (point
3 above isn't solved though); or
2. if the Tiles plugin is installed, the convention's search is
extended(?) to search for a Tile matching "package.action.result" (not
sure how yet...)
3.Change TilesResult to accept variables in the tiles name
@Result(name="show", type=TilesResult.class,
value="tiles.{action}.show") (which doesn't reduce code, but starts a
useful convention)
I get the impression that few users use TilesResult though (but do use
Tiles within JSPs).
Any thoughts?
cheers,
Jeromy Evans
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
