-
1. Re: Frameset & Seam
pmuir Nov 6, 2006 5:09 AM (in response to bluetrade)Which type of links are you using? h:commandLink?
-
2. Re: Frameset & Seam
diablo341 Nov 8, 2006 10:13 AM (in response to bluetrade)I'm designing a new app and I want to know if it's a good idea to use frames with Seam/MyFaces/Facelets? In our j2ee 1.4 apps, we've always had a header frame with the menu, a content frame, and a footer frame with copyright info. Will this work with Seam or should I wrap my components with tags and have an AJAX approach to render specific 's only. (not that I'm comfortable with this concept yet...)
John -
3. Re: Frameset & Seam
diablo341 Nov 8, 2006 10:15 AM (in response to bluetrade)Sorry, I should've disabled HTML... the sentence should read:
Will this work with Seam or should I wrap my components with div tags and have an AJAX approach to render specific div's only. (not that I'm comfortable with this concept yet...) -
4. Re: Frameset & Seam
cja987 Nov 8, 2006 10:44 AM (in response to bluetrade)Framesets are highly troublesome in JSF in general: there's no easy way for a postback to force rerendering of the whole frameset. Nor can you effectively submit two frames at once. This is actually a problem with framesets in general, not just JSF.
Facelets makes composing templates really easy. The booking example does exactly what you mentioned -- a menu on top, a blurb at bottom (and a sidebar to the left). It uses facelets to do this, and Ajax4FSF for partial page refresh for the search area. It looks even simpler than Prototype to use -- no javascript at all. -
5. Re: Frameset & Seam
diablo341 Nov 8, 2006 10:50 AM (in response to bluetrade)So that's why I saw the <a:commandButton> tag! ;)
-
6. Re: Frameset & Seam
gavin.king Nov 8, 2006 10:51 AM (in response to bluetrade)Frames are very oldfashioned, I don't see any big websites using frames today.