struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nimish Chourey , Tidel Park - Chennai" <>
Subject RE: Tiles Two JSP's for Displaying One Form .
Date Tue, 03 Jun 2003 13:15:03 GMT
And you need to have 40 JSP's  to insert those 40 Definintions ...
Isnt it ??

Fine You have one JSp for the Body content .. Then you extend from the
master page to make a new definition in the XML file . 
But then I require another JSP which actually inserts that definition ...

-----Original Message-----
From: Jeff Kyser []
Sent: Tuesday, June 03, 2003 6:24 PM
To: Struts Users Mailing List
Subject: Re: Tiles Two JSP's for Displaying One Form .

No, it should be more like 40 + 1 per re-usable tile component

I set up a 'master page' with the basic layout,
and perhaps a 'menu' include containing my menu buttons / links,
and then the tiles definition just inserts the content into a definition
derived from the master page layout. And that is all done in
the tiles-config.xml file

So you might have 40 definitions in your tiles config + 40 body content 
but certainly not 80 JSPs.

or at least that's my way of thinking on the matter


On Tuesday, June 3, 2003, at 07:41  AM, Nimish Chourey , Tidel Park - 
Chennai wrote:

> Hi ,
> 	In my application there may be around 40 forms . I am using the
> classic layout for the application .
> the body changes for every page , I mean I have a different JSP's for 
> these
> forms .
> Each form is submitted and a result page is desplayed .
> Now my question is if I have 40 forms , so do I need to create total 
> of 80
> JSP (Excluding the result page) ??
> I mean one JSP having the body content and the other one to integrate 
> all
> tiles .
> The second option could be using one JSP having all the insert Tags 
> with the
> Body content .
> Is there any better option available ??
> This question is not for the results page as I know the result page 
> can be
> directly called from the action .
> Nimish

To unsubscribe, e-mail:
For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message