Re: Design question: Frames or

[Craig R. McClanahan]

Nikolaus Rumm wrote: Hello, I have a question regarding the best practise in page design using struts. One common problem is that a page is composed of several jsp-pages. Normally one would do this using frames, but struts allows a solution with tables and <struts:include>-tags. * IMHO different frames lead to different request-paths, as every frame is an independent page. In the case of <struts:include> tags, will I get a single request, or one for each page ?* Is it possible to refresh a frame or an included page programmatically from another page/action ? What I'm looking for is something as a forward tag with a target property. Regards Nikolaus The last time I suggested frames to a particular web developer that I was working with, it's a good thing I was standing a ways back -- she would have broken my nose :-).  There tend to be very strong feelings on both sides of this issue, so Struts is basically capable of supporting either style. On your latter question, you can indeed cause a different frame to be refreshed programmatically using JavaScript. Craig PS:  One note -- you should only use the <struts:include> tag instead of <jsp:include> if you are nested inside another tag (like perhaps an iteration).  Otherwise, go ahead and use <jsp:include>, which will give you higher performance.  The reason for this is that <jsp:include> currently has a limitation that its output can only go straight to the response, and cannot be buffered.  The <struts:include> tag works around this by initiating a separate HTTP request inside the tag, and then buffering the response.