> > > > I think this template structure is helpful for the DRY (don't repeat > yourself) concept. Imagine: you are changing the portal to a new design: > would you like to edit and test the same snippet in all the pages? > Something similar is aimed in the Tiles framework within Struts framework > using JSP(http://struts.apache.org/struts-tiles/index.html). Could you > take > a look at it if it is helpful integrating this in your future work on JSP > templates?
AFAIK, struts templates are not divided into multiple file. Struts template is a single file which holds the complete page outline. Page fragments (tiles) are included into the page outline at runtime. And this is what actually want to achieve. Jetspeed decorator templates are defined just once (if I am not wrong) and there is no question of DRY. For a new portal design, I believe you will need a new tempalte which may have totally diffrent structure. > difficult to edit a template in a editor (e.gEclipse). > > Maybe it could be helpful in documentation a short "how-to": editing > templates in editors (e.gEclipse). > (helpful mainly for beginners like I am :)) Yes, any kind of documation is always helpful. Thanks, Raj --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
