by using tiles, you can define components. A component has a layout and a few jsp. Actually, the layout itself is a jsp written with tiles tags. A component can be nested in another component, just like swing. jsp:include is so simple, and to archive the same goal as tiles, you should do a lot of extra work.
2006/4/12, Antonio Petrelli <[EMAIL PROTECTED]>: > > Raghuveer ha scritto: > > hi Greg, > > How about performance issue if we go for tiles for application that has > 50 > > jsp's > > and that works 24 X 7 with minimum 4 users hitting site at same time ? > > > What I can say is "try and check it out!" ;-) > Anyway, through the performance perspective, Tiles is not so different > to simple <jsp:include>'s. Tiles introduces a little overhead due to the > need of dispatching the tiles around, but it is a very little time > compared to the time that a JSP page needs to render itself. > Raghuveer, you're seeing it to the wrong point of view, Tiles does not > impact on performance when you have JSPs composed of different pieces. > It is different from having a single JSP page for a single HTML rendered > page, but it is the same if you use <jsp:include>'s. > HTH > Antonio > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- 过犹不及
