I took a look at what we are doing in our current application (no Faces just yet) that uses Tiles and has the "nav" section you are describing.
Basically we know the id of the form that will ultimately end up in the "main" section of our page so we use: document.forms.fooForm.submit(); Why not just use this approach? I think you can add a style to your <h:commandButton> so it would be hidden. sean On Tue, 15 Feb 2005 08:39:34 -0600, Norm Deane <[EMAIL PROTECTED]> wrote: > The hidden command button/javascript click() solution is working for me. > I'm not real crazy about it though. Seems like a hack. How about a JSF > component that renders a submit button for a form defined elsewhere? I > haven't dug very deep into the JSF internals yet but it seems like the > component could navigate the component tree, find a form by id, and then > render a submit button that uses JavaScript to submit the form. Would > this work? > > Thanks, > > Norm Deane > http://jroller.com/page/deanen > > Norm Deane wrote: > > > Sean Schofield wrote: > > > >> Hmmm. Well I better figure this out because the application I am > >> going to eventually be porting over an existing application to JSF > >> that will require this! > >> > >> How about this ... > >> > >> Make a command button on the main page but have it be hidden (with a > >> style I guess.) Give it a meaningful id and use the new forceId > >> attribute. Then have a button on your nav page that uses javascript > >> and getElementById to locate the button and "click" it. > >> > >> > >> > > > > I think I'll give this approach a shot and see how it works. > > > >> Another option might be to put the <h:form> tag in your top level > >> tiles layout page so both your nav page and your main page are part of > >> the same form. > >> > >> HTH, > >> > >> sean > >> > >> > >> > > I thought about this approach but it could get messy when you get into > > multiple forms on a page. > > > > Norm > > > >
