In an XPage, that's easy - there's a boolean "createForm" attribute that does precisely what you'd expect: if it evaluates to false, no form tag is generated.
There's just one small problem: that also tells Domino you don't want to rely on built-in platform features for any data interchange. This means that it breaks any server-defined event handlers (as opposed to event listeners you're manually attaching in client-side JavaScript), because it doesn't know where to post the event data (which I guess makes sense for full refreshes, but for partial refresh is bizarre, since that's XHR anyway).
So if your interface uses homegrown XHR (manually constructed posts with endpoints and postdata of your own choosing) or is totally non-interactive (aside from very basic navigation), this is a handy setting. Otherwise the reduction in platform functionality is not worth whatever was perceived to be beneficial about suppression of the form element... especially since the types of use cases where we used to want multiple form tags are now dead simple in XPages (e.g. having a site search feature that's handled separately from submission of site content).
In an XPage, that's easy - there's a boolean "createForm" attribute that does precisely what you'd expect: if it evaluates to false, no form tag is generated.
There's just one small problem: that also tells Domino you don't want to rely on built-in platform features for any data interchange. This means that it breaks any server-defined event handlers (as opposed to event listeners you're manually attaching in client-side JavaScript), because it doesn't know where to post the event data (which I guess makes sense for full refreshes, but for partial refresh is bizarre, since that's XHR anyway).
So if your interface uses homegrown XHR (manually constructed posts with endpoints and postdata of your own choosing) or is totally non-interactive (aside from very basic navigation), this is a handy setting. Otherwise the reduction in platform functionality is not worth whatever was perceived to be beneficial about suppression of the form element... especially since the types of use cases where we used to want multiple form tags are now dead simple in XPages (e.g. having a site search feature that's handled separately from submission of site content).