Currently, the Sparkle Tab component can be used in one of two ways:

1. Entire tab component and all tab panes, and their children, contained in a single form. This is consistent with the ICEfaces 1.x panelTab component.

2. Tab component itself is not contained in a form at all, and each tab panel can use a form to wrap components it contains as required.

However, this mechanism requires the use of the so-called "formless" submit feature that was originally part of early Glimmer core.This notion of components not requiring a form is no longer seen as desirable, certainly, at least, the tab should not require it's use.

Instead, the tab should be refactored such that the tab control itself can reside in one form, while the tab panes may each reside in forms of their own (or contain forms of their own). One way this could be achieved is if the tabPanes are not specified within a Tab component tag (heriarchical), but instead, use a "for=xxx" attribute to specify the tab control that they are associated with. Using this approach, the tab-control can be placed in one form and each tab pane can be placed in another, or all tab panes in one form and the tab control in another, or all in one form, etc.