2006/9/24, David Geary <[EMAIL PROTECTED]>:
2006/9/24, Wendy Smoak <[EMAIL PROTECTED]>: > > On 9/24/06, Gary VanMatre <[EMAIL PROTECTED]> wrote: > > > Hey Wendy, this looks like the classic JSF 1.1 problem with JSP that > will > > be fixed in JSF 1.2. > > That's what I thought. :)
No, that's not the case. You must still use subviews in JSF 1.2. That's a different issue than integration with JSP. david
It's also a good practice to wrap an included fragments in a subview > tag. The subview is a naming container that will allow the same fragment > containing input widgets to be included several times in the same page. > > > > <f:subview> > > <tiles:get name="htmlHeader" flush="false"/> > > </f:subview> > > This came up recently on [EMAIL PROTECTED] [1] and Dick Starr reported that > the <tiles:insert> was working with or without a subview tag. I'm not > sure how that differs from <tiles:get> though. Anytime you include content with JSF you must wrap the included content in a subview (and you must manually assign the subview an id with the id attribute). I doubt he's including the header text more than once... exactly when > is the subview tag necessary, and what does it do? It's actually quite similar to Clay: it grafts a subview onto the main view. You always need it when you include content, whether you use <jsp:include> or Tiles. btw, <tiles:get> doesn't include content; it only gets the value of a tile attribute as a string. That's why it doesn't require a subview. david [1] > http://www.nabble.com/Shale-1.0.3-and-Tiles-Question---Tag-Question-t2204571.html#a6288731 > > Thanks, > Wendy >
