Actually, for me it was a tradeoff. Here are a few thoughts:

Good things about Sitemesh:
- Sitemesh does not have as much XML configuration as tiles, which was
very compelling (most configuration was maintained in the JSP page).
- Relatively simple to learn and simpler to maintain since most things
you need are configured once in an XML (decorator) and the rest you
could rely on an included JSP (optional) to managed other attributes.
- Since there is no XML that dictates the tiles (only a filter that
knows how to decorate the fetched HTML page), there is no need to add
the overhead of managing another XML structure (e.g. tiles) to know
which tile goes where.


Bad things about Sitemesh:
- Sitemesh has not been maintained for a long time. Release of 2.3 was
done in 2006 and 2.4 and 3.0 is still in development.
- Sitemesh uses a StringBuffer object to decorate the output (as far as
I know, this is the case in version 2.3) which means that depending on
the presentation you need to fetch, such decorating can become an
expensive operation.

I like Sitemesh a lot and after working with both for some years now, I
would recommend Sitemesh mostly for simplicity.

Hope this helps!

Kibo wrote:
> Hi konference
>
> In Struts1 i used Tiles and i was satisfied. I saw that now in Struts2 it is
> recomended use Sitemesh.
> I read about Sitemesh and i dont find whay is Sitemesh for me better then
> Tiles 2.
>
> Maybe is Sitemesh better when:
> - i need to decorate some old application
> - i use other framework then Struts2
>
> but I started new application in Struts2.
> Is it other reason why i have to use Sitemesh?
>
> Thanks very much
>
>
> -----
> Tomas Jurman
> Czech Republic

--

Alberto A. Flores
http://www.linkedin.com/in/aflores

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@(protected)
For additional commands, e-mail: user-help@(protected)