0 Replies Latest reply on Jun 22, 2011 11:24 AM by Ryan Yoder

    rich:tabpanel no longer supports nested forms for ajax and server switch types

    Ryan Yoder Newbie

      We are trying to port several apps from RF3 to RF4 and the rich tabpanel is going to be a problem.

       

      You used to be able to have a form for each tab such as this:

       

      <rich:tabpanel switchType="ajax">

           <rich:tab>

                <h:form>

                </h:form>

           </rich:tab>

           <rich:tab>

                <h:form>

                </h:form>

           </rich:tab>

      </rich:tabpanel>

       

       

      This allowed us to build a large application with many tabs containing completely unrelated forms.

      This no longer works.  The tabpanel now needs to be in its own h:form.

      Is there a workaround for this?  When can this be fixed?

       

      I am also upset about losing the selectedTab property.  One of our apps has 2 links on page 1, which take the user to page 2.  Each link auto opens a different tab on page 2.  We did this with the simple selectedTab property.  Now that this feature is gone we will have to either subclas the tabPanel renderer or do some hokey client side switch workaround. 

      I would like this functionality to come back because if we want to subclass as few component renderers as possible for obvious reasons.